From: Wolfram Sang <wsa@the-dreams.de>
To: Maxime Ripard <maxime.ripard@bootlin.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Gregory Clement <gregory.clement@bootlin.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: i2c: sun6i-p2wi: Fix the binding example
Date: Fri, 5 Jul 2019 20:33:00 +0200 [thread overview]
Message-ID: <20190705183300.GF4717@kunai> (raw)
In-Reply-To: <20190703095338.11266-2-maxime.ripard@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
On Wed, Jul 03, 2019 at 11:53:38AM +0200, Maxime Ripard wrote:
> Even though the binding claims that the frequency can go up to 6MHz, the
> common i2c binding sets a limit at 3MHz, which then triggers a warning.
>
> Since the only SoC that uses that bus uses a frequency of 100kHz, and that
> this bus hasn't been found in an SoC for something like 5 years, let's just
> fix the example to have a frequency within the acceptable range for i2c.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-07-05 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 9:53 [PATCH 1/2] dt-bindings: i2c: mv64xxx: Fix the example compatible Maxime Ripard
2019-07-03 9:53 ` [PATCH 2/2] dt-bindings: i2c: sun6i-p2wi: Fix the binding example Maxime Ripard
2019-07-05 10:34 ` Gregory CLEMENT
2019-07-05 16:21 ` Rob Herring
2019-07-05 18:33 ` Wolfram Sang [this message]
2019-07-05 10:34 ` [PATCH 1/2] dt-bindings: i2c: mv64xxx: Fix the example compatible Gregory CLEMENT
2019-07-05 16:22 ` Rob Herring
2019-07-05 18:32 ` Wolfram Sang
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=20190705183300.GF4717@kunai \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.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;
as well as URLs for NNTP newsgroup(s).