From: Johan Jonker <jbx6244@gmail.com>
To: Simon Glass <sjg@chromium.org>
Cc: kever.yang@rock-chips.com, philipp.tomsich@vrull.eu,
u-boot@lists.denx.de, w.egorov@phytec.de, hl@rock-chips.com,
jagan@amarulasolutions.com, heiko@sntech.de
Subject: Re: [PATCH v2 12/12] rockchip: fix boot_devices constants
Date: Thu, 3 Mar 2022 15:37:49 +0100 [thread overview]
Message-ID: <d69824ff-a728-063e-e993-3dbed5a9c98f@gmail.com> (raw)
In-Reply-To: <CAPnjgZ0gtNr55QUWoDTULUC_r8t9F8zCgUeVr8kBrSb9RgspQg@mail.gmail.com>
Hi Simon,
Thank you for your test report.
As I don't always have the hardware, could the board maintainers help me
identify u-boot specific property differences with Linux that need to be
moved to a dtsi file.
Will send a new serie with fixes.
Johan
===
After I sync rk3288.dtsi I get this warning.
fdt64_t is generated by a script and is not something that I can update
the regmap_init_mem_plat function for.
Any advice here?
ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make chromebook_jerry_defconfig
CC spl/drivers/ram/rockchip/sdram_rk3288.o
drivers/ram/rockchip/sdram_rk3288.c: In function ‘conv_of_plat’:
drivers/ram/rockchip/sdram_rk3288.c:1032:41: warning: passing argument 2
of ‘regmap_init_mem_plat’ from incompatible pointer type
[-Wincompatible-pointer-types]
ret = regmap_init_mem_plat(dev, of_plat->reg,
~~~~~~~^~~~~
In file included from drivers/ram/rockchip/sdram_rk3288.c:18:
include/regmap.h:391:58: note: expected ‘fdt_val_t *’ {aka ‘unsigned int
*’} but argument is of type ‘fdt64_t *’ {aka ‘long long unsigned int *’}
int regmap_init_mem_plat(struct udevice *dev, fdt_val_t *reg, int count,
On 3/3/22 04:37, Simon Glass wrote:
> Hi Johan,
>
> On Mon, 28 Feb 2022 at 18:48, Johan Jonker <jbx6244@gmail.com> wrote:
>>
>> The DT node name pattern in mmc-controller.yaml for mmc
>> is "^mmc(@.*)?$". The Rockchip mmc nodes have been synced
>> with Linux, so update the boot_devices constants as well.
>>
>> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
>> Reviewed-by: Simon Glass <sjg@chromium.org>
>> ---
>> arch/arm/mach-rockchip/rk3188/rk3188.c | 4 ++--
>> arch/arm/mach-rockchip/rk322x/rk322x.c | 4 ++--
>> arch/arm/mach-rockchip/rk3288/rk3288.c | 4 ++--
>> arch/arm/mach-rockchip/rk3328/rk3328.c | 4 ++--
>> arch/arm/mach-rockchip/rk3368/rk3368.c | 4 ++--
>> 5 files changed, 10 insertions(+), 10 deletions(-)
>
> I tested this series on snow and it seems fine.
>
> I tried it on jerry and got:
>
> DRAM init failed: -19
noc: syscon@ffac0000 {
compatible = "rockchip,rk3288-noc", "syscon";
reg = <0x0 0xffac0000 0x0 0x2000>;
Forgot something. Does that help or is there more that needs to be fixed?
==> u-boot,dm-pre-reloc;
};
TODO: Must change/update dmc/noc reg size when I sync rk3288.dtsi.
>
> It also seemed fine on bob although my display is not coming up, for
> different reasons.
In SPL or full U-boot?
rk3288-veyron-chromebook.dtsi:
aliases {
i2c20 = &i2c_tunnel;
video0 = &vopl;
video1 = &vopb;
};
Is this video alias something U-boot specific?
Fixing U-boot video is beyond my U-boot knowledge.
>
> Regards
>
> Simon
next prev parent reply other threads:[~2022-03-03 14:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 1:47 [PATCH v2 01/12] rockchip: rk3228-power: sync power domain dt-binding header from Linux Johan Jonker
2022-03-01 1:47 ` [PATCH v2 02/12] rockchip: rk3228-cru: sync the clock " Johan Jonker
2022-03-01 1:47 ` [PATCH v2 03/12] arm: dts: rockchip: move all rk322x u-boot specific properties in separate dtsi files Johan Jonker
2022-03-01 1:47 ` [PATCH v2 04/12] arm: dts: rockchip: sync rk322x.dtsi from Linux Johan Jonker
2022-03-01 1:47 ` [PATCH v2 05/12] arm: dts: rockchip: sync rk3229-evb.dts " Johan Jonker
2022-03-01 1:47 ` [PATCH v2 06/12] rockchip: rk3288-power: sync power domain dt-binding header " Johan Jonker
2022-03-01 1:47 ` [PATCH v2 07/12] rockchip: rk3288-cru: sync the clock " Johan Jonker
2022-03-01 1:47 ` [PATCH v2 08/12] arm: dts: rockchip: move all rk3288 u-boot specific properties in separate dtsi files Johan Jonker
2022-03-01 1:47 ` [PATCH v2 09/12] arm: dts: rockchip: sync rk3288.dtsi from Linux Johan Jonker
2022-03-01 1:47 ` [PATCH v2 10/12] arm: dts: rockchip: sync rk3288 DT boards " Johan Jonker
2022-03-01 1:47 ` [PATCH v2 11/12] arm: dts: rockchip: sync rk3288-veyron DT " Johan Jonker
2022-03-01 1:47 ` [PATCH v2 12/12] rockchip: fix boot_devices constants Johan Jonker
2022-03-03 3:37 ` Simon Glass
2022-03-03 14:37 ` Johan Jonker [this message]
2022-03-03 19:00 ` Johan Jonker
2022-03-12 2:25 ` Simon Glass
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=d69824ff-a728-063e-e993-3dbed5a9c98f@gmail.com \
--to=jbx6244@gmail.com \
--cc=heiko@sntech.de \
--cc=hl@rock-chips.com \
--cc=jagan@amarulasolutions.com \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=w.egorov@phytec.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