devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: niravkumar.l.rabara@intel.com
To: dinguyen@kernel.org
Cc: devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
	linux-kernel@vger.kernel.org, niravkumar.l.rabara@intel.com,
	robh+dt@kernel.org
Subject: Re: [PATCH] arm64: dts: altera: socfpga_stratix10: move clocks out of soc node
Date: Fri, 24 Jun 2022 11:10:17 +0800	[thread overview]
Message-ID: <20220624031017.3247656-1-niravkumar.l.rabara@intel.com> (raw)
In-Reply-To: <b111c356-ee6a-bd68-d08f-fbe2a67d2f55@kernel.org>

>
>Take that back. Your changes are fine, but you need to update the board 
>files as well. i.e socfpga_stratix10_socdk.dts
>
>
>--- a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
>+++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
>@@ -52,12 +52,6 @@ ref_033v: regulator-v-ref {
>         };
>
>         soc {
>               clocks {
>                       osc1 {
>                               clock-frequency = <25000000>;
>                       };
>               };
>
>                eccmgr {
>                         sdmmca-ecc@ff8c8c00 {
>                                 compatible = "altr,socfpga-s10-sdmmc-ecc",
>@@ -113,6 +107,10 @@ &mmc {
>         bus-width = <4>;
>  };
>
>+&osc1 {
>+       clock-frequency = <25000000>;
>+};
>+

Sorry I missed this change, will update in v2 patch.

Thanks,
Nirav


  reply	other threads:[~2022-06-24  3:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  2:42 [PATCH] arm64: dts: altera: socfpga_stratix10: move clocks out of soc node niravkumar.l.rabara
2022-06-23 16:16 ` Dinh Nguyen
2022-06-23 19:07   ` Dinh Nguyen
2022-06-24  3:10     ` niravkumar.l.rabara [this message]
2022-06-24 11:59       ` niravkumar.l.rabara
2022-06-24 14:49         ` Dinh Nguyen
2022-06-24 16:21           ` [PATCHv3] " niravkumar.l.rabara
2022-06-24 22:47             ` Dinh Nguyen

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=20220624031017.3247656-1-niravkumar.l.rabara@intel.com \
    --to=niravkumar.l.rabara@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@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).