All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Harvey <tharvey@gateworks.com>
To: Francesco Dolcini <francesco.dolcini@toradex.com>,
	"marex@denx.de" <marex@denx.de>
Cc: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	 "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	 "festevam@denx.de" <festevam@denx.de>,
	"peng.fan@nxp.com" <peng.fan@nxp.com>,
	 "shawnguo@kernel.org" <shawnguo@kernel.org>,
	"linux-imx@nxp.com" <linux-imx@nxp.com>,
	Adam Ford <aford173@gmail.com>
Subject: Re: [PATCH 2/2] arm64: dts: imx8mm: Add i.MX8M Mini Toradex Verdin based Menlo board
Date: Fri, 8 Apr 2022 08:29:15 -0700	[thread overview]
Message-ID: <CAJ+vNU0TN5VdyLbqs6YxKOHDDGgqMB6VZhhdaza3bmTAittnUg@mail.gmail.com> (raw)
In-Reply-To: <20220408084938.GB85970@francesco-nb.int.toradex.com>

On Fri, Apr 8, 2022 at 2:05 AM Francesco Dolcini
<francesco.dolcini@toradex.com> wrote:
>
> On Fri, Apr 08, 2022 at 09:56:09AM +0200, Marcel Ziswiler wrote:
> > On Fri, 2022-04-08 at 08:46 +0200, Francesco Dolcini wrote:
> > > On Thu, Apr 07, 2022 at 10:24:56PM +0200, Marek Vasut wrote:
> > > > +
> > > > +&i2c1 {
> > > > +       /* IMX8MM ERRATA e7805 -- I2C is limited to 384 kHz due to SoC bug */
> > > > +       clock-frequency = <100000>;
> > > should this and the related changes in the other i2c nodes done in the
> > > verdin.dtsi? Marcel? (errata is here:
> > > https://www.nxp.com/docs/en/errata/IMX8MDQLQ_1N14W.pdf)
> >
> > Hehe, good catch. Yeah, we probably should move this one into imx8mm-verdin.dtsi instead. On the other hand, it
> > won't hurt doing it twice resp. this one will always override it like that.
> >
> > Anyway, looks like NXP has not fixed this and is re-using the exact same I2C IP with the same errata (;-p).
>
> It looks like even i.MX7 is affected, and NXP has a quirk in the
> i2c-imx driver [0]
>
> [0] https://source.codeaurora.org/external/imx/linux-imx/commit/drivers/i2c/busses/i2c-imx.c?h=lf-5.15.y&id=493b3892ee156af529796641889ca19b971735d2
>
> Francesco

Francesco and Marek,

Interesting - I've never noticed this errata.

I don't see mention of it in the imx8mm-evk which sets the busses to
400khz, and all the other verdin I2C busses are set to 400khz as well.

Should we address this in the i2c driver in U-Boot (and Linux)
instead? Otherwise, I think all of us board maintainers should be
moving the i2c clock to 100kHz. Its not clear to me what I2C slaves
may be affected by this issue.... perhaps maintainers are only
concerned with things that go off-board?

Best Regards,

Tim

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-04-08 15:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 20:24 [PATCH 1/2] dt-bindings: arm: Add i.MX8M Mini Toradex Verdin based Menlo board Marek Vasut
2022-04-07 20:24 ` Marek Vasut
2022-04-07 20:24 ` [PATCH 2/2] arm64: dts: imx8mm: " Marek Vasut
2022-04-08  6:46   ` Francesco Dolcini
2022-04-08  7:56     ` Marcel Ziswiler
2022-04-08  8:49       ` Francesco Dolcini
2022-04-08 15:29         ` Tim Harvey [this message]
2022-04-08 15:54           ` Adam Ford
2022-04-08 16:16             ` Tim Harvey
2022-04-08 16:24               ` Marcel Ziswiler
2022-04-08 17:21           ` Marek Vasut
2022-04-08 16:20         ` Marek Vasut
2022-04-08 16:46           ` Fabio Estevam
2022-04-08 15:31       ` Marek Vasut
2022-04-08 15:02     ` Marek Vasut
2022-04-10  8:46       ` Francesco Dolcini
2022-04-10 21:37         ` Marek Vasut
2022-04-13  9:44           ` Francesco Dolcini
2022-04-13 14:14             ` Marek Vasut
2022-04-08  7:55 ` [PATCH 1/2] dt-bindings: arm: " Marcel Ziswiler
2022-04-08  7:55   ` Marcel Ziswiler
2022-04-08 16:25   ` Marek Vasut
2022-04-08 16:25     ` Marek Vasut

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=CAJ+vNU0TN5VdyLbqs6YxKOHDDGgqMB6VZhhdaza3bmTAittnUg@mail.gmail.com \
    --to=tharvey@gateworks.com \
    --cc=aford173@gmail.com \
    --cc=festevam@denx.de \
    --cc=francesco.dolcini@toradex.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=marex@denx.de \
    --cc=peng.fan@nxp.com \
    --cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.