[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <601d07b5-264d-4322-b92e-63d58b3d69fa@alliedtelesis.co.nz>
Date: Tue, 19 Dec 2023 19:28:43 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: "wsa@...nel.org" <wsa@...nel.org>, Krzysztof Kozlowski
<krzysztof.kozlowski@...aro.org>, "andi.shyti@...nel.org"
<andi.shyti@...nel.org>, "robh+dt@...nel.org" <robh+dt@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org" <krzysztof.kozlowski+dt@...aro.org>,
"conor+dt@...nel.org" <conor+dt@...nel.org>, "gregory.clement@...tlin.com"
<gregory.clement@...tlin.com>, "linux-i2c@...r.kernel.org"
<linux-i2c@...r.kernel.org>, "devicetree@...r.kernel.org"
<devicetree@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 1/2] dt-bindings: i2c: add bus-reset-gpios property
On 20/12/23 06:02, wsa@...nel.org wrote:
>>> Putting it into the controller bindings looks like solving OS issue with
>>> incorrect hardware description.
>> Yes that's entirely whats happening here.
> So, this series can be dropped?
>
I personally would like to see it accepted but it seems there are
objections to this approach. I've yet to come up with anything better to
offer as an alternative.
Powered by blists - more mailing lists