[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877clapixa.fsf@geanix.com>
Date: Tue, 19 Dec 2023 11:48:17 +0100
From: esben@...nix.com
To: Gregor Herburger <gregor.herburger@...tq-group.com>
Cc: Oleksij Rempel <o.rempel@...gutronix.de>, Pengutronix Kernel Team
<kernel@...gutronix.de>, Andi Shyti <andi.shyti@...nel.org>, Shawn Guo
<shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, Fabio
Estevam <festevam@...il.com>, NXP Linux Team <linux-imx@....com>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux@...tq-group.com"
<linux@...tq-group.com>
Subject: Re: [PATCH] i2c: i2c-imx: allow bus recovery on non-muxable pads
Gregor Herburger <gregor.herburger@...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
Powered by blists - more mailing lists