linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Thomas.Lendacky@amd.com (Lendacky, Thomas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: amd: seattle: Use "spi" as name for SPI controllers
Date: Mon, 24 Sep 2018 13:09:16 +0000	[thread overview]
Message-ID: <b0721afb-ff52-f348-a481-bc4e8ee0f4a7@amd.com> (raw)
In-Reply-To: <20180924094648.20797-1-thierry.reding@gmail.com>

On 09/24/2018 04:46 AM, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> Recent versions of DTC contain additional checks for SPI busses and warn
> about certain common mistakes, such as when an SPI controller has a name
> other than "spi".
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>

Looks like the same patch was already submitted:

http://lists.infradead.org/pipermail/linux-arm-kernel/2018-September/601706.html

Thanks,
Tom

> ---
>  arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi b/arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi
> index 125f4deb52fe..b664e7af74eb 100644
> --- a/arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi
> +++ b/arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi
> @@ -107,7 +107,7 @@
>  			clock-names = "uartclk", "apb_pclk";
>  		};
>  
> -		spi0: ssp at e1020000 {
> +		spi0: spi at e1020000 {
>  			status = "disabled";
>  			compatible = "arm,pl022", "arm,primecell";
>  			reg = <0 0xe1020000 0 0x1000>;
> @@ -117,7 +117,7 @@
>  			clock-names = "apb_pclk";
>  		};
>  
> -		spi1: ssp at e1030000 {
> +		spi1: spi at e1030000 {
>  			status = "disabled";
>  			compatible = "arm,pl022", "arm,primecell";
>  			reg = <0 0xe1030000 0 0x1000>;
> 

  reply	other threads:[~2018-09-24 13:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  9:46 [PATCH] arm64: amd: seattle: Use "spi" as name for SPI controllers Thierry Reding
2018-09-24 13:09 ` Lendacky, Thomas [this message]
2018-09-24 13:26   ` Thierry Reding

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=b0721afb-ff52-f348-a481-bc4e8ee0f4a7@amd.com \
    --to=thomas.lendacky@amd.com \
    --cc=linux-arm-kernel@lists.infradead.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).