[PATCH 1/2] of: base: add new barebox,status property

[PATCH 1/2] of: base: add new barebox,status property

[Ahmad Fatoum]

I am confronted with an occasional hang on the Radxa Rock 3A during
PCI probe. The board has no PCI devices connected.

This hang doesn't happen in Linux and doesn't happen on the QNAP
TS433-eU, which is also RK3568, but actually has PCIe devices, which are
probed normally.

For such purposes, add a barebox,status property as setting the status
to disabled, would impact Linux as well if barebox were to pass along
its own device tree, e.g. when installing the UEFI device tree
configuration table.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
v1 -> v2:
  - rework to make clearer when to use the new property. (Marco)
  - add example with UEFI device tree configuration table into commit
    message (Marco)
---
 .../devicetree/bindings/barebox/barebox,status.rst | 14 ++++++++++++++
 drivers/of/base.c                                  |  4 +++-
 2 files changed, 17 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/devicetree/bindings/barebox/barebox,status.rst

diff --git a/Documentation/devicetree/bindings/barebox/barebox,status.rst b/Documentation/devicetree/bindings/barebox/barebox,status.rst
new file mode 100644
index 000000000000..03f484cdcfe1
--- /dev/null
+++ b/Documentation/devicetree/bindings/barebox/barebox,status.rst
@@ -0,0 +1,14 @@
+barebox,status property
+=======================
+
+barebox interprets ``barebox,status`` the same as it does ``status``,
+but gives the barebox-specific property precedence if both exist.
+
+The purpose of this property is to keep the ``status`` property of the
+upstream DT, imported from Linux, untouched.
+
+Using ``barebox,status`` may be necessary to temporarily workaround
+barebox drivers that misbehave on a given board; Disabling the driver
+may be undesirable if it can handle other instances of the same device
+on the board or if barebox is being built to support other boards
+at the same time, where the driver functions correctly.
diff --git a/drivers/of/base.c b/drivers/of/base.c
index 54fd458bd9a1..4e83a757a4e9 100644
--- a/drivers/of/base.c
+++ b/drivers/of/base.c
@@ -2149,7 +2149,9 @@ int of_device_is_available(const struct device_node *device)
 	const char *status;
 	int statlen;
 
-	status = of_get_property(device, "status", &statlen);
+	status = of_get_property(device, "barebox,status", &statlen);
+	if (status == NULL)
+		status = of_get_property(device, "status", &statlen);
 	if (status == NULL)
 		return 1;
 
-- 
2.47.3

[PATCH 2/2] arm: dts: rk356x: rock3a: disable pcie3x2

[Ahmad Fatoum]

The board hangs occasionally on PCI probe after:

  phy7: lane number 0, val 1

On other boots, it continues to:

  rockchip-dw-pcie 3c0800000.pcie@fe280000.of: Phy link never came up

In both cases, the hang affects the second PCIe host controller
to probe and the first probe never hangs:

  rockchip-dw-pcie 3c0000000.pcie@fe260000.of: Phy link never came up

This hang happens on the very first read access to the PCI controller
at register PCIE_ATU_VIEWPORT. Reading Linux code, the first access
seems to be to PCIE_VERSION_NUMBER (0x8F8), but accessing that in
barebox equally hangs from time to time.

My board doesn't have any PCIe devices connected and this hang
doesn't happen in Linux and doesn't happen on the QNAP
TS433-eU, which is also RK3568, but actually has PCIe devices, which are
probed normally.

Disable the device in barebox, so the board is usable with
rockchip_v8_defconfig, which enables the PCI driver.
barebox,status is used, so the Linux device tree is not affected.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
v1 -> v2:
  - add short comment explaining why we disable this device in particular
---
 arch/arm/dts/rk3568-rock-3a.dts | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/arch/arm/dts/rk3568-rock-3a.dts b/arch/arm/dts/rk3568-rock-3a.dts
index bcbfab14a580..4834a85b367a 100644
--- a/arch/arm/dts/rk3568-rock-3a.dts
+++ b/arch/arm/dts/rk3568-rock-3a.dts
@@ -55,3 +55,8 @@ environment_sd: partition@408000 {
 		};
 	};
 };
+
+/* Device driver probe occasionally hangs, but pcie2x1 is fine... */
+&pcie3x2 {
+	barebox,status = "disabled";
+};
-- 
2.47.3

Re: [PATCH 1/2] of: base: add new barebox,status property

[Ahmad Fatoum]

Hi,

sorry missed adding the v2..

On 1/21/26 12:31 PM, Ahmad Fatoum wrote:
> I am confronted with an occasional hang on the Radxa Rock 3A during
> PCI probe. The board has no PCI devices connected.
> 
> This hang doesn't happen in Linux and doesn't happen on the QNAP
> TS433-eU, which is also RK3568, but actually has PCIe devices, which are
> probed normally.
> 
> For such purposes, add a barebox,status property as setting the status
> to disabled, would impact Linux as well if barebox were to pass along
> its own device tree, e.g. when installing the UEFI device tree
> configuration table.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> v1 -> v2:
>   - rework to make clearer when to use the new property. (Marco)
>   - add example with UEFI device tree configuration table into commit
>     message (Marco)
> ---
>  .../devicetree/bindings/barebox/barebox,status.rst | 14 ++++++++++++++
>  drivers/of/base.c                                  |  4 +++-
>  2 files changed, 17 insertions(+), 1 deletion(-)
>  create mode 100644 Documentation/devicetree/bindings/barebox/barebox,status.rst
> 
> diff --git a/Documentation/devicetree/bindings/barebox/barebox,status.rst b/Documentation/devicetree/bindings/barebox/barebox,status.rst
> new file mode 100644
> index 000000000000..03f484cdcfe1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/barebox/barebox,status.rst
> @@ -0,0 +1,14 @@
> +barebox,status property
> +=======================
> +
> +barebox interprets ``barebox,status`` the same as it does ``status``,
> +but gives the barebox-specific property precedence if both exist.
> +
> +The purpose of this property is to keep the ``status`` property of the
> +upstream DT, imported from Linux, untouched.
> +
> +Using ``barebox,status`` may be necessary to temporarily workaround
> +barebox drivers that misbehave on a given board; Disabling the driver
> +may be undesirable if it can handle other instances of the same device
> +on the board or if barebox is being built to support other boards
> +at the same time, where the driver functions correctly.
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 54fd458bd9a1..4e83a757a4e9 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -2149,7 +2149,9 @@ int of_device_is_available(const struct device_node *device)
>  	const char *status;
>  	int statlen;
>  
> -	status = of_get_property(device, "status", &statlen);
> +	status = of_get_property(device, "barebox,status", &statlen);
> +	if (status == NULL)
> +		status = of_get_property(device, "status", &statlen);
>  	if (status == NULL)
>  		return 1;
>  

-- 
Pengutronix e.K.                  |                             |
Steuerwalder Str. 21              | http://www.pengutronix.de/  |
31137 Hildesheim, Germany         | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

Re: [PATCH 1/2] of: base: add new barebox,status property

[Marco Felsch]

On 26-01-21, Ahmad Fatoum wrote:
> I am confronted with an occasional hang on the Radxa Rock 3A during
> PCI probe. The board has no PCI devices connected.
> 
> This hang doesn't happen in Linux and doesn't happen on the QNAP
> TS433-eU, which is also RK3568, but actually has PCIe devices, which are
> probed normally.
> 
> For such purposes, add a barebox,status property as setting the status
> to disabled, would impact Linux as well if barebox were to pass along
> its own device tree, e.g. when installing the UEFI device tree
> configuration table.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>

Reviewed-by: Marco Felsch <m.felsch@pengutronix.de>

> ---
> v1 -> v2:
>   - rework to make clearer when to use the new property. (Marco)
>   - add example with UEFI device tree configuration table into commit
>     message (Marco)
> ---
>  .../devicetree/bindings/barebox/barebox,status.rst | 14 ++++++++++++++
>  drivers/of/base.c                                  |  4 +++-
>  2 files changed, 17 insertions(+), 1 deletion(-)
>  create mode 100644 Documentation/devicetree/bindings/barebox/barebox,status.rst
> 
> diff --git a/Documentation/devicetree/bindings/barebox/barebox,status.rst b/Documentation/devicetree/bindings/barebox/barebox,status.rst
> new file mode 100644
> index 000000000000..03f484cdcfe1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/barebox/barebox,status.rst
> @@ -0,0 +1,14 @@
> +barebox,status property
> +=======================
> +
> +barebox interprets ``barebox,status`` the same as it does ``status``,
> +but gives the barebox-specific property precedence if both exist.
> +
> +The purpose of this property is to keep the ``status`` property of the
> +upstream DT, imported from Linux, untouched.
> +
> +Using ``barebox,status`` may be necessary to temporarily workaround
> +barebox drivers that misbehave on a given board; Disabling the driver
> +may be undesirable if it can handle other instances of the same device
> +on the board or if barebox is being built to support other boards
> +at the same time, where the driver functions correctly.
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 54fd458bd9a1..4e83a757a4e9 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -2149,7 +2149,9 @@ int of_device_is_available(const struct device_node *device)
>  	const char *status;
>  	int statlen;
>  
> -	status = of_get_property(device, "status", &statlen);
> +	status = of_get_property(device, "barebox,status", &statlen);
> +	if (status == NULL)
> +		status = of_get_property(device, "status", &statlen);
>  	if (status == NULL)
>  		return 1;
>  
> -- 
> 2.47.3
> 
> 

-- 
#gernperDu 
#CallMeByMyFirstName

Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |

Re: [PATCH 2/2] arm: dts: rk356x: rock3a: disable pcie3x2

[Marco Felsch]

On 26-01-21, Ahmad Fatoum wrote:
> The board hangs occasionally on PCI probe after:
> 
>   phy7: lane number 0, val 1
> 
> On other boots, it continues to:
> 
>   rockchip-dw-pcie 3c0800000.pcie@fe280000.of: Phy link never came up
> 
> In both cases, the hang affects the second PCIe host controller
> to probe and the first probe never hangs:
> 
>   rockchip-dw-pcie 3c0000000.pcie@fe260000.of: Phy link never came up
> 
> This hang happens on the very first read access to the PCI controller
> at register PCIE_ATU_VIEWPORT. Reading Linux code, the first access
> seems to be to PCIE_VERSION_NUMBER (0x8F8), but accessing that in
> barebox equally hangs from time to time.
> 
> My board doesn't have any PCIe devices connected and this hang
> doesn't happen in Linux and doesn't happen on the QNAP
> TS433-eU, which is also RK3568, but actually has PCIe devices, which are
> probed normally.
> 
> Disable the device in barebox, so the board is usable with
> rockchip_v8_defconfig, which enables the PCI driver.
> barebox,status is used, so the Linux device tree is not affected.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>

Reviewed-by: Marco Felsch <m.felsch@pengutronix.de>

Re: [PATCH 2/2] arm: dts: rk356x: rock3a: disable pcie3x2

[Ahmad Fatoum]

Hi,

On 1/21/26 11:15, Marco Felsch wrote:
> On 26-01-21, Ahmad Fatoum wrote:
>> Hello Marco,
>>
>> On 1/21/26 10:16, Marco Felsch wrote:
>>> On 26-01-21, Ahmad Fatoum wrote:
>>>> With barebox as EFI loader, we always install the barebox DT in a configuration
>>>> table and leaves it to grub or whatever to decide whether it wants to use it or
>>>> if it wants to use another DT it finds itself.
>>>
>>> Ah, thanks for the explanation :) this wasn't clear to me. Maybe it's
>>> worth a comment when to use this within the barebox,status description.
>>
>> Whether the barebox DT is used for Linux or not is inconsequential though.
>> We want the barebox DT to be always _usable_ for Linux, even if it's not
>> used. I thus intentionally didn't list when barebox passes along its own
>> DT in the binding doc.
> 
> Get your point but at least your patch here wasn't clear to me in the
> first place. Therefore my question :) Now with the new barebox,status it
> isn't clear when to use this.
> 
> This could be sovled either via policy like: use barebox,status if
> you're going to toogle the status of an upstream-dt within the barebox.

The binding in patch 1 documents:

Use this property only for devices for which barebox has a driver, but
that barebox should not be probing on a per-board basis.

Do you have a suggestion how to make this clearer?

> Or via a comment within the DT to make it clear, why barebox,status is
> used.

I can also add a comment in addition to the commit message.

>> Normally, you would disable drivers that don't work for board, but we can't do that in
>> a multi defconfig, so we need to disable the device on a per-board basis.
>>
>> This is different than secure-status, where device availability is actually
>> dependent on the security mode of the system.
> 
> Right, I just wanted to point out, that downstream bindings or
> downstream behaviors hit us hard in the past. That beeing said, I don't
> see a problem for barebox,status.

Many of these issues would have been avoided had we used a barebox, prefix.

Cheers,
Ahmad


> 
> Regards,
>   Marco
> 
> 
>>
>> Cheers,
>> Ahmad
>>
>>>
>>>> The support for the Android fastboot's protocol boot command also doesn't pass
>>>> a DT and expects the bootloader to pass its.
>>>
>>> Good to know :)
>>>
>>> Thanks,
>>>   Marco
>>>
>>>>
>>>> Cheers,
>>>> Ahmad
>>>>>
>>>>> Regards,
>>>>>   Marco
>>>>>
>>>>>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>>>>>> ---
>>>>>>  arch/arm/dts/rk3568-rock-3a.dts | 4 ++++
>>>>>>  1 file changed, 4 insertions(+)
>>>>>>
>>>>>> diff --git a/arch/arm/dts/rk3568-rock-3a.dts b/arch/arm/dts/rk3568-rock-3a.dts
>>>>>> index bcbfab14a580..b7258d7e61b3 100644
>>>>>> --- a/arch/arm/dts/rk3568-rock-3a.dts
>>>>>> +++ b/arch/arm/dts/rk3568-rock-3a.dts
>>>>>> @@ -55,3 +55,7 @@ environment_sd: partition@408000 {
>>>>>>  		};
>>>>>>  	};
>>>>>>  };
>>>>>> +
>>>>>> +&pcie3x2 {
>>>>>> +	barebox,status = "disabled";
>>>>>> +};
>>>>>> -- 
>>>>>> 2.47.3
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> -- 
>>>> Pengutronix e.K.                           |                             |
>>>> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
>>>> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
>>>> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>>>>
>>>
>>
>>
>> -- 
>> Pengutronix e.K.                           |                             |
>> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
>> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
>> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>>
> 


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

Re: [PATCH 2/2] arm: dts: rk356x: rock3a: disable pcie3x2

[Marco Felsch]

On 26-01-21, Ahmad Fatoum wrote:
> Hello Marco,
> 
> On 1/21/26 10:16, Marco Felsch wrote:
> > On 26-01-21, Ahmad Fatoum wrote:
> >> With barebox as EFI loader, we always install the barebox DT in a configuration
> >> table and leaves it to grub or whatever to decide whether it wants to use it or
> >> if it wants to use another DT it finds itself.
> > 
> > Ah, thanks for the explanation :) this wasn't clear to me. Maybe it's
> > worth a comment when to use this within the barebox,status description.
> 
> Whether the barebox DT is used for Linux or not is inconsequential though.
> We want the barebox DT to be always _usable_ for Linux, even if it's not
> used. I thus intentionally didn't list when barebox passes along its own
> DT in the binding doc.

Get your point but at least your patch here wasn't clear to me in the
first place. Therefore my question :) Now with the new barebox,status it
isn't clear when to use this.

This could be sovled either via policy like: use barebox,status if
you're going to toogle the status of an upstream-dt within the barebox.

Or via a comment within the DT to make it clear, why barebox,status is
used.

> > That beeing said, is it worth tying to make it barebox unspecific and
> > try to upstream the binding. I had something like bootloader,status or
> > bl33,status in my mind.
> 
> I don't think the prospects for upstreaming are favorable. This doesn't describe
> hardware, but the fact that the barebox driver needs further work.

Good point!

> Normally, you would disable drivers that don't work for board, but we can't do that in
> a multi defconfig, so we need to disable the device on a per-board basis.
> 
> This is different than secure-status, where device availability is actually
> dependent on the security mode of the system.

Right, I just wanted to point out, that downstream bindings or
downstream behaviors hit us hard in the past. That beeing said, I don't
see a problem for barebox,status.

Regards,
  Marco


> 
> Cheers,
> Ahmad
> 
> > 
> >> The support for the Android fastboot's protocol boot command also doesn't pass
> >> a DT and expects the bootloader to pass its.
> > 
> > Good to know :)
> > 
> > Thanks,
> >   Marco
> > 
> >>
> >> Cheers,
> >> Ahmad
> >>>
> >>> Regards,
> >>>   Marco
> >>>
> >>>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> >>>> ---
> >>>>  arch/arm/dts/rk3568-rock-3a.dts | 4 ++++
> >>>>  1 file changed, 4 insertions(+)
> >>>>
> >>>> diff --git a/arch/arm/dts/rk3568-rock-3a.dts b/arch/arm/dts/rk3568-rock-3a.dts
> >>>> index bcbfab14a580..b7258d7e61b3 100644
> >>>> --- a/arch/arm/dts/rk3568-rock-3a.dts
> >>>> +++ b/arch/arm/dts/rk3568-rock-3a.dts
> >>>> @@ -55,3 +55,7 @@ environment_sd: partition@408000 {
> >>>>  		};
> >>>>  	};
> >>>>  };
> >>>> +
> >>>> +&pcie3x2 {
> >>>> +	barebox,status = "disabled";
> >>>> +};
> >>>> -- 
> >>>> 2.47.3
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >>
> >> -- 
> >> Pengutronix e.K.                           |                             |
> >> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
> >> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
> >> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
> >>
> > 
> 
> 
> -- 
> Pengutronix e.K.                           |                             |
> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
> 

-- 
#gernperDu 
#CallMeByMyFirstName

Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |

Re: [PATCH 2/2] arm: dts: rk356x: rock3a: disable pcie3x2

[Ahmad Fatoum]

Hello Marco,

On 1/21/26 10:16, Marco Felsch wrote:
> On 26-01-21, Ahmad Fatoum wrote:
>> With barebox as EFI loader, we always install the barebox DT in a configuration
>> table and leaves it to grub or whatever to decide whether it wants to use it or
>> if it wants to use another DT it finds itself.
> 
> Ah, thanks for the explanation :) this wasn't clear to me. Maybe it's
> worth a comment when to use this within the barebox,status description.

Whether the barebox DT is used for Linux or not is inconsequential though.
We want the barebox DT to be always _usable_ for Linux, even if it's not
used. I thus intentionally didn't list when barebox passes along its own
DT in the binding doc.

> That beeing said, is it worth tying to make it barebox unspecific and
> try to upstream the binding. I had something like bootloader,status or
> bl33,status in my mind.

I don't think the prospects for upstreaming are favorable. This doesn't describe
hardware, but the fact that the barebox driver needs further work.

Normally, you would disable drivers that don't work for board, but we can't do that in
a multi defconfig, so we need to disable the device on a per-board basis.

This is different than secure-status, where device availability is actually
dependent on the security mode of the system.

Cheers,
Ahmad

> 
>> The support for the Android fastboot's protocol boot command also doesn't pass
>> a DT and expects the bootloader to pass its.
> 
> Good to know :)
> 
> Thanks,
>   Marco
> 
>>
>> Cheers,
>> Ahmad
>>>
>>> Regards,
>>>   Marco
>>>
>>>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>>>> ---
>>>>  arch/arm/dts/rk3568-rock-3a.dts | 4 ++++
>>>>  1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/arch/arm/dts/rk3568-rock-3a.dts b/arch/arm/dts/rk3568-rock-3a.dts
>>>> index bcbfab14a580..b7258d7e61b3 100644
>>>> --- a/arch/arm/dts/rk3568-rock-3a.dts
>>>> +++ b/arch/arm/dts/rk3568-rock-3a.dts
>>>> @@ -55,3 +55,7 @@ environment_sd: partition@408000 {
>>>>  		};
>>>>  	};
>>>>  };
>>>> +
>>>> +&pcie3x2 {
>>>> +	barebox,status = "disabled";
>>>> +};
>>>> -- 
>>>> 2.47.3
>>>>
>>>>
>>>>
>>>
>>
>>
>> -- 
>> Pengutronix e.K.                           |                             |
>> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
>> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
>> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>>
> 


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

Re: [PATCH 2/2] arm: dts: rk356x: rock3a: disable pcie3x2

[Marco Felsch]

On 26-01-21, Ahmad Fatoum wrote:
> Hello Marco,
> 
> On 1/21/26 01:07, Marco Felsch wrote:
> > Hi Ahmad,
> > 
> > On 26-01-20, Ahmad Fatoum wrote:
> >> The board hangs occasionally on PCI probe after:
> >>
> >>   phy7: lane number 0, val 1
> >>
> >> On other boots, it continues to:
> >>
> >>   rockchip-dw-pcie 3c0800000.pcie@fe280000.of: Phy link never came up
> >>
> >> In both cases, the hang affects the second PCIe host controller
> >> to probe and the first probe never hangs:
> >>
> >>   rockchip-dw-pcie 3c0000000.pcie@fe260000.of: Phy link never came up
> >>
> >> This hang happens on the very first read access to the PCI controller
> >> at register PCIE_ATU_VIEWPORT. Reading Linux code, the first access
> >> seems to be to PCIE_VERSION_NUMBER (0x8F8), but accessing that in
> >> barebox equally hangs from time to time.
> >>
> >> My board doesn't have any PCIe devices connected and this hang
> >> doesn't happen in Linux and doesn't happen on the QNAP
> >> TS433-eU, which is also RK3568, but actually has PCIe devices, which are
> >> probed normally.
> >>
> >> Disable the device in barebox, so the board is usable with
> >> rockchip_v8_defconfig, which enables the PCI driver.
> >> barebox,status is used, so the Linux device tree is not affected.
> > 
> > The barebox internal device-tree is passed to Linux? Else we just can
> > make use of the "normal" status field since it would be not propagated
> > to Linux as well.
> 
> With barebox as EFI loader, we always install the barebox DT in a configuration
> table and leaves it to grub or whatever to decide whether it wants to use it or
> if it wants to use another DT it finds itself.

Ah, thanks for the explanation :) this wasn't clear to me. Maybe it's
worth a comment when to use this within the barebox,status description.

That beeing said, is it worth tying to make it barebox unspecific and
try to upstream the binding. I had something like bootloader,status or
bl33,status in my mind.

> The support for the Android fastboot's protocol boot command also doesn't pass
> a DT and expects the bootloader to pass its.

Good to know :)

Thanks,
  Marco

> 
> Cheers,
> Ahmad
> > 
> > Regards,
> >   Marco
> > 
> >> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> >> ---
> >>  arch/arm/dts/rk3568-rock-3a.dts | 4 ++++
> >>  1 file changed, 4 insertions(+)
> >>
> >> diff --git a/arch/arm/dts/rk3568-rock-3a.dts b/arch/arm/dts/rk3568-rock-3a.dts
> >> index bcbfab14a580..b7258d7e61b3 100644
> >> --- a/arch/arm/dts/rk3568-rock-3a.dts
> >> +++ b/arch/arm/dts/rk3568-rock-3a.dts
> >> @@ -55,3 +55,7 @@ environment_sd: partition@408000 {
> >>  		};
> >>  	};
> >>  };
> >> +
> >> +&pcie3x2 {
> >> +	barebox,status = "disabled";
> >> +};
> >> -- 
> >> 2.47.3
> >>
> >>
> >>
> > 
> 
> 
> -- 
> Pengutronix e.K.                           |                             |
> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
> 

-- 
#gernperDu 
#CallMeByMyFirstName

Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |

Re: [PATCH 2/2] arm: dts: rk356x: rock3a: disable pcie3x2

[Ahmad Fatoum]

Hello Marco,

On 1/21/26 01:07, Marco Felsch wrote:
> Hi Ahmad,
> 
> On 26-01-20, Ahmad Fatoum wrote:
>> The board hangs occasionally on PCI probe after:
>>
>>   phy7: lane number 0, val 1
>>
>> On other boots, it continues to:
>>
>>   rockchip-dw-pcie 3c0800000.pcie@fe280000.of: Phy link never came up
>>
>> In both cases, the hang affects the second PCIe host controller
>> to probe and the first probe never hangs:
>>
>>   rockchip-dw-pcie 3c0000000.pcie@fe260000.of: Phy link never came up
>>
>> This hang happens on the very first read access to the PCI controller
>> at register PCIE_ATU_VIEWPORT. Reading Linux code, the first access
>> seems to be to PCIE_VERSION_NUMBER (0x8F8), but accessing that in
>> barebox equally hangs from time to time.
>>
>> My board doesn't have any PCIe devices connected and this hang
>> doesn't happen in Linux and doesn't happen on the QNAP
>> TS433-eU, which is also RK3568, but actually has PCIe devices, which are
>> probed normally.
>>
>> Disable the device in barebox, so the board is usable with
>> rockchip_v8_defconfig, which enables the PCI driver.
>> barebox,status is used, so the Linux device tree is not affected.
> 
> The barebox internal device-tree is passed to Linux? Else we just can
> make use of the "normal" status field since it would be not propagated
> to Linux as well.

With barebox as EFI loader, we always install the barebox DT in a configuration
table and leaves it to grub or whatever to decide whether it wants to use it or
if it wants to use another DT it finds itself.

The support for the Android fastboot's protocol boot command also doesn't pass
a DT and expects the bootloader to pass its.

Cheers,
Ahmad
> 
> Regards,
>   Marco
> 
>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>> ---
>>  arch/arm/dts/rk3568-rock-3a.dts | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/arm/dts/rk3568-rock-3a.dts b/arch/arm/dts/rk3568-rock-3a.dts
>> index bcbfab14a580..b7258d7e61b3 100644
>> --- a/arch/arm/dts/rk3568-rock-3a.dts
>> +++ b/arch/arm/dts/rk3568-rock-3a.dts
>> @@ -55,3 +55,7 @@ environment_sd: partition@408000 {
>>  		};
>>  	};
>>  };
>> +
>> +&pcie3x2 {
>> +	barebox,status = "disabled";
>> +};
>> -- 
>> 2.47.3
>>
>>
>>
> 


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

Re: [PATCH 2/2] arm: dts: rk356x: rock3a: disable pcie3x2

[Marco Felsch]

Hi Ahmad,

On 26-01-20, Ahmad Fatoum wrote:
> The board hangs occasionally on PCI probe after:
> 
>   phy7: lane number 0, val 1
> 
> On other boots, it continues to:
> 
>   rockchip-dw-pcie 3c0800000.pcie@fe280000.of: Phy link never came up
> 
> In both cases, the hang affects the second PCIe host controller
> to probe and the first probe never hangs:
> 
>   rockchip-dw-pcie 3c0000000.pcie@fe260000.of: Phy link never came up
> 
> This hang happens on the very first read access to the PCI controller
> at register PCIE_ATU_VIEWPORT. Reading Linux code, the first access
> seems to be to PCIE_VERSION_NUMBER (0x8F8), but accessing that in
> barebox equally hangs from time to time.
> 
> My board doesn't have any PCIe devices connected and this hang
> doesn't happen in Linux and doesn't happen on the QNAP
> TS433-eU, which is also RK3568, but actually has PCIe devices, which are
> probed normally.
> 
> Disable the device in barebox, so the board is usable with
> rockchip_v8_defconfig, which enables the PCI driver.
> barebox,status is used, so the Linux device tree is not affected.

The barebox internal device-tree is passed to Linux? Else we just can
make use of the "normal" status field since it would be not propagated
to Linux as well.

Regards,
  Marco

> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
>  arch/arm/dts/rk3568-rock-3a.dts | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/arch/arm/dts/rk3568-rock-3a.dts b/arch/arm/dts/rk3568-rock-3a.dts
> index bcbfab14a580..b7258d7e61b3 100644
> --- a/arch/arm/dts/rk3568-rock-3a.dts
> +++ b/arch/arm/dts/rk3568-rock-3a.dts
> @@ -55,3 +55,7 @@ environment_sd: partition@408000 {
>  		};
>  	};
>  };
> +
> +&pcie3x2 {
> +	barebox,status = "disabled";
> +};
> -- 
> 2.47.3
> 
> 
> 

-- 
#gernperDu 
#CallMeByMyFirstName

Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |

[PATCH 2/2] arm: dts: rk356x: rock3a: disable pcie3x2

[Ahmad Fatoum]

The board hangs occasionally on PCI probe after:

  phy7: lane number 0, val 1

On other boots, it continues to:

  rockchip-dw-pcie 3c0800000.pcie@fe280000.of: Phy link never came up

In both cases, the hang affects the second PCIe host controller
to probe and the first probe never hangs:

  rockchip-dw-pcie 3c0000000.pcie@fe260000.of: Phy link never came up

This hang happens on the very first read access to the PCI controller
at register PCIE_ATU_VIEWPORT. Reading Linux code, the first access
seems to be to PCIE_VERSION_NUMBER (0x8F8), but accessing that in
barebox equally hangs from time to time.

My board doesn't have any PCIe devices connected and this hang
doesn't happen in Linux and doesn't happen on the QNAP
TS433-eU, which is also RK3568, but actually has PCIe devices, which are
probed normally.

Disable the device in barebox, so the board is usable with
rockchip_v8_defconfig, which enables the PCI driver.
barebox,status is used, so the Linux device tree is not affected.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 arch/arm/dts/rk3568-rock-3a.dts | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/arch/arm/dts/rk3568-rock-3a.dts b/arch/arm/dts/rk3568-rock-3a.dts
index bcbfab14a580..b7258d7e61b3 100644
--- a/arch/arm/dts/rk3568-rock-3a.dts
+++ b/arch/arm/dts/rk3568-rock-3a.dts
@@ -55,3 +55,7 @@ environment_sd: partition@408000 {
 		};
 	};
 };
+
+&pcie3x2 {
+	barebox,status = "disabled";
+};
-- 
2.47.3