[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c9b5bb0-7229-43b4-adc6-dce8f96eac90@gmail.com>
Date: Fri, 19 Mar 2021 11:40:02 +0300
From: Sergei Shtylyov <sergei.shtylyov@...il.com>
To: Adam Ford <aford173@...il.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: netdev <netdev@...r.kernel.org>,
Adam Ford-BE <aford@...conembedded.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Magnus Damm <magnus.damm@...il.com>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V3 5/5] arm64: dts: renesas: beacon kits: Setup AVB refclk
On 18.03.2021 15:44, Adam Ford wrote:
>>> The AVB refererence clock assumes an external clock that runs
>>
>> reference
>>
>>> automatically. Because the Versaclock is wired to provide the
>>> AVB refclock, the device tree needs to reference it in order for the
>>> driver to start the clock.
>>>
>>> Signed-off-by: Adam Ford <aford173@...il.com>
>>
>> Reviewed-by: Geert Uytterhoeven <geert+renesas@...der.be>
>> i.e. will queue in renesas-devel (with the typo fixed) once the DT
>> bindings have been accepted.
>>
>
> Who do I need to ping to get the DT bindings accepted? They have an
> acked-by from Rob.
Normally, the bindings get picked up by a subsystem maintainer... or Rob :-)
[...]
MBR, Sergei
Powered by blists - more mailing lists