From: Tom Rini <trini@konsulko.com>
To: anoduck <anoduck@protonmail.com>
Cc: u-boot@lists.denx.de, Sumit Garg <sumit.garg@kernel.org>,
Minda Chen <minda.chen@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>
Subject: Re: [PATCH RFC PineTab-V DTS File] RFC: Pine64 Pinetab-V dts Device Tree File
Date: Sat, 18 Jul 2026 16:25:05 -0600 [thread overview]
Message-ID: <20260718222505.GV749385@bill-the-cat> (raw)
In-Reply-To: <20260718-develop-v1-1-d4b5c0675f87@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
On Sat, Jul 18, 2026 at 08:10:38AM +0000, anoduck wrote:
> Added compilable PineTab-V device-tree dts file derived from pine64 community distributed dts and additional parameters
> Community provided definitions:
> - Audio Codec
> - Accelerometer
>
> Additional parameters include:
> - Definitions for sd-card and on board EMMC devices
> - Definitins for power supply to sd-card
>
> Signed-off-by: The Anoduck <anoduck@protonmail.com>
> ---
> Provide support for the Pine64 Pinetab-V Risc-V 64bit Tablet
>
> Signed-off-by: anoduck <anoduck@protonmail.com>
> ---
> .../src/riscv/starfive/jh7110-pine64-pinetabv.dts | 116 +++++++++++++++++++++
> 1 file changed, 116 insertions(+)
So per the documentation at
https://docs.u-boot-project.org/en/latest/develop/devicetree/control.html#resyncing-with-devicetree-rebasing
we only take modifications in dts/upstream that are strict cherry-pick's
from the upstream source. This needs to be done under arch/riscv/
instead, and you should split the additional changes in to a
-u-boot.dtsi suffixed file, so that it's easier to replace this with the
upstream file when ready. Thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-07-18 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 8:10 [PATCH RFC PineTab-V DTS File] RFC: Pine64 Pinetab-V dts Device Tree File anoduck
2026-07-18 22:25 ` Tom Rini [this message]
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=20260718222505.GV749385@bill-the-cat \
--to=trini@konsulko.com \
--cc=anoduck@protonmail.com \
--cc=hal.feng@starfivetech.com \
--cc=minda.chen@starfivetech.com \
--cc=sumit.garg@kernel.org \
--cc=u-boot@lists.denx.de \
/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