From: Walker Chen <walker.chen@starfivetech.com>
To: Conor Dooley <conor+dt@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Hal Feng <hal.feng@starfivetech.com>
Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
Walker Chen <walker.chen@starfivetech.com>
Subject: [PATCH v1 0/2] Add dma and tdm nodes for StarFive JH7110 SOC
Date: Mon, 24 Jul 2023 14:51:56 +0800 [thread overview]
Message-ID: <20230724065158.925-1-walker.chen@starfivetech.com> (raw)
Hi Conor,
These patches add dma and tdm nodes for the StarFive JH7110 SoC, they
are based on linux-next. I have tested them on the VisionFive2 board.
Thanks.
Best regards,
Walker
Walker Chen (2):
riscv: dts: starfive: jh7110: add dma controller node
riscv: dts: starfive: jh7110: add the node and pins configuration for
tdm
.../jh7110-starfive-visionfive-2.dtsi | 40 +++++++++++++++++++
arch/riscv/boot/dts/starfive/jh7110.dtsi | 39 ++++++++++++++++++
2 files changed, 79 insertions(+)
--
2.17.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Walker Chen <walker.chen@starfivetech.com>
To: Conor Dooley <conor+dt@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Hal Feng <hal.feng@starfivetech.com>
Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
Walker Chen <walker.chen@starfivetech.com>
Subject: [PATCH v1 0/2] Add dma and tdm nodes for StarFive JH7110 SOC
Date: Mon, 24 Jul 2023 14:51:56 +0800 [thread overview]
Message-ID: <20230724065158.925-1-walker.chen@starfivetech.com> (raw)
Hi Conor,
These patches add dma and tdm nodes for the StarFive JH7110 SoC, they
are based on linux-next. I have tested them on the VisionFive2 board.
Thanks.
Best regards,
Walker
Walker Chen (2):
riscv: dts: starfive: jh7110: add dma controller node
riscv: dts: starfive: jh7110: add the node and pins configuration for
tdm
.../jh7110-starfive-visionfive-2.dtsi | 40 +++++++++++++++++++
arch/riscv/boot/dts/starfive/jh7110.dtsi | 39 ++++++++++++++++++
2 files changed, 79 insertions(+)
--
2.17.1
next reply other threads:[~2023-07-24 6:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 6:51 Walker Chen [this message]
2023-07-24 6:51 ` [PATCH v1 0/2] Add dma and tdm nodes for StarFive JH7110 SOC Walker Chen
2023-07-24 6:51 ` [PATCH v1 1/2] riscv: dts: starfive: jh7110: add dma controller node Walker Chen
2023-07-24 6:51 ` Walker Chen
2023-07-24 6:51 ` [PATCH v1 2/2] riscv: dts: starfive: jh7110: add the node and pins configuration for tdm Walker Chen
2023-07-24 6:51 ` Walker Chen
2023-07-26 16:21 ` [PATCH v1 0/2] Add dma and tdm nodes for StarFive JH7110 SOC Conor Dooley
2023-07-26 16:21 ` Conor Dooley
2023-08-18 12:40 ` Hal Feng
2023-08-18 12:40 ` Hal Feng
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=20230724065158.925-1-walker.chen@starfivetech.com \
--to=walker.chen@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hal.feng@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.