diff options
author | Laxman Dewangan <ldewangan@nvidia.com> | 2015-06-30 16:24:26 +0530 |
---|---|---|
committer | Wolfram Sang <wsa@the-dreams.de> | 2015-08-10 08:37:33 +0200 |
commit | 6f4664b2e2c2cfa35b48271423c5e602b6970f14 (patch) | |
tree | fef4bbe9df6cd3e4c56725d7d232261644b2cc89 /Makefile | |
parent | 77441ac00d324c037c088da090fa505b45dad9d4 (diff) | |
download | linux-6f4664b2e2c2cfa35b48271423c5e602b6970f14.tar.bz2 |
i2c: tegra: update CONFIG_LOAD for new conifiguration
Once the new configuration is set on the conifg register of
I2C controller, it is require to update the CONFIG_LOAD register
to transfer the new SW configuration to actual HW internal
registers that would be used in the actual logic.
It is like, SW is programming only shadow registers through
regular configuration and when these load_config bit fields
are set to 1, it causes the regular/shadows registers
configuration transferred to the HW internal active registers.
So SW has to set these bit fields at the end of all regular
registers configuration. And these config_load bits are HW
auto-clear bits. HW clears these bit fields once the register
configuration is moved to HW internal active registers. So SW
has to wait until these bits are auto-cleared before going
for any further programming
This mechanism is supported on T124 and after this SoCs.
Signed-off-by: Chaitanya Bandi <bandik@nvidia.com>
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Tested-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions