From: Marek Vasut <marex@denx.de>
To: Frank Wunderlich <frank-w@public-files.de>,
Frank Wunderlich <linux@fw-web.de>, Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Jonas Karlman <jonas@kwiboo.se>
Subject: Re: Aw: [PATCH v3] board: rockchip: Add Bananapi R2Pro Board
Date: Sat, 16 Sep 2023 18:07:44 +0200 [thread overview]
Message-ID: <f00dad5e-bbe7-7a4d-e955-ce317cefb932@denx.de> (raw)
In-Reply-To: <trinity-6cf108b4-a879-40e2-a04a-54451262d671-1694873885042@3c-app-gmx-bs23>
On 9/16/23 16:18, Frank Wunderlich wrote:
> Hi,
>
> just a friedly reminder. would be great if it can be merged in next uboot-version.
+CC Tom
> regards Frank
>
>
>> Gesendet: Sonntag, 20. August 2023 um 18:00 Uhr
>> Von: "Frank Wunderlich" <linux@fw-web.de>
>> An: u-boot@lists.denx.de
>> Cc: "Frank Wunderlich" <frank-w@public-files.de>, "Simon Glass" <sjg@chromium.org>, "Philipp Tomsich" <philipp.tomsich@vrull.eu>, "Kever Yang" <kever.yang@rock-chips.com>, "Marek Vasut" <marex@denx.de>, "Jonas Karlman" <jonas@kwiboo.se>
>> Betreff: [PATCH v3] board: rockchip: Add Bananapi R2Pro Board
>>
>> From: Frank Wunderlich <frank-w@public-files.de>
>>
>> Add Bananapi R2 Pro board.
>>
>> Till now evb dts could be used, but iodomain is different
>> (evb has 1v8 on vccio2 and vccio4 which are 3v3 on r2pro)
>> and with iodomain driver this can cause hardware fault.
>>
>> Devicetree in mainline-Linux:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts
What would be real helpful is a commit ID from which the DT was copied ,
so it can be easily updated in the future.
next prev parent reply other threads:[~2023-09-16 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 16:00 [PATCH v3] board: rockchip: Add Bananapi R2Pro Board Frank Wunderlich
2023-09-16 14:18 ` Aw: " Frank Wunderlich
2023-09-16 16:07 ` Marek Vasut [this message]
2023-09-16 16:45 ` Frank Wunderlich
2023-09-16 18:28 ` Marek Vasut
2023-09-16 22:36 ` Jonas Karlman
2023-09-16 22:51 ` Jonas Karlman
2023-09-17 7:19 ` Aw: " Frank Wunderlich
2023-09-17 9:26 ` Jonas Karlman
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=f00dad5e-bbe7-7a4d-e955-ce317cefb932@denx.de \
--to=marex@denx.de \
--cc=frank-w@public-files.de \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=linux@fw-web.de \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--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