From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: broonie@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, markus.stockhausen@gmx.de,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v5 2/3] mips: dts: realtek: Add SPI NAND controller
Date: Sat, 23 Nov 2024 12:03:49 +0100 [thread overview]
Message-ID: <Z0G2lYGXHKwXpuWB@alpha.franken.de> (raw)
In-Reply-To: <20241015225434.3970360-3-chris.packham@alliedtelesis.co.nz>
On Wed, Oct 16, 2024 at 11:54:33AM +1300, Chris Packham wrote:
> Add the SPI-NAND controller on the RTL9300 family of devices. This
> supports serial/dual/quad data width and DMA for read/program
> operations.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
>
> Notes:
> Changes in v4 & v5:
> - none
> Changes in v3:
> - drop wildcard rtl9300-snand compatible
> - drop clock-names
> Changes in v2:
> - Add clocks
>
> arch/mips/boot/dts/realtek/rtl930x.dtsi | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/mips/boot/dts/realtek/rtl930x.dtsi b/arch/mips/boot/dts/realtek/rtl930x.dtsi
> index f271940f82be..b01a40ec3064 100644
> --- a/arch/mips/boot/dts/realtek/rtl930x.dtsi
> +++ b/arch/mips/boot/dts/realtek/rtl930x.dtsi
> @@ -32,6 +32,8 @@ lx_clk: clock-175mhz {
> };
>
> &soc {
> + ranges = <0x0 0x18000000 0x20000>;
> +
> intc: interrupt-controller@3000 {
> compatible = "realtek,rtl9300-intc", "realtek,rtl-intc";
> reg = <0x3000 0x18>, <0x3018 0x18>;
> @@ -59,6 +61,17 @@ timer0: timer@3200 {
> interrupts = <7>, <8>, <9>, <10>, <11>;
> clocks = <&lx_clk>;
> };
> +
> + snand: spi@1a400 {
> + compatible = "realtek,rtl9301-snand";
> + reg = <0x1a400 0x44>;
> + interrupt-parent = <&intc>;
> + interrupts = <19>;
> + clocks = <&lx_clk>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + status = "disabled";
> + };
> };
>
> &uart0 {
> --
> 2.47.0
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2024-11-23 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 22:54 [PATCH v5 0/3] Realtek SPI-NAND controller Chris Packham
2024-10-15 22:54 ` [PATCH v5 1/3] dt-bindings: spi: Add realtek,rtl9301-snand Chris Packham
2024-10-16 6:42 ` Krzysztof Kozlowski
2024-10-15 22:54 ` [PATCH v5 2/3] mips: dts: realtek: Add SPI NAND controller Chris Packham
2024-11-20 2:41 ` Chris Packham
2024-11-20 9:02 ` Thomas Bogendoerfer
2024-11-20 20:07 ` Chris Packham
2024-11-23 11:03 ` Thomas Bogendoerfer [this message]
2024-10-15 22:54 ` [PATCH v5 3/3] spi: spi-mem: Add Realtek SPI-NAND controller Chris Packham
2024-10-21 22:34 ` (subset) [PATCH v5 0/3] " Mark Brown
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=Z0G2lYGXHKwXpuWB@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=broonie@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=markus.stockhausen@gmx.de \
--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
all inboxes | Powered by JetHome®