[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqKrad8JndQhxHAYjFXPkj7eaJ0GXqkSJy=xrfa=EHvOwA@mail.gmail.com>
Date: Thu, 7 Mar 2024 12:15:48 -0600
From: Rob Herring <robh+dt@...nel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: daniel.lezcano@...aro.org, tglx@...utronix.de,
krzysztof.kozlowski+dt@...aro.org, matthias.bgg@...il.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH 2/2] dt-bindings: timer: mediatek: Convert to json-schema
On Thu, Sep 29, 2022 at 7:29 AM AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com> wrote:
>
> Convert the MediaTek SoC timer txt binding to json-schema.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
> ---
> .../bindings/timer/mediatek,mtk-timer.txt | 47 ----------
> .../bindings/timer/mediatek,timer.yaml | 86 +++++++++++++++++++
> 2 files changed, 86 insertions(+), 47 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/timer/mediatek,mtk-timer.txt
> create mode 100644 Documentation/devicetree/bindings/timer/mediatek,timer.yaml
Looks like this never got applied. I've applied it now and added 8365
which got added to the .txt binding in the mean time. I'm not sure
it's right though. The txt binding says it was CPUX timer, but the dts
says otherwise. The 6795 dts looks wrong. It says the timer is CPUX
and GPT timer. That warning remains.
Rob
Powered by blists - more mailing lists