From: Tom Rini <trini@konsulko.com>
To: "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>
Cc: jens.wiklander@linaro.org, oleksandr.suvorov@foundries.io,
u-boot@lists.denx.de
Subject: Re: [PATCHv5] drivers: tee: i2c: support the NXP SE05x probe errata
Date: Thu, 15 Sep 2022 08:48:29 -0400 [thread overview]
Message-ID: <20220915124829.GW6993@bill-the-cat> (raw)
In-Reply-To: <20220915045342.GA3376955@trex>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
On Thu, Sep 15, 2022 at 06:53:42AM +0200, Jorge Ramirez-Ortiz, Foundries wrote:
> On 14/09/22, Tom Rini wrote:
> > On Tue, Aug 30, 2022 at 09:56:45PM +0200, Jorge Ramirez-Ortiz wrote:
> >
> > > Early instantiation of this I2C device would lock up when being
> > > probed.
> > >
> > > https://www.nxp.com/docs/en/errata/SE050_Erratasheet.pdf
> > > 3.2.2
> > > In scenarios of detecting I2C ICs on the bus using an empty
> > > I2C frame containing only the address the SE050 will block
> > > the I2C bus.
> > >
> > > Tested on STM32MP1
> > >
> > > Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io>
> > > Acked-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
> >
> > This fails causes failure to build on sandbox:
> > https://source.denx.de/u-boot/u-boot/-/jobs/496922#L51
>
> um, will send an updated patch - sorry about it.
> does that sandbox uses different build flags?
It's normal sandbox. There's a chance I either mis-applied it (it didn't
apply cleanly), or one of the few other patches I'm testing in that
branch and about to push to next changed something.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-09-15 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 19:56 [PATCHv5] drivers: tee: i2c: support the NXP SE05x probe errata Jorge Ramirez-Ortiz
2022-09-14 22:11 ` Tom Rini
2022-09-15 4:53 ` Jorge Ramirez-Ortiz, Foundries
2022-09-15 12:48 ` Tom Rini [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=20220915124829.GW6993@bill-the-cat \
--to=trini@konsulko.com \
--cc=jens.wiklander@linaro.org \
--cc=jorge@foundries.io \
--cc=oleksandr.suvorov@foundries.io \
--cc=u-boot@lists.denx.de \
/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.