-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Somebody in the thread at some point said:
| Am Mo 16. Juni 2008 schrieb Andy Green:
|> Somebody in the thread at some point said:
|> | Someone please tell me why I cant read that register successfully
during
|> | resume???????
|> |
|> | Its as though the kernel caches it.
|>|> The only way it could "cache" it is if the iis memory mapped register
|> region of cpu space was literally marked as cacheable, because readl()
|> is just reading memory. So I think you can read from it OK.
| btw, probably OT, but made me curious somehow:
| 90 /*
| 91 * wm8753 register cache
| 92 * We can't read the WM8753 register space when we
| 93 * are using 2 wire for device control, so we cache them instead.
| 94 */
It's true, but those are different "registers" in the codec over i2c.
We are talking about registers in IIS unit on s3c2442, these are memory
mapped.
As Graeme posted in his trac entry:
~ iiscon = readl(s3c24xx_i2s.regs + S3C2410_IISCON);
Like I said, "readl() is just reading memory".
- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkhWQSUACgkQOjLpvpq7dMqkiQCfRyqtX+Orn623Y1+4VVMvJMuA
ufwAn17f9A0jG2+6C7U4glr6aKrTsLHQ
=d7WT
-----END PGP SIGNATURE-----