From: Thor Thayer <thor.thayer@linux.intel.com>
To: dinguyen@kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
catalin.marinas@arm.com, will.deacon@arm.com, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: stratix10: Add SPI clocks for Stratix10
Date: Thu, 21 Jun 2018 13:25:08 -0500 [thread overview]
Message-ID: <69d83030-efdc-ff16-a55c-3f0549ca29b6@linux.intel.com> (raw)
In-Reply-To: <1527617612-2205-2-git-send-email-thor.thayer@linux.intel.com>
Hi Dinh,
On 05/29/2018 01:13 PM, thor.thayer@linux.intel.com wrote:
> From: Thor Thayer <thor.thayer@linux.intel.com>
>
> Add the SPI clocks to the Stratix10 device tree.
>
> Signed-off-by: Thor Thayer <thor.thayer@linux.intel.com>
> ---
> arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi b/arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi
> index 47fa4b450324..34658f135daf 100644
> --- a/arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi
> +++ b/arch/arm64/boot/dts/altera/socfpga_stratix10.dtsi
> @@ -316,6 +316,8 @@
> resets = <&rst SPIM0_RESET>;
> reg-io-width = <4>;
> num-cs = <4>;
> + clocks = <&clkmgr STRATIX10_L4_MAIN_CLK>,
> + <&clkmgr STRATIX10_SPI_M_CLK>;
> status = "disabled";
> };
>
> @@ -328,6 +330,8 @@
> resets = <&rst SPIM1_RESET>;
> reg-io-width = <4>;
> num-cs = <4>;
> + clocks = <&clkmgr STRATIX10_L4_MAIN_CLK>,
> + <&clkmgr STRATIX10_SPI_M_CLK>;
> status = "disabled";
> };
>
>
Any comments on this patch?
next prev parent reply other threads:[~2018-06-21 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 18:13 [PATCH 1/2] arm64: dts: stratix10: Fix SPI nodes for Stratix10 thor.thayer
2018-05-29 18:13 ` [PATCH 2/2] arm64: dts: stratix10: Add SPI clocks " thor.thayer
2018-06-21 18:25 ` Thor Thayer [this message]
2018-06-21 18:25 ` [PATCH 1/2] arm64: dts: stratix10: Fix SPI nodes " Thor Thayer
2018-06-22 18:55 ` 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=69d83030-efdc-ff16-a55c-3f0549ca29b6@linux.intel.com \
--to=thor.thayer@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
/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).