[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABjd4YyQ1wg4Esd0ZGO-2+WGXkzrqfbhxLMWJ9N8eXTDr4BBgg@mail.gmail.com>
Date: Tue, 13 May 2025 20:08:12 +0400
From: Alexey Charkov <alchark@...il.com>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3] dt-bindings: timer: via,vt8500-timer: Convert to YAML
On Tue, May 13, 2025 at 7:49 PM Daniel Lezcano
<daniel.lezcano@...aro.org> wrote:
>
> On Tue, May 06, 2025 at 04:16:32PM +0400, Alexey Charkov wrote:
> > Rewrite the textual description for the VIA/WonderMedia timer
> > as YAML schema.
> >
> > The IP can generate up to four interrupts from four respective match
> > registers, so reflect that in the schema.
> >
> > Reviewed-by: Rob Herring (Arm) <robh@...nel.org>
> > Signed-off-by: Alexey Charkov <alchark@...il.com>
> > ---
> > Changes in v3:
> > - Added Rob's review tag (thanks Rob)
> > - Rebased on top of next-20250506 to pull in MAINTAINERS updates
> > - Link to v2: https://lore.kernel.org/r/20250418-via_vt8500_timer_binding-v2-1-3c125568f028@gmail.com
> >
> > Changes in v2:
> > - split out this binding change from the big series affecting multiple
> > subsystems unnecessarily (thanks Rob)
> > - added description for the four possible interrupts (thanks Rob)
> > - added overall description of the IC block
> >
> > Link to v1: https://lore.kernel.org/all/20250416-wmt-updates-v1-6-f9af689cdfc2@gmail.com/
> > ---
>
> The patch does not apply.
>
> --- MAINTAINERS
> +++ MAINTAINERS
> @@ -3467,6 +3467,7 @@ F: Documentation/devicetree/bindings/hwinfo/via,vt8500-scc-id.yaml
> F: Documentation/devicetree/bindings/i2c/i2c-wmt.txt
> F: Documentation/devicetree/bindings/interrupt-controller/via,vt8500-intc.yaml
> F: Documentation/devicetree/bindings/pwm/via,vt8500-pwm.yaml
>
> ^^^^^^ those bindings are not in my tree
This series is based on next-20250506. Happy to rebase onto 6.15-rc1,
but these will result in a (trivial) conflict when merging the
different trees into -next and to master. Please let me know if that's
better.
Best regards,
Alexey
Powered by blists - more mailing lists