From: Wolfram Sang <wsa@the-dreams.de>
To: Douglas Anderson <dianders@chromium.org>
Cc: andy.gross@linaro.org, bjorn.andersson@linaro.org,
kramasub@codeaurora.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
David Brown <david.brown@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-soc@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: soc: qcom: Fix default clock-freq for qcom,geni-i2c
Date: Sun, 24 Jun 2018 00:16:06 +0900 [thread overview]
Message-ID: <20180623151605.kyycbeema55trj7w@ninjato> (raw)
In-Reply-To: <20180613175011.217585-1-dianders@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
On Wed, Jun 13, 2018 at 10:50:11AM -0700, Douglas Anderson wrote:
> 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>
Acked-by: Wolfram Sang <wsa@the-dreams.de>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-23 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 17:50 [PATCH] dt-bindings: soc: qcom: Fix default clock-freq for qcom,geni-i2c Douglas Anderson
2018-06-22 16:51 ` Bjorn Andersson
2018-06-23 15:16 ` Wolfram Sang [this message]
2018-06-26 19:24 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180623151605.kyycbeema55trj7w@ninjato \
--to=wsa@the-dreams.de \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=kramasub@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox