[PATCH v10 03/13] dt-bindings: Convert gpio-mmio to yaml

[Sean Anderson]

On 3/13/23 04:53, Leonard, Niall wrote:
> [You don't often get email from niall.leonard at ncr.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> On 09/03/2023 09:16, Linus Walleij wrote:
>> *External Message* - Use caution before opening links or attachments
>>
>> On Tue, Mar 7, 2023 at 4:35 PM Sean Anderson <sean.anderson at seco.com> wrote:
>>> On 3/7/23 03:42, Krzysztof Kozlowski wrote:
>>
>>>> https://urldefense.com/v3/__https://lore.kernel.org/all/20230126-gpio-mmio-fix-v2-1-38397aace340@ncr.com/__;!!In4Qlw!uQKGkt7dO5TA-561XcuPNoqyti_AogqJ0cV3ymFZNob-Q1-Z1xmcOv_22JBP5xO-OIemaCZ1VY37nWLIe1AXyOkieg$
>>>
>>> Thanks for linking to that.
>>>
>>> I believe this patch should be applied instead of that one because
>>>
>>> - It documents all the registers, which were previously only documented
>>>    in the driver
>>> - It handles the endianness properties.
>>> - It consolidates the various descriptions of this binding into one
>>>    schema.
>>
>> Niall are you sending a v3 of this patch soon?
>> Include Sean on the reviewer list!
>>
>> Yours,
>> Linus Walleij
> I never got around to working on the V3 patch. The hold up for me was
> the changes to the bindings.
> I'm now wondering if I should wait on Sean's patch being accepted and
> then I could re-submit the driver changes.
> What's the consensus ?

I am going to submit v11 later today. However, the phy subsystem
maintainer refuses to review the phy patches until all the other patches
are ready. Therefore, I suspect v11 may not be the last revision of this
series. If the GPIO folks want to pick v11 of this patch separately, I
think that would help accelerate the process.

--Sean