From: Robert Marko <robert.marko@sartura.hr>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
robh+dt@kernel.org, linux-arm-msm <linux-arm-msm@vger.kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Luka Perkov <luka.perkov@sartura.hr>
Subject: Re: [PATCH v2 1/4] arm: dts: qcom: ipq4019: add more labels
Date: Fri, 2 Oct 2020 19:39:44 +0200 [thread overview]
Message-ID: <CA+HBbNH6rBM6naA9iTAq2JO1tC9D81+7f-Q5XxhYVF-vYoo+oQ@mail.gmail.com> (raw)
In-Reply-To: <20200909195640.3127341-2-robert.marko@sartura.hr>
On Wed, Sep 9, 2020 at 9:56 PM Robert Marko <robert.marko@sartura.hr> wrote:
>
> Lets add labels to more commonly used nodes for easier modification in board DTS files.
>
> Signed-off-by: Robert Marko <robert.marko@sartura.hr>
> Cc: Luka Perkov <luka.perkov@sartura.hr>
> ---
> Changes since v1:
> * Drop include that does not exist
>
> arch/arm/boot/dts/qcom-ipq4019.dtsi | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi b/arch/arm/boot/dts/qcom-ipq4019.dtsi
> index 3d056aada8d1..7bf1da916f25 100644
> --- a/arch/arm/boot/dts/qcom-ipq4019.dtsi
> +++ b/arch/arm/boot/dts/qcom-ipq4019.dtsi
> @@ -190,7 +190,7 @@ gcc: clock-controller@1800000 {
> reg = <0x1800000 0x60000>;
> };
>
> - rng@22000 {
> + prng: rng@22000 {
> compatible = "qcom,prng";
> reg = <0x22000 0x140>;
> clocks = <&gcc GCC_PRNG_AHB_CLK>;
> @@ -310,7 +310,7 @@ cryptobam: dma@8e04000 {
> status = "disabled";
> };
>
> - crypto@8e3a000 {
> + crypto: crypto@8e3a000 {
> compatible = "qcom,crypto-v5.1";
> reg = <0x08e3a000 0x6000>;
> clocks = <&gcc GCC_CRYPTO_AHB_CLK>,
> @@ -396,7 +396,7 @@ blsp1_uart2: serial@78b0000 {
> dma-names = "rx", "tx";
> };
>
> - watchdog@b017000 {
> + watchdog: watchdog@b017000 {
> compatible = "qcom,kpss-wdt", "qcom,kpss-wdt-ipq4019";
> reg = <0xb017000 0x40>;
> clocks = <&sleep_clk>;
> --
> 2.26.2
>
Hi,
Is there an issue with the patch preventing the review?
Regards,
Robert
next prev parent reply other threads:[~2020-10-02 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 19:56 [PATCH v2 0/4] arm: dts: qcom: ipq4019: add more boards Robert Marko
2020-09-09 19:56 ` [PATCH v2 1/4] arm: dts: qcom: ipq4019: add more labels Robert Marko
2020-10-02 17:39 ` Robert Marko [this message]
2020-09-09 19:56 ` [PATCH v2 2/4] arm: dts: add 8devices Jalapeno Robert Marko
2020-09-10 3:06 ` kernel test robot
2020-10-02 17:40 ` Robert Marko
2020-09-09 19:56 ` [PATCH v2 3/4] arm: dts: add Alfa Network AP120C-AC Robert Marko
2020-10-02 17:40 ` Robert Marko
2020-09-09 19:56 ` [PATCH v2 4/4] arm: dts: add 8devices Habanero DVK Robert Marko
2020-10-02 17:41 ` Robert Marko
2021-01-22 18:56 ` Bjorn Andersson
2021-01-25 11:02 ` Robert Marko
[not found] ` <CA+HBbNHtvP7_8RovLs1L=C+iSpGTRAov17TuC58DwNkkAeSjfQ@mail.gmail.com>
2021-01-25 16:52 ` Bjorn Andersson
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=CA+HBbNH6rBM6naA9iTAq2JO1tC9D81+7f-Q5XxhYVF-vYoo+oQ@mail.gmail.com \
--to=robert.marko@sartura.hr \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--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).