[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <89d6a820-d510-4549-8097-76670fa36e6a@collabora.com>
Date: Fri, 8 Mar 2024 09:38:10 +0100
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
To: Rob Herring <robh+dt@...nel.org>
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
Il 07/03/24 19:15, Rob Herring ha scritto:
> 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.
>
Thanks. This one got totally forgotten, yes.
By the way, I'll recheck the 6795 DT as soon as possible.
Cheers!
Angelo
Powered by blists - more mailing lists