From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Adam Ford <aford173@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: netdev <netdev@vger.kernel.org>,
Adam Ford-BE <aford@beaconembedded.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3 5/5] arm64: dts: renesas: beacon kits: Setup AVB refclk
Date: Fri, 19 Mar 2021 11:40:02 +0300 [thread overview]
Message-ID: <2c9b5bb0-7229-43b4-adc6-dce8f96eac90@gmail.com> (raw)
In-Reply-To: <CAHCN7xLtDyfB5h5rWTLpiUgWY==2KmxYCOQkVSeU8DV8KB-NKg@mail.gmail.com>
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@gmail.com>
>>
>> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.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
next prev parent reply other threads:[~2021-03-19 8:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 11:51 [PATCH V3 1/5] dt-bindings: net: renesas,etheravb: Add additional clocks Adam Ford
2021-02-24 11:51 ` [PATCH V3 2/5] ARM: dts: renesas: Add fck to etheravb-rcar-gen2 clock-names list Adam Ford
2021-02-24 13:45 ` Andrew Lunn
2021-02-25 7:51 ` Geert Uytterhoeven
2021-02-24 11:51 ` [PATCH V3 3/5] arm64: dts: renesas: Add fck to etheravb-rcar-gen3 " Adam Ford
2021-02-24 13:46 ` Andrew Lunn
2021-04-19 9:38 ` Geert Uytterhoeven
2021-02-24 11:51 ` [PATCH V3 4/5] net: ethernet: ravb: Enable optional refclk Adam Ford
2021-02-24 13:47 ` Andrew Lunn
2021-03-04 8:08 ` Geert Uytterhoeven
2021-03-29 12:45 ` Adam Ford
2021-03-29 13:08 ` Geert Uytterhoeven
2021-02-24 11:51 ` [PATCH V3 5/5] arm64: dts: renesas: beacon kits: Setup AVB refclk Adam Ford
2021-03-04 8:03 ` Geert Uytterhoeven
2021-03-18 12:44 ` Adam Ford
2021-03-18 13:08 ` Geert Uytterhoeven
2021-03-19 8:40 ` Sergei Shtylyov [this message]
2021-04-17 13:54 ` Adam Ford
2021-04-19 9:39 ` Geert Uytterhoeven
2021-03-18 20:18 ` [PATCH V3 1/5] dt-bindings: net: renesas,etheravb: Add additional clocks Sergei Shtylyov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2c9b5bb0-7229-43b4-adc6-dce8f96eac90@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).