Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <robh+dt@kernel.org>, <krzk+dt@kernel.org>, <palmer@dabbelt.com>
Cc: <paul.walmsley@sifive.com>, <palmer@rivosinc.com>,
	<aou@eecs.berkeley.edu>, <Daire.McNamara@microchip.com>,
	<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
	<robh@kernel.org>
Subject: Re: [PATCH v2] riscv: dts: microchip: remove spi-max-frequency property
Date: Mon, 6 Jun 2022 16:46:51 +0000	[thread overview]
Message-ID: <92127698-ddba-8ee2-4c97-e9809d8f2ff9@microchip.com> (raw)
In-Reply-To: <20220603084534.1919804-1-conor.dooley@microchip.com>

On 03/06/2022 09:45, Conor Dooley wrote:
> spi-max-frequency property is supposed to be a per SPI peripheral device
> property, not a SPI controller property, so remove it.
> 
> Reported-by: Rob Herring <robh@kernel.org>
> Link: https://lore.kernel.org/lkml/20220526014141.2872567-1-robh@kernel.org/
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>

Feels weird saying this, but:
Applied to dt-for-next of conor/linux.git

> ---
> Since v1:
> - Rebase on changed filename JIC
> ---
>  arch/riscv/boot/dts/microchip/mpfs.dtsi | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/arch/riscv/boot/dts/microchip/mpfs.dtsi b/arch/riscv/boot/dts/microchip/mpfs.dtsi
> index 3095d08453a1..65a20c0b8af1 100644
> --- a/arch/riscv/boot/dts/microchip/mpfs.dtsi
> +++ b/arch/riscv/boot/dts/microchip/mpfs.dtsi
> @@ -299,7 +299,6 @@ spi1: spi@20109000 {
>  			interrupt-parent = <&plic>;
>  			interrupts = <55>;
>  			clocks = <&clkcfg CLK_SPI1>;
> -			spi-max-frequency = <25000000>;
>  			status = "disabled";
>  		};
>  
> @@ -311,7 +310,6 @@ qspi: spi@21000000 {
>  			interrupt-parent = <&plic>;
>  			interrupts = <85>;
>  			clocks = <&clkcfg CLK_QSPI>;
> -			spi-max-frequency = <25000000>;
>  			status = "disabled";
>  		};
>  

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2022-06-06 16:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  8:45 [PATCH v2] riscv: dts: microchip: remove spi-max-frequency property Conor Dooley
2022-06-06 16:46 ` Conor.Dooley [this message]

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=92127698-ddba-8ee2-4c97-e9809d8f2ff9@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=Daire.McNamara@microchip.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@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