[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5edf3d3b-6f59-0af3-6414-940a278962bf@microchip.com>
Date:   Fri, 26 May 2023 04:47:28 +0000
From:   <Claudiu.Beznea@...rochip.com>
To:     <conor@...nel.org>
CC:     <robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
        <conor+dt@...nel.org>, <Nicolas.Ferre@...rochip.com>,
        <alexandre.belloni@...tlin.com>, <daniel.lezcano@...aro.org>,
        <tglx@...utronix.de>, <wim@...ux-watchdog.org>,
        <linux@...ck-us.net>, <sebastian.reichel@...labora.com>,
        <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <linux-watchdog@...r.kernel.org>
Subject: Re: [PATCH 3/5] dt-bindings: timer: microchip,sam9x60-pit64b: convert
 to yaml
On 25.05.2023 20:14, Conor Dooley wrote:
>> Convert Microchip PIT64B to YAML. Along with it clock-names binding has
>> been added as the driver needs it to get PIT64B clocks.
> I don't think both of these PIT things need to have different binding
> files. 90% of it is the same, just the clock-names/number - so you can
But these are different hardware blocks with different functionalities and
different drivers.
> combine the two into one file with an
Powered by blists - more mailing lists
 
