From: Shawn Guo <shawnguo@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: robh+dt@kernel.org, festevam@gmail.com, plaes@plaes.org,
kernel@pengutronix.de, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: imx6qdl-kontron-samx6i: increase i2c-frequency
Date: Tue, 1 Dec 2020 09:19:55 +0800 [thread overview]
Message-ID: <20201201011955.GP4072@dragon> (raw)
In-Reply-To: <20201126192252.6067-1-m.felsch@pengutronix.de>
On Thu, Nov 26, 2020 at 08:22:52PM +0100, Marco Felsch wrote:
> Set it to max. allowed 375kHz for faster transfers. The limit is given
> by the erratum [1].
>
> [1] https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
Applied, thanks.
prev parent reply other threads:[~2020-12-01 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 19:22 [PATCH] ARM: dts: imx6qdl-kontron-samx6i: increase i2c-frequency Marco Felsch
2020-12-01 1:19 ` Shawn Guo [this message]
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=20201201011955.GP4072@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=m.felsch@pengutronix.de \
--cc=plaes@plaes.org \
--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).