From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de, Peter Robinson <pbrobinson@gmail.com>,
Tim Harvey <tharvey@gateworks.com>,
Jagan Teki <jagan@amarulasolutions.com>,
"Marty E . Plummer" <hanetzer@startmail.com>,
Heiko Schocher <hs@denx.de>,
Alexandre Vicenzi <alexandre.vicenzi@suse.com>,
Artem Lapkin <email2tema@gmail.com>,
Christian Hewitt <christianshewitt@gmail.com>,
Fabio Estevam <festevam@denx.de>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Andre Przywara <andre.przywara@arm.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Johan Jonker <jbx6244@gmail.com>,
Kever Yang <kever.yang@rock-chips.com>
Subject: Re: [PATCH 1/4] rockchip: gru: Set up SoC IO domain registers
Date: Tue, 7 Dec 2021 23:31:35 +0300 [thread overview]
Message-ID: <69a6472c-2cae-f744-2d54-6f3cb195efce@gmail.com> (raw)
In-Reply-To: <CAPnjgZ2fcCVzwmC7m4rj9CJabFLRbnLvfnda70YHWnUxJJBwJg@mail.gmail.com>
On 03/12/2021 06:31, Simon Glass wrote:
> On Thu, 25 Nov 2021 at 10:40, Alper Nebi Yasak <alpernebiyasak@gmail.com> wrote:
>> The RK3399 SoC needs to know the voltage value provided by some
>> regulators, which is done by setting relevant register bits. Configure
>> these the way other RK3399 boards do, but with values set in coreboot.
>
> What do you mean by values set in coreboot? We don't need that to run
> here, do we?
I meant that I wasn't blindly copying from other boards which have the
same block (e.g. Pinebook Pro), but was using known-good values for Gru
boards that coreboot also uses [1].
I tested again and it looks like my Kevin works just as good without
this patch, so I'll drop it.
[1]
https://review.coreboot.org/plugins/gitiles/coreboot/+/refs/heads/master/src/mainboard/google/gru/bootblock.c#19
>> Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
>> ---
>> There is a driver for this on Rockchip's repo, I managed to forward-port
>> it and get it working. If that's more desirable than doing it per-board
>> like this I can send that upstream (but I'd prefer to do it after this).
>>
>> board/google/gru/gru.c | 54 ++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 54 insertions(+)
next prev parent reply other threads:[~2021-12-07 20:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 17:39 [PATCH 0/4] rockchip: Improve support for Bob chromebook and add support for Kevin Alper Nebi Yasak
2021-11-25 17:39 ` [PATCH 1/4] rockchip: gru: Set up SoC IO domain registers Alper Nebi Yasak
2021-12-03 3:31 ` Simon Glass
2021-12-07 20:31 ` Alper Nebi Yasak [this message]
2021-12-09 2:32 ` Simon Glass
2021-12-09 20:56 ` Alper Nebi Yasak
2021-11-25 17:39 ` [PATCH 2/4] rockchip: gru: Add more devicetree settings Alper Nebi Yasak
2021-11-25 17:39 ` [PATCH 3/4] rockchip: bob: Enable more configs Alper Nebi Yasak
2021-11-25 17:39 ` [PATCH 4/4] rockchip: rk3399: Add support for chromebook_kevin Alper Nebi Yasak
2021-12-03 3:31 ` Simon Glass
2021-12-07 20:53 ` Alper Nebi Yasak
2021-12-15 3:27 ` Simon Glass
2021-12-01 14:23 ` [PATCH 0/4] rockchip: Improve support for Bob chromebook and add support for Kevin Peter Robinson
2021-12-03 3:31 ` Simon Glass
2021-12-03 12:19 ` Peter Robinson
2021-12-03 20:13 ` Simon Glass
2021-12-07 22:21 ` Alper Nebi Yasak
2021-12-08 9:31 ` Peter Robinson
2021-12-13 21:55 ` Alper Nebi Yasak
2021-12-03 3:31 ` Simon Glass
2021-12-07 20:49 ` Alper Nebi Yasak
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=69a6472c-2cae-f744-2d54-6f3cb195efce@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=alexandre.vicenzi@suse.com \
--cc=andre.przywara@arm.com \
--cc=christianshewitt@gmail.com \
--cc=email2tema@gmail.com \
--cc=festevam@denx.de \
--cc=hanetzer@startmail.com \
--cc=hs@denx.de \
--cc=jagan@amarulasolutions.com \
--cc=jbx6244@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=narmstrong@baylibre.com \
--cc=pbrobinson@gmail.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=tharvey@gateworks.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