diff options
author | Douglas Anderson <dianders@chromium.org> | 2018-06-13 10:50:11 -0700 |
---|---|---|
committer | Rob Herring <robh@kernel.org> | 2018-06-26 13:25:49 -0600 |
commit | 5bfabc0aabe64a5fccc7afa6e5a9cc4443d8898b (patch) | |
tree | 67fbbff48fe8e2b1870855b757b70294d0cec0d6 /drivers/of | |
parent | e88d133d6229de49cce1f8bc11455e93b6f9b837 (diff) | |
download | linux-stable-5bfabc0aabe64a5fccc7afa6e5a9cc4443d8898b.tar.gz linux-stable-5bfabc0aabe64a5fccc7afa6e5a9cc4443d8898b.tar.bz2 linux-stable-5bfabc0aabe64a5fccc7afa6e5a9cc4443d8898b.zip |
dt-bindings: soc: qcom: Fix default clock-freq for qcom,geni-i2c
In an early version of the I2C patch that was posted to the list the
default I2C frequency (if none was specified) was 400 kHz. There was
debate on the list and we decided that it would be more consistent
with the rest of i2c if we defaulted to 100 kHz. ...but we never
updated the bindings. Let's fix this.
NOTE: since the i2c driver itself hasn't actually landed yet and the
SoC here is very new it seems terribly unlikely that anyone was
relying on the old 400 kHz number, so I'll assume this is an OK
"incompatible" device tree change.
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Acked-by: Wolfram Sang <wsa@the-dreams.de>
Signed-off-by: Rob Herring <robh@kernel.org>
Diffstat (limited to 'drivers/of')
0 files changed, 0 insertions, 0 deletions