From: esben@geanix.com
To: Gregor Herburger <gregor.herburger@ew.tq-group.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Andi Shyti <andi.shyti@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux@ew.tq-group.com" <linux@ew.tq-group.com>
Subject: Re: [PATCH] i2c: i2c-imx: allow bus recovery on non-muxable pads
Date: Tue, 19 Dec 2023 11:48:17 +0100 [thread overview]
Message-ID: <877clapixa.fsf@geanix.com> (raw)
In-Reply-To: <ZYFpUpP0Ll5c99py@herburgerg-w2> (Gregor Herburger's message of "Tue, 19 Dec 2023 10:58:42 +0100")
Gregor Herburger <gregor.herburger@ew.tq-group.com> writes:
> Hi Esben,
>
>> Why not move to use the generic GPIO recovery instead? Will something
>> like this be able to cover at least the same scenarios as your change?
>
> I was not aware of the generic GPIO recovery functions. At a first
> glance I think your solution should work. I will give it a try and test
> it on hardware.
Great. Let me know if it works for me. If it does, I guess I should send
the patch to the list in it's own thread.
/Esben
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-19 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 17:06 [PATCH] i2c: i2c-imx: allow bus recovery on non-muxable pads Gregor Herburger
2023-12-19 7:43 ` esben
2023-12-19 9:58 ` Gregor Herburger
2023-12-19 10:48 ` esben [this message]
2023-12-20 10:37 ` Gregor Herburger
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=877clapixa.fsf@geanix.com \
--to=esben@geanix.com \
--cc=andi.shyti@kernel.org \
--cc=festevam@gmail.com \
--cc=gregor.herburger@ew.tq-group.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=o.rempel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--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 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).