From: Stefan Eichenberger <eichest@gmail.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
kernel@pengutronix.de, shawnguo@kernel.org,
s.hauer@pengutronix.de, festevam@gmail.com, Frank.Li@nxp.com,
francesco.dolcini@toradex.com, linux-i2c@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stefan Eichenberger <stefan.eichenberger@toradex.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2 1/4] i2c: imx: only poll for bus busy in multi master mode
Date: Fri, 23 Aug 2024 15:48:32 +0200 [thread overview]
Message-ID: <ZsiTMITWF0Tj3o8Q@eichest-laptop> (raw)
In-Reply-To: <2bbddaxyjkxfmlgmq3yqcbzo7dsb2pq5bvdatk2y4ig4iintkt@35btqkdv7sy3>
Hi Andi,
On Fri, Aug 23, 2024 at 02:35:54AM +0200, Andi Shyti wrote:
> Hi,
>
> On Thu, Aug 22, 2024 at 12:04:43PM GMT, Oleksij Rempel wrote:
> > On Thu, Aug 22, 2024 at 09:03:55AM +0200, Stefan Eichenberger wrote:
> > > Hi Andi,
> > >
> > > On Thu, Aug 22, 2024 at 12:21:30AM +0200, Andi Shyti wrote:
> > > > Hi Stefan,
> > > >
> > > > > @@ -1468,6 +1473,8 @@ static int i2c_imx_probe(struct platform_device *pdev)
> > > > > goto rpm_disable;
> > > > > }
> > > > >
> > > > > + i2c_imx->multi_master = of_property_read_bool(pdev->dev.of_node, "multi-master");
> > > > > +
> > > >
> > > > you might also want to add the multi-master boolean property in
> > > > the binding.
> > >
> > > We discussed this internally and weren't sure when it was required
> > > because e.g. i2c-rcar and i2c-tegra don't have it documented in their
> > > bindings. Is it still required if it is part of the dt-schema?
> > > https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/i2c/i2c-controller.yaml
> >
> > The i2c-imx.yaml has "unevaluatedProperties: false", which fill discard
> > every thing not in this yaml
> >
> > > If so, I will add it in the next version.
> >
> > Yes, please.
>
> sorry for the confusion, please don't add it. I had a chat with
> Krzysztof and I will quote him: "this is a core property, coming
> with dtschema, so they dont need to update bindings".
>
> He also sent a cleanup to remove the only binding using it.
No problem, thanks for the clarification.
Should I still separate the multi-master patch from the rest of the
series, even though it doesn't seem to fix the problem Fabio sees? I did
some more testing today and the workarounds he found do not solve the
problem I see, so they are definitely not the same.
Regards,
Stefan
next prev parent reply other threads:[~2024-08-23 13:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 7:19 [PATCH v2 0/4] i2c: imx: prevent rescheduling in non-dma mode Stefan Eichenberger
2024-08-19 7:19 ` [PATCH v2 1/4] i2c: imx: only poll for bus busy in multi master mode Stefan Eichenberger
2024-08-21 11:01 ` Fabio Estevam
2024-08-21 14:39 ` Oleksij Rempel
2024-08-21 15:23 ` Stefan Eichenberger
2024-08-21 16:43 ` Fabio Estevam
2024-08-21 22:31 ` Andi Shyti
2024-08-22 6:51 ` Oleksij Rempel
2024-08-22 11:07 ` Fabio Estevam
2024-08-22 11:50 ` Stefan Eichenberger
2024-08-22 12:59 ` Fabio Estevam
2024-08-23 13:43 ` Stefan Eichenberger
2024-08-21 22:21 ` Andi Shyti
2024-08-22 7:03 ` Stefan Eichenberger
2024-08-22 10:04 ` Oleksij Rempel
2024-08-22 12:03 ` Stefan Eichenberger
2024-08-23 0:35 ` Andi Shyti
2024-08-23 13:48 ` Stefan Eichenberger [this message]
2024-08-23 14:04 ` Oleksij Rempel
2024-08-23 14:42 ` Stefan Eichenberger
2024-08-19 7:19 ` [PATCH v2 2/4] i2c: imx: separate atomic, dma and non-dma use case Stefan Eichenberger
2024-08-30 7:31 ` Oleksij Rempel
2024-08-19 7:19 ` [PATCH v2 3/4] i2c: imx: use readb_relaxed and writeb_relaxed Stefan Eichenberger
2024-08-30 7:37 ` Oleksij Rempel
2024-08-19 7:19 ` [PATCH v2 4/4] i2c: imx: prevent rescheduling in non dma mode Stefan Eichenberger
2024-08-30 8:13 ` Oleksij Rempel
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=ZsiTMITWF0Tj3o8Q@eichest-laptop \
--to=eichest@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=andi.shyti@kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan.eichenberger@toradex.com \
/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.