From: Kanak Shilledar <kanakshilledar@gmail.com>
Cc: Kanak Shilledar <kanakshilledar@gmail.com>,
Jisheng Zhang <jszhang@kernel.org>, Guo Ren <guoren@kernel.org>,
Fu Wei <wefu@redhat.com>, Conor Dooley <conor@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/1] Add basic SPI support on TH1520
Date: Fri, 5 Jul 2024 15:04:58 +0530 [thread overview]
Message-ID: <20240705093503.215787-1-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.
[2] Driver Patch discussion
[3] Devicetree binding discussion
Changes made in v3:
- Dropped the driver patch as the generic fallback compatible was
working properly. [2]
- Removed the devicetree binding patch as it got accepted and is already
in the linux-next branch. [3]
- Arranged the devicetree aliases alphabetically in the DTS files.
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
[2] https://lore.kernel.org/all/20240701121355.262259-4-kanakshilledar@gmail.com/
[3] https://lore.kernel.org/all/20240701121355.262259-3-kanakshilledar@gmail.com/
Kanak Shilledar (1):
riscv: dts: thead: add basic spi node
.../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 ++++++++++++++++
4 files changed, 34 insertions(+)
base-commit: 22a40d14b572deb80c0648557f4bd502d7e83826
--
2.45.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2024-07-05 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 9:34 Kanak Shilledar [this message]
2024-07-05 9:34 ` [PATCH v3 1/1] riscv: dts: thead: add basic spi node Kanak Shilledar
2024-07-12 8:41 ` Kanak Shilledar
2024-07-12 13:48 ` Conor Dooley
2024-07-12 16:05 ` Drew Fustini
2024-07-14 7:11 ` Kanak Shilledar
2024-07-26 3:52 ` [PATCH v3 0/1] Add basic SPI support on TH1520 Drew Fustini
2024-07-26 8:19 ` Emil Renner Berthing
2024-07-26 16:05 ` Drew Fustini
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=20240705093503.215787-1-kanakshilledar@gmail.com \
--to=kanakshilledar@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=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