arch/arm64/boot/dts/axiado/ax3000-evk.dts | 3 +++ 1 file changed, 3 insertions(+)
Axiado AX3000 EVK has total of 4 UART ports. Add missing alias for uart0,
uart1, uart2.
This fixes the probe failures on the remaining UARTs.
Fixes: 1f7055779001 ("arm64: dts: axiado: Add initial support for AX3000 SoC and eval board")
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Harshit Shah <hshah@axiado.com>
---
- Run "b4 trailes -u"
- Link to v3: https://lore.kernel.org/r/20250824-axiado-ax3000-missing-serial-alias-v3-1-5db4143bf189@axiado.com
Changes in v3:
- move "Fixes:" tag before Signed-off-by in commit (Krzysztof)
- Link to v2: https://lore.kernel.org/r/20250822-axiado-ax3000-missing-serial-alias-v2-1-54052d75467b@axiado.com
Changes in v2:
- Add missing "Fixes:" tag in commit msg
- Link to v1: https://lore.kernel.org/r/20250821-axiado-ax3000-missing-serial-alias-v1-1-527d979c3ea0@axiado.com
---
arch/arm64/boot/dts/axiado/ax3000-evk.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/axiado/ax3000-evk.dts b/arch/arm64/boot/dts/axiado/ax3000-evk.dts
index 92101c5b534bfac8b463adaa1c4f0d4367d01e21..b86e969625573bf92bdd5e4435ea571dd7500de2 100644
--- a/arch/arm64/boot/dts/axiado/ax3000-evk.dts
+++ b/arch/arm64/boot/dts/axiado/ax3000-evk.dts
@@ -14,6 +14,9 @@ / {
#size-cells = <2>;
aliases {
+ serial0 = &uart0;
+ serial1 = &uart1;
+ serial2 = &uart2;
serial3 = &uart3;
};
---
base-commit: 8742b2d8935f476449ef37e263bc4da3295c7b58
change-id: 20250813-axiado-ax3000-missing-serial-alias-39c489370ba9
Best regards,
--
Harshit Shah <hshah@axiado.com>
On 28/08/2025 20:27, Harshit Shah wrote: > Axiado AX3000 EVK has total of 4 UART ports. Add missing alias for uart0, > uart1, uart2. > > This fixes the probe failures on the remaining UARTs. > > Fixes: 1f7055779001 ("arm64: dts: axiado: Add initial support for AX3000 SoC and eval board") > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > Signed-off-by: Harshit Shah <hshah@axiado.com> > --- > - Run "b4 trailes -u" > - Link to v3: https://lore.kernel.org/r/20250824-axiado-ax3000-missing-serial-alias-v3-1-5db4143bf189@axiado.com Please don't do this. It just generates unnecessary traffic. See my instructions you receive on your first submissions.... unless you want to send patches to soc@ (which looks added here) but then this is also wrong - we do not send patch by patch. Collect *all* the patches for the next merge window and send them around rc5 (rc6 being the latest). Best regards, Krzysztof
On 8/28/2025 10:58 PM, Krzysztof Kozlowski wrote: > Please don't do this. It just generates unnecessary traffic. See my > instructions you receive on your first submissions.... unless you want > to send patches to soc@ (which looks added here) but then this is also Hi Krzysztof, Yes, the reason I have resent this patch with adding (soc@) as this is the fix from the previous series. Fixes: 1f7055779001 ("arm64: dts: axiado: Add initial support for AX3000 SoC and eval board") I missed to add those aliases and it is giving probe failures without these changes. So I was hoping if this could be merged as the fix in the upcoming -rcX before the next merge window. Regards, Harshit.
On 29/08/2025 20:17, Harshit Shah wrote: > On 8/28/2025 10:58 PM, Krzysztof Kozlowski wrote: >> Please don't do this. It just generates unnecessary traffic. See my >> instructions you receive on your first submissions.... unless you want >> to send patches to soc@ (which looks added here) but then this is also > > Hi Krzysztof, > > Yes, the reason I have resent this patch with adding (soc@) as this is > the fix from the previous series. > > Fixes: 1f7055779001 ("arm64: dts: axiado: Add initial support for AX3000 SoC and eval board") > > I missed to add those aliases and it is giving probe failures without > these changes. So I was hoping if this could be merged as the fix > > in the upcoming -rcX before the next merge window. The goal is correct, but you need to follow standard soc-subsystem maintainer process. You need to have your tree in the next, then collect the patches and fixes to respective branches, and then send multiple of them in pull request or as patches ONLY to soc@. My Beginners maintainer talk from LPC 23 might help you. Best regards, Krzysztof
© 2016 - 2025 Red Hat, Inc.