From: Drew Fustini <drew@pdp7.com>
To: Kanak Shilledar <kanakshilledar@gmail.com>
Cc: 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: Re: [PATCH v3 0/1] Add basic SPI support on TH1520
Date: Thu, 25 Jul 2024 20:52:25 -0700 [thread overview]
Message-ID: <ZqMdeTrV5GE0TVUV@x1> (raw)
In-Reply-To: <20240705093503.215787-1-kanakshilledar@gmail.com>
On Fri, Jul 05, 2024 at 03:04:58PM +0530, Kanak Shilledar wrote:
> 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].
>
> [...]
Applied to thead-dt-for-next, thanks!
[1/1] riscv: dts: thead: add basic spi node
commit: 0f351f8c4f4ee87b729cc366917e67e3eee2d3db
Best regards,
--
Drew Fustini <drew@pdp7.com>
Link: https://github.com/pdp7/linux/commit/0f351f8c4f4ee87b729cc366917e67e3eee2d3db
next prev parent reply other threads:[~2024-07-26 3:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 9:34 [PATCH v3 0/1] Add basic SPI support on TH1520 Kanak Shilledar
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 ` Drew Fustini [this message]
2024-07-26 8:19 ` [PATCH v3 0/1] Add basic SPI support on TH1520 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=ZqMdeTrV5GE0TVUV@x1 \
--to=drew@pdp7.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=kanakshilledar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).