From: Kanak Shilledar <kanakshilledar@gmail.com>
Cc: Kanak Shilledar <kanakshilledar@gmail.com>,
Serge Semin <fancer.lancer@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jisheng Zhang <jszhang@kernel.org>, Guo Ren <guoren@kernel.org>,
Fu Wei <wefu@redhat.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: [PATCH v2 0/3] Add basic SPI support on TH1520
Date: Mon, 1 Jul 2024 17:43:51 +0530 [thread overview]
Message-ID: <20240701121355.262259-2-kanakshilledar@gmail.com> (raw)
Implemented basic SPI support for TH1520 SoC. There are two SPIs reserved
on the LicheePi4A, one on the SPI Flash pads that are blanked out on the
back, and one on the pins. I implemented the one connected to the pad.
It is using a fixed clock of 396MHz. The address and clock frequency was
referenced from the TH1520 System Reference Manual [1].
I have tested this on the LicheePi4A.
Changes made in v2:
- Changed from single patch file to a patchset by splitting the single
commit into dt-bindings, driver and the devicetree.
[1] https://openbeagle.org/beaglev-ahead/beaglev-ahead/-/blob/main/docs/TH1520%20System%20User%20Manual.pdf
Kanak Shilledar (3):
dt-bindings: spi: snps,dw-apb-ssi.yaml: update compatible property
spi: dw-mmio: update dw_spi_mmio_of_match struct with thead
riscv: dts: thead: add basic spi node
.../devicetree/bindings/spi/snps,dw-apb-ssi.yaml | 4 ++++
.../boot/dts/thead/th1520-beaglev-ahead.dts | 9 +++++++++
.../boot/dts/thead/th1520-lichee-module-4a.dtsi | 4 ++++
.../riscv/boot/dts/thead/th1520-lichee-pi-4a.dts | 5 +++++
arch/riscv/boot/dts/thead/th1520.dtsi | 16 ++++++++++++++++
drivers/spi/spi-dw-mmio.c | 1 +
6 files changed, 39 insertions(+)
base-commit: 6ba59ff4227927d3a8530fc2973b80e94b54d58f
--
2.45.2
next reply other threads:[~2024-07-01 12:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 12:13 Kanak Shilledar [this message]
2024-07-01 12:13 ` [PATCH v2 1/3] dt-bindings: spi: snps,dw-apb-ssi.yaml: update compatible property Kanak Shilledar
2024-07-01 14:10 ` Conor Dooley
2024-07-01 12:13 ` [PATCH v2 2/3] spi: dw-mmio: update dw_spi_mmio_of_match struct with thead Kanak Shilledar
2024-07-01 13:17 ` Samuel Holland
2024-07-01 18:57 ` Serge Semin
2024-07-03 7:28 ` Conor Dooley
2024-07-03 13:12 ` Kanak Shilledar
2024-07-03 14:27 ` Conor Dooley
2024-07-03 14:37 ` Kanak Shilledar
2024-07-01 12:13 ` [PATCH v2 3/3] riscv: dts: thead: add basic spi node Kanak Shilledar
2024-07-03 14:45 ` Conor Dooley
2024-07-04 5:42 ` Kanak Shilledar
2024-07-04 16:49 ` Conor Dooley
2024-07-04 16:59 ` Drew Fustini
2024-07-04 17:53 ` Drew Fustini
2024-07-05 9:11 ` Kanak Shilledar
2024-07-01 18:55 ` (subset) [PATCH v2 0/3] Add basic SPI support on TH1520 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=20240701121355.262259-2-kanakshilledar@gmail.com \
--to=kanakshilledar@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=wefu@redhat.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).