aboutsummaryrefslogtreecommitdiff
path: root/drivers/phy
diff options
context:
space:
mode:
authorGuenter Roeck2016-06-22 10:01:57 -0700
committerGuenter Roeck2016-07-12 14:24:09 -0700
commita9f92ccf334f7e15124193b1d7b89b7e6e6624e2 (patch)
tree82ffa2c205613f863d97e0736b55422350d40395 /drivers/phy
parent3d8f7a89a1979be7f631cf06e02f882adf144885 (diff)
hwmon: (tmp102) Rework chip configuration
So far the chip was forced into polarity 0, even if it was preconfigured differently. Do not touch the polarity when configuring the chip. Also, the configuration register was read beack to check if the configuration 'sticks'. Ultimately, that is similar to checking if the chip is a tmp102 in the first place. Checking if a write into the configuration register was successful is really not the way to do it, and quite risky if the chip is not a tmp102, so drop that check. Instead, verify if the configuration register has unexpected bits set before writing into it. Acked-by: Nishanth Menon <nm@ti.com> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'drivers/phy')
0 files changed, 0 insertions, 0 deletions