When OF_LIVE flag is enabled on a 64 bits platform, there is an
issue when dev_read_addr() is called and need to perform an address
translation using __of_translate_address().
In case of error, __of_translate_address() return's value is OF_BAD_ADDR
(wich is defined in include/dm/of.h to ((u64)-1)
Hi Simon
On 12/24/21 2:17 PM, Simon Glass wrote:
> Hi Patrice,
>
> On Thu, 23 Dec 2021 at 09:09, Patrice Chotard
> wrote:
>>
>> When OF_LIVE flag is enabled on a 64 bits platform, there is an
>> issue when dev_read_addr() is called and need to perform an address
>> translation using __of_transla
Hi
> -Original Message-
> From: Simon Glass
> Sent: Tuesday, December 28, 2021 2:03 PM
> To: Gaurav Jain
> Cc: U-Boot Mailing List ; Stefano Babic
> ; Fabio Estevam ; Peng Fan
> ; Priyanka Jain ; Ye Li
> ; Horia Geanta ; Ji Luo
> ; Franck Lenormand ; Silvano Di
> Ninno ; Sahil Malhotra ;
On Sun, Jan 2, 2022 at 7:36 PM Markus Koch wrote:
>
> NXP's mEMAC reference manual, Chapter 6.5.5 "MDIO Ethernet Management
> Interface usage", specifies to poll the BSY (0) bit in the CFG (we call
> it CTL) register to wait until a transaction has finished, not bit 31 in
> the data register.
>
>
On Mon, Jan 3, 2022 at 2:32 PM Adam Ford wrote:
>
>
>
> On Mon, Jan 3, 2022 at 10:20 PM Tim Harvey wrote:
>>
>> On Thu, Dec 23, 2021 at 6:08 AM Adam Ford wrote:
>> >
>> > The imx8mm and imx8mn appear compatible with imx7d-usb
>> > flags in the OTG driver. If the dr_mode is defined as
>> > host
Dear Sean,
On 11/24/21 5:03 AM, Sean Anderson wrote:
> This series ports some of the patches from fsl_esdhc to fsl_esdhc_imx.
> Because these drivers share a common lineage, many of these patches
> apply with minor changes. For each one, I have noted the originating
> commit in the style of linux
On Mon, Jan 3, 2022 at 10:20 PM Tim Harvey wrote:
> On Thu, Dec 23, 2021 at 6:08 AM Adam Ford wrote:
> >
> > The imx8mm and imx8mn appear compatible with imx7d-usb
> > flags in the OTG driver. If the dr_mode is defined as
> > host or peripheral, the device appears to operate correctly,
> > howe
On Thu, Dec 23, 2021 at 6:08 AM Adam Ford wrote:
>
> The imx8mm and imx8mn appear compatible with imx7d-usb
> flags in the OTG driver. If the dr_mode is defined as
> host or peripheral, the device appears to operate correctly,
> however the auto host/peripheral detection results in an error.
>
>
NXP's mEMAC reference manual, Chapter 6.5.5 "MDIO Ethernet Management
Interface usage", specifies to poll the BSY (0) bit in the CFG (we call
it CTL) register to wait until a transaction has finished, not bit 31 in
the data register.
In the Linux kernel, this has already been fixed in commit 26eee
Gentle ping. Can we get this merged?
On 11/23/21 14:42, Ariel D'Alessandro wrote:
Changes in v2:
* Properly added MAINTAINERS entry.
* Fixed binman configuration.
* Picked device tree from kernel.
* Removed CONFIG_SPL_BUILD anti-pattern in board config.
* Removed downstream stuff in bootargs.
*
Gentle ping. Can we get this merged?
On 11/23/21 13:33, Ariel D'Alessandro wrote:
Changes in v6:
* Fixed typo in documentation.
* Removed downstream config option IMX8M_BOARD_INIT_DRAM.
Changes in v5:
* Fixed documentation.
Changes in v4:
* Added board documentation.
* Cleaned up board config.
Hi Simon,
On 12/28/21 9:32 AM, Simon Glass wrote:
On Tue, 14 Dec 2021 at 09:57, Patrick Delaunay
wrote:
This converts the following to Kconfig:
CONFIG_AT91_EFLASH
Signed-off-by: Patrick Delaunay
---
arch/arm/mach-at91/Kconfig | 8
configs/ethernut5_defconfig | 2 +-
incl
Hi Quentin,
Am Montag, 3. Januar 2022, 13:26:09 CET schrieb Quentin Schulz:
> Hi Heiko,
>
> On 12/26/21 13:45, Heiko Stuebner wrote:
> > The rk3399-puma board needs a 950mV vdd_log to work stable.
> > This was already added in
> > commit 77012e79ffc3 ("rockchip: rk3399-puma: Set VDD_LOG to 950 mV
By default the Model information from DT is printed:
CPU: Freescale i.MX6SX rev1.2 996 MHz (running at 792 MHz)
CPU: Extended Commercial temperature grade (-20C to 105C) at 63C
Reset cause: POR
Model: UDOO Neo Basic
Board: UDOO Neo FULL
I2C: ready
As the udoo basic DT is used, such output m
Currently, the board model is not printed correctly:
Board: UDOO Neo UNDEFINED
Read the model type in SPL and store it the internal OCRAM, so that
U-Boot proper can retrieve it correctly.
Signed-off-by: Fabio Estevam
---
This applies on top of Peter's series:
https://lore.kernel.org/all/2021122
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
Allow device trees to be reused between Linux and U-Boot.
The source for these device trees is linux-next as of commit
bd8a9cd624c6 ("arm64: dts: ls1028a-rdb: update copyright"), which was
chosen because some changes needed to be done to the Linux DTs
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
Reuse the scheme implemented by the Kontron SL28 boards in commit
d08011d7f9b4 ("arm: dts: ls1028a: disable the PCIe controller by
default") and move the 'status = "okay"' lines for the PCIe controllers
inside a separate U-Boot dtsi for the LS1028A-RD
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
Now that all in-tree boards have been converted to the compatible
strings from Linux, delete the support for the ad-hoc "pcf2127-rtc"
one.
Cc: Simon Glass
Signed-off-by: Vladimir Oltean
Reviewed-by: Simon Glass
Reviewed-by: Michael Walle
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
During the LS1028A-RDB sync with Linux device trees, it was observed
that the same RTC is present on the two boards, and the wrong
compatible
string is used in both places. This change updates the RTC from the
LX2160A-RDB to use the compatible strin
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
During this board's sync with Linux device trees, it was observed that
it doesn't use the same compatible string for the RTC node as in
U-Boot.
This change makes the RTC compatible strings match, for a smoother
sync.
Signed-off-by: Vladimir Oltean
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
The LS1028A-QDS board won't be synced with the Linux device trees right
now, since those are currently still in progress (Ethernet is missing).
However, while we're at converting the RDB, it can be observed that the
same RTC is present on the two boa
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
During the LS1028A-RDB sync with Linux device trees, it was observed
that the same RTC is present on the two boards, and the wrong
compatible
string is used in both places. This change updates the RTC from the
LX2160A-QDS to use the compatible strin
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
During the LS1028A-RDB sync with Linux device trees, it was observed
that the same RTC is present on the two boards, and the wrong
compatible
string is used in both places. This change updates the RTC from the
LS1088A-RDB to use the compatible strin
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
During the LS1028A-RDB sync with Linux device trees, it was observed
that the same RTC is present on the two boards, and the wrong
compatible
string is used in both places. This change updates the RTC from the
LS1088A-QDS to use the compatible strin
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
Allow this driver to be used by boards which inherit their device trees
from Linux. Compatibility is temporarily retained with the old
compatible string which is U-Boot specific, and will be removed after a
few changes.
Cc: Simon Glass
Signed-off-by
Am 2022-01-03 13:47, schrieb Vladimir Oltean:
This seems to be very similar to the already existing PCA9547, save for
the fact that it supports 0.8V and doesn't support 5V. In fact, it is
so
similar to the PCA9547 that the NXP LS1028A-RDB board has been driving
this chip using a "nxp,pca9547" c
Hi Sean,
On 2021-12-30 08:21, Sean Anderson wrote:
On 12/29/21 8:35 AM, Angus Ainslie wrote:
Hi Sean,
On 2021-12-28 08:59, Sean Anderson wrote:
Hi Angus,
NXP's mfgtool queies the mmc blocksize and splits a sparse image
into
blocksize size pieces for the upload.
It's still not clear to me
The commit in the Fixes: tag below broke traffic through switch ports
where the SERDES protocol requires in-band autoneg and this requirement
isn't described in the device tree: SGMII, QSGMII, USXGMII (with
2500Base-X, in-band autoneg isn't supported).
The LS1028A-QDS boards are not yet ready for
Allow device trees to be reused between Linux and U-Boot.
The source for these device trees is linux-next as of commit
bd8a9cd624c6 ("arm64: dts: ls1028a-rdb: update copyright"), which was
chosen because some changes needed to be done to the Linux DTs too,
before they could be shared:
https://lore.
There is no I2C peripheral on these buses on the reference design board,
and the Linux device tree does not enable them either.
Signed-off-by: Vladimir Oltean
Reviewed-by: Priyanka Jain
---
v1->v3: none
arch/arm/dts/fsl-ls1028a-rdb.dts | 28
1 file changed, 28 dele
There is no SPI peripheral on the LS1028A-RDB, therefore no reason to
enable these nodes in the U-Boot device tree (and Linux does not enable
them either).
Signed-off-by: Vladimir Oltean
Reviewed-by: Priyanka Jain
---
v1->v3: none
arch/arm/dts/fsl-ls1028a-rdb.dts | 12
1 file chan
Reuse the scheme implemented by the Kontron SL28 boards in commit
d08011d7f9b4 ("arm: dts: ls1028a: disable the PCIe controller by
default") and move the 'status = "okay"' lines for the PCIe controllers
inside a separate U-Boot dtsi for the LS1028A-RDB board. This way, the
existing Linux device tre
The nodes in the NXP LS1028A-RDB device tree are out of order, regroup
them alphabetically to have a simple delta when the Linux device tree is
brought in.
Signed-off-by: Vladimir Oltean
Reviewed-by: Priyanka Jain
---
v1->v3: none
arch/arm/dts/fsl-ls1028a-rdb.dts | 110 +++-
In a bit of a blunder, the blamed commit in the Fixes: tag below made
the mscc_felix switch driver look at the 'managed = "in-band-status"'
device tree property, forgetting that the U-Boot device tree had not
been updated to include that property, whereas the Linux one does.
The switch is therefor
During the LS1028A-RDB sync with Linux device trees, it was observed
that the same RTC is present on the two boards, and the wrong compatible
string is used in both places. This change updates the RTC from the
LX2160A-RDB to use the compatible string that was established in Linux.
Signed-off-by: V
Now that all in-tree boards have been converted to the compatible
strings from Linux, delete the support for the ad-hoc "pcf2127-rtc" one.
Cc: Simon Glass
Signed-off-by: Vladimir Oltean
Reviewed-by: Simon Glass
---
v1->v3: none
drivers/rtc/pcf2127.c | 1 -
1 file changed, 1 deletion(-)
diff
During this board's sync with Linux device trees, it was observed that
it doesn't use the same compatible string for the RTC node as in U-Boot.
This change makes the RTC compatible strings match, for a smoother sync.
Signed-off-by: Vladimir Oltean
---
v1->v2: patch is new
v2->v3: none
arch/arm/
The LS1028A-QDS board won't be synced with the Linux device trees right
now, since those are currently still in progress (Ethernet is missing).
However, while we're at converting the RDB, it can be observed that the
same RTC is present on the two boards, and the wrong compatible string
is used in
During the LS1028A-RDB sync with Linux device trees, it was observed
that the same RTC is present on the two boards, and the wrong compatible
string is used in both places. This change updates the RTC from the
LX2160A-QDS to use the compatible string that was established in Linux.
Signed-off-by: V
During the LS1028A-RDB sync with Linux device trees, it was observed
that the same RTC is present on the two boards, and the wrong compatible
string is used in both places. This change updates the RTC from the
LS1088A-RDB to use the compatible string that was established in Linux.
Signed-off-by: V
Allow this driver to be used by boards which inherit their device trees
from Linux. Compatibility is temporarily retained with the old
compatible string which is U-Boot specific, and will be removed after a
few changes.
Cc: Simon Glass
Signed-off-by: Vladimir Oltean
Reviewed-by: Simon Glass
---
The changes were intended to be minimal, but unfortunately I discovered
some other stuff as well:
- we need to make some changes to the compatible strings of RTC devices
and I2C muxes. This has ramifications to other NXP boards which were
also updated.
- I broke Ethernet on LS1028A boards throu
During the LS1028A-RDB sync with Linux device trees, it was observed
that the same RTC is present on the two boards, and the wrong compatible
string is used in both places. This change updates the RTC from the
LS1088A-QDS to use the compatible string that was established in Linux.
Signed-off-by: V
This seems to be very similar to the already existing PCA9547, save for
the fact that it supports 0.8V and doesn't support 5V. In fact, it is so
similar to the PCA9547 that the NXP LS1028A-RDB board has been driving
this chip using a "nxp,pca9547" compatible string.
Create a new compatible for the
> From: Ilias Apalodimas
> Date: Mon, 3 Jan 2022 14:07:37 +0200
>
> U-Boot, in some occasions, injects a 'kaslr-seed' property on the /chosen
> node. That would be problematic in case we want to measure the DTB we
> install in the config table, since it would change across reboots.
>
> The Lin
Hi Heiko,
On 12/26/21 13:45, Heiko Stuebner wrote:
The rk3399-puma board needs a 950mV vdd_log to work stable.
This was already added in
commit 77012e79ffc3 ("rockchip: rk3399-puma: Set VDD_LOG to 950 mV")
but lost again with
commit 167efc2c7a46 ("arm64: dts: rk3399: Sync v5.7-rc1 from Linux")
On Mon, 3 Jan 2022 at 13:04, wrote:
>
> From: Quentin Schulz
>
> Philipp does not work at Theobroma Systems anymore so let's swap
> Philipp's address with mine.
>
> Cc: Philipp Tomsich
> Cc: Quentin Schulz
> Signed-off-by: Quentin Schulz
Reviewed-by: Philipp Tomsich
U-Boot, in some occasions, injects a 'kaslr-seed' property on the /chosen
node. That would be problematic in case we want to measure the DTB we
install in the config table, since it would change across reboots.
The Linux kernel EFI-stub completely ignores it and only relies on
EFI_RNG_PROTOCOL fo
From: Quentin Schulz
Philipp does not work at Theobroma Systems anymore so let's swap
Philipp's address with mine.
Cc: Philipp Tomsich
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
---
v2: add commit log so that the commit can be merged
@Philipp, I can update your mail address if you wan
Hi Sven,
On Sun, Jan 2, 2022 at 4:38 PM Sven Schwermer wrote:
>
> Similar to what has been done before with c5437e5b for u-boot proper, we
> enable the SMP bit for SPL as well. This is necessary when SDP booting
> straight into Linux, i.e. falcon boot. When SDP boot mode is active, the
> ROM code
On Thu, Dec 30, 2021 at 01:55:15AM +0800, Xiang W wrote:
> 在 2021-12-29星期三的 17:23 +0800，Leo Liang写道：
> > Hi Xiang,
> > On Wed, Dec 22, 2021 at 07:32:53AM +0800, Xiang W wrote:
> > > Various specifications of riscv allow the number of hart to be
> > > greater than 32. The limit of 32 is determined b
Dear AKASHI,
On 12/10/21 3:49 PM, AKASHI Takahiro wrote:
> Every time a mmc bus/port is scanned and a new device is detected,
> we want to call device_probe() as it will give us a chance to run
> additional post-processings for some purposes.
>
> In particular, support for creating partitions on
Hi Jaime,
You made a typo on Jagan's address, you might need to resend.
The title does not look correct, maybe you miss a word after Octal. And
is it something Macronix specific? I believe this is generic and you
can drop "Macronix" (the second occurrence) from the title.
jaimeliao...@gmail.com
Hello all,
For my question below, I later found I didn't load enough bytes for the FIT
image (that's why it could find the configuration node).
Now because our FPGA board has only 8MB fake RAM for now, I loaded FIT
(about 5.7MB. containing kernel Image, fdt and initramfs.cpio.gz) to
0x8000_ (s
54 matches
Mail list logo
