rockchip: dts: rk3399: Create initial rk3399-u-boot.dtsi
Subsystems (2)
PATCH 3/13 rockchip: dts: rk3399: Create initial rk3399-u-boot.dtsi
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and which is U-Boot specific devicetrees binding.
Move it on global rk3399-u-boot.dtsi file and rest of the U-Boot bindings will move it future based on the requirement.
This would help to sync the devicetrees from Linux whenever required instead of adding specific nodes.
---
Changes for v3.1:
- exclude changes for other dts files, since they handle separately.
arch/arm/dts/rk3399-u-boot.dtsi | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 arch/arm/dts/rk3399-u-boot.dtsi
arch/arm/dts/rk3399-u-boot.dtsi new file +8 -0
@@ -0,0 +1,8 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* + * Copyright (C) 2019 Jagan Teki <jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org> + */ + +&sdmmc { + u-boot,dm-pre-reloc; +};
Signature · 1 line
2.18.0.321.gffc6fa0e3
A message that is not in the archive (sent off-list or not yet received): 20190426131817.16776-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org
Hi,
Quoted 11 lines · Jagan Teki
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and which is U-Boot specific devicetrees binding.
Move it on global
rk3399-u-boot.dtsifile and rest of the U-Boot bindings will move it future based on the requirement.This would help to sync the devicetrees from Linux whenever required instead of adding specific nodes.
Since your patch has changed significantly, you can no longer include a Reviewed-by that was given on a previous iteration.
It looks like we are still missing bits to have rk3399-u-boot.dtsi included, so this patch does not get my Reviewed-by tag.
Cheers,
Paul
Quoted 22 lines
---
Changes for v3.1:
- exclude changes for other dts files, since they handle separately.arch/arm/dts/rk3399-u-boot.dtsi | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 arch/arm/dts/rk3399-u-boot.dtsiarch/arm/dts/rk3399-u-boot.dtsi new file +8
-0@@ -0,0 +1,8 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* + * Copyright (C) 2019 Jagan Teki <jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org> + */ + +&sdmmc { + u-boot,dm-pre-reloc; +};
Signature · 3 lines
Paul Kocialkowski, Bootlin Embedded Linux and kernel engineering https://bootlin.com
A message that is not in the archive (sent off-list or not yet received): accbbfc8d9d0ff50996f12b23b7588c453236864.camel-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org
Quoted 13 lines · Paul Kocialkowski
Hi,
Quoted 9 lines · Jagan Teki
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and which is U-Boot specific devicetrees binding.
Move it on global
rk3399-u-boot.dtsifile and rest of the U-Boot bindings will move it future based on the requirement.This would help to sync the devicetrees from Linux whenever required instead of adding specific nodes.
Quoted 8 lines
Quoted 2 lines
Since your patch has changed significantly, you can no longer include a Reviewed-by that was given on a previous iteration.
It looks like we are still missing bits to have
rk3399-u-boot.dtsiincluded, so this patch does not get my Reviewed-by tag.
It will include rockchip-u-boot.dtsi automatically and I made the receptive changes to include other files in this patch [1] and sure I will ask Philipp to remove the reviewed-by tag, thanks.
Hi,
Quoted 20 lines · Jagan Teki
Quoted 18 lines · Paul Kocialkowski
Hi,
Quoted 11 lines · Jagan Teki
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and which is U-Boot specific devicetrees binding.
Move it on global
rk3399-u-boot.dtsifile and rest of the U-Boot bindings will move it future based on the requirement.This would help to sync the devicetrees from Linux whenever required instead of adding specific nodes.
Signed-off-by Jagan Teki <[email protected]>Reviewed-by Paul Kocialkowski <[email protected]>Since your patch has changed significantly, you can no longer include a Reviewed-by that was given on a previous iteration.
Quoted 6 lines
Quoted 2 lines
It looks like we are still missing bits to have
rk3399-u-boot.dtsiincluded, so this patch does not get my Reviewed-by tag.It will include
rockchip-u-boot.dtsiautomatically and I made the receptive changes to include other files in this patch [1] and sure I will ask Philipp to remove the reviewed-by tag, thanks.
Most importantly (now that I see the new series), you should certainly have sent that patch as part of your new series because we now have an inter-dependency between both series.
Could you clean that up and make a proper standalone series that creates and populates rk3399-u-boot.dtsi?
Cheers,
Paul
Quoted 1 line
Signature · 8 lines
Paul Kocialkowski, Bootlin Embedded Linux and kernel engineering https://bootlin.com _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
Quoted 27 lines · Paul Kocialkowski
Hi,
Quoted 23 lines · Jagan Teki
Quoted 20 lines · Paul Kocialkowski
Hi,
Quoted 11 lines · Jagan Teki
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and which is U-Boot specific devicetrees binding.
Move it on global
rk3399-u-boot.dtsifile and rest of the U-Boot bindings will move it future based on the requirement.This would help to sync the devicetrees from Linux whenever required instead of adding specific nodes.
Signed-off-by Jagan Teki <[email protected]>Reviewed-by Paul Kocialkowski <[email protected]>Since your patch has changed significantly, you can no longer include a Reviewed-by that was given on a previous iteration.
It looks like we are still missing bits to have
rk3399-u-boot.dtsiincluded, so this patch does not get my Reviewed-by tag.
Quoted 7 lines
Quoted 3 lines
It will include
rockchip-u-boot.dtsiautomatically and I made the receptive changes to include other files in this patch [1] and sure I will ask Philipp to remove the reviewed-by tag, thanks.Most importantly (now that I see the new series), you should certainly have sent that patch as part of your new series because we now have an inter-dependency between both series.
It is not like an inter-dependency the previous rk3399-u-boot.dtsi is not included by these files so they would work as before. and now this series would need this change to include rk3399-u-boot.dtsi since the goal here to add binman node to common for all rk3399 dts files.
_______________________________________________
U-Boot mailing list
[email protected]
https://lists.denx.de/listinfo/u-boot
Hi,
Quoted 32 lines · Jagan Teki
Quoted 30 lines · Paul Kocialkowski
Hi,
Quoted 26 lines · Jagan Teki
Quoted 12 lines · Paul Kocialkowski
Hi,
Quoted 9 lines · Jagan Teki
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and which is U-Boot specific devicetrees binding.
Move it on global
rk3399-u-boot.dtsifile and rest of the U-Boot bindings will move it future based on the requirement.This would help to sync the devicetrees from Linux whenever required instead of adding specific nodes.
Quoted 8 lines
Quoted 2 lines
Signed-off-by Jagan Teki <[email protected]>Reviewed-by Paul Kocialkowski <[email protected]>Since your patch has changed significantly, you can no longer include a Reviewed-by that was given on a previous iteration.
It looks like we are still missing bits to have
rk3399-u-boot.dtsiincluded, so this patch does not get my Reviewed-by tag.It will include
rockchip-u-boot.dtsiautomatically and I made the receptive changes to include other files in this patch [1] and sure I will ask Philipp to remove the reviewed-by tag, thanks.
Quoted 8 lines
Quoted 3 lines
Most importantly (now that I see the new series), you should certainly have sent that patch as part of your new series because we now have an inter-dependency between both series.
It is not like an inter-dependency the previous
rk3399-u-boot.dtsiis not included by these files so they would work as before. and now this series would need this change to includerk3399-u-boot.dtsisince the goal here to add binman node to common for all rk3399 dts files.
Well, what I mean is that the latest series you sent mentions a dependency on the first one, when it really should be the other way
round: you need the rework to make things in your first series work at all, since that dm-pre-reloc is necessary.
We don't want to merge one broken series and then the fix for it later, even if it would still build in all cases. Here there is a clear logical dependency, in the reverse ordre to the one you are describing.
In order to get this right, you need to take that v3.1 patch from the first series and stick first in the new one. When that's done, I'll be happy to move on to reviewing the code!
Cheers,
Paul
Signature · 8 lines
Paul Kocialkowski, Bootlin Embedded Linux and kernel engineering https://bootlin.com _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
Quoted 45 lines · Paul Kocialkowski
Hi,
Quoted 32 lines · Jagan Teki
Quoted 30 lines · Paul Kocialkowski
Hi,
Quoted 26 lines · Jagan Teki
Quoted 12 lines · Paul Kocialkowski
Hi,
Quoted 9 lines · Jagan Teki
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and which is U-Boot specific devicetrees binding.
Move it on global
rk3399-u-boot.dtsifile and rest of the U-Boot bindings will move it future based on the requirement.This would help to sync the devicetrees from Linux whenever required instead of adding specific nodes.
Quoted 8 lines
Quoted 2 lines
Signed-off-by Jagan Teki <[email protected]>Reviewed-by Paul Kocialkowski <[email protected]>Since your patch has changed significantly, you can no longer include a Reviewed-by that was given on a previous iteration.
It looks like we are still missing bits to have
rk3399-u-boot.dtsiincluded, so this patch does not get my Reviewed-by tag.It will include
rockchip-u-boot.dtsiautomatically and I made the receptive changes to include other files in this patch [1] and sure I will ask Philipp to remove the reviewed-by tag, thanks.Quoted 8 lines
Quoted 3 lines
Most importantly (now that I see the new series), you should certainly have sent that patch as part of your new series because we now have an inter-dependency between both series.
It is not like an inter-dependency the previous
rk3399-u-boot.dtsiis not included by these files so they would work as before. and now this series would need this change to includerk3399-u-boot.dtsisince the goal here to add binman node to common for all rk3399 dts files.
Quoted 8 lines
Well, what I mean is that the latest series you sent mentions a dependency on the first one, when it really should be the other way
round: you need the rework to make things in your first series work at all, since that dm-pre-reloc is necessary.We don't want to merge one broken series and then the fix for it later, even if it would still build in all cases. Here there is a clear logical dependency, in the reverse ordre to the one you are describing.
I don't understand your point, sorry.
This patch [1] will make use of the new boards added on that series it will not effect existing or previous rk3399 boards. in that case why it is broken patch or series could you elaborate? the existing boards are already supported dm-pre-reloc on their respective devicetree files.
[1] https://patchwork.ozlabs.org/patch/1091534/
_______________________________________________
U-Boot mailing list
[email protected]
https://lists.denx.de/listinfo/u-boot
A message that is not in the archive (sent off-list or not yet received): CAMty3ZC1200fH34qoOBTuokgmby-uLGp6ocCKtkFPQLo-8XLLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org
Hi,
Quoted 55 lines · Jagan Teki
Quoted 44 lines · Paul Kocialkowski
Hi,
Quoted 32 lines · Jagan Teki
Quoted 30 lines · Paul Kocialkowski
Hi,
Quoted 26 lines · Jagan Teki
Quoted 12 lines · Paul Kocialkowski
Hi,
Quoted 9 lines · Jagan Teki
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and which is U-Boot specific devicetrees binding.
Move it on global
rk3399-u-boot.dtsifile and rest of the U-Boot bindings will move it future based on the requirement.This would help to sync the devicetrees from Linux whenever required instead of adding specific nodes.
Quoted 8 lines
Quoted 2 lines
Since your patch has changed significantly, you can no longer include a Reviewed-by that was given on a previous iteration.
It looks like we are still missing bits to have
rk3399-u-boot.dtsiincluded, so this patch does not get my Reviewed-by tag.It will include
rockchip-u-boot.dtsiautomatically and I made the receptive changes to include other files in this patch [1] and sure I will ask Philipp to remove the reviewed-by tag, thanks.Quoted 8 lines
Quoted 3 lines
Most importantly (now that I see the new series), you should certainly have sent that patch as part of your new series because we now have an inter-dependency between both series.
It is not like an inter-dependency the previous
rk3399-u-boot.dtsiis not included by these files so they would work as before. and now this series would need this change to includerk3399-u-boot.dtsisince the goal here to add binman node to common for all rk3399 dts files.Quoted 8 lines
Well, what I mean is that the latest series you sent mentions a dependency on the first one, when it really should be the other way
round: you need the rework to make things in your first series work at all, since that dm-pre-reloc is necessary.We don't want to merge one broken series and then the fix for it later, even if it would still build in all cases. Here there is a clear logical dependency, in the reverse ordre to the one you are describing.
Quoted 7 lines
I don't understand your point, sorry.
This patch [1] will make use of the new boards added on that series it will not effect existing or previous rk3399 boards. in that case why it is broken patch or series could you elaborate? the existing boards are already supported dm-pre-reloc on their respective devicetree files.
On looks like I still didn't really get what you are trying to do. Let's try and recap the situation:
- Currently, we have rk3399 boards with u-boot,dm-pre-reloc in their shared dtsi;
- Your v3.1 adds rk3399-u-boot.dtsi but keeps the u-boot,dm-pre-reloc in each device since rk3399-u-boot won't be included.
- Your new series allows rk3399-u-boot.dtsi to be included automatically, so we can move the per-common-device-dts u-boot,dm-pre- reloc to rk3399-u-boot.dtsi
If that's correct, then it indeed makes sense the way it is proposed. Your commit messages just lack a clear explanation of what is going on here, since it's not quite trivial for anyone but you.
Cheers,
Paul
Quoted 1 line
Signature · 3 lines
Paul Kocialkowski, Bootlin Embedded Linux and kernel engineering https://bootlin.com
A message that is not in the archive (sent off-list or not yet received): 863a27628b5e563bb769accf4595575e91023ebe.camel-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org
Quoted 67 lines · Paul Kocialkowski
Hi,
Quoted 55 lines · Jagan Teki
Quoted 44 lines · Paul Kocialkowski
Hi,
Quoted 32 lines · Jagan Teki
Quoted 30 lines · Paul Kocialkowski
Hi,
Quoted 26 lines · Jagan Teki
Quoted 12 lines · Paul Kocialkowski
Hi,
Quoted 9 lines · Jagan Teki
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and which is U-Boot specific devicetrees binding.
Move it on global
rk3399-u-boot.dtsifile and rest of the U-Boot bindings will move it future based on the requirement.This would help to sync the devicetrees from Linux whenever required instead of adding specific nodes.
Quoted 8 lines
Quoted 2 lines
Since your patch has changed significantly, you can no longer include a Reviewed-by that was given on a previous iteration.
It looks like we are still missing bits to have
rk3399-u-boot.dtsiincluded, so this patch does not get my Reviewed-by tag.It will include
rockchip-u-boot.dtsiautomatically and I made the receptive changes to include other files in this patch [1] and sure I will ask Philipp to remove the reviewed-by tag, thanks.Quoted 8 lines
Quoted 3 lines
Most importantly (now that I see the new series), you should certainly have sent that patch as part of your new series because we now have an inter-dependency between both series.
It is not like an inter-dependency the previous
rk3399-u-boot.dtsiis not included by these files so they would work as before. and now this series would need this change to includerk3399-u-boot.dtsisince the goal here to add binman node to common for all rk3399 dts files.Quoted 8 lines
Well, what I mean is that the latest series you sent mentions a dependency on the first one, when it really should be the other way
round: you need the rework to make things in your first series work at all, since that dm-pre-reloc is necessary.We don't want to merge one broken series and then the fix for it later, even if it would still build in all cases. Here there is a clear logical dependency, in the reverse ordre to the one you are describing.
Quoted 7 lines
I don't understand your point, sorry.
This patch [1] will make use of the new boards added on that series it will not effect existing or previous rk3399 boards. in that case why it is broken patch or series could you elaborate? the existing boards are already supported dm-pre-reloc on their respective devicetree files.
Quoted 5 lines
On looks like I still didn't really get what you are trying to do. Let's try and recap the situation:
- Currently, we have rk3399 boards with u-boot,dm-pre-reloc in their shared dtsi;
No, the existing boards don't have shared dtsi that have u-boot,dm-pre-reloc instead they included on respective dts files.
Quoted 2 lines
- Your v3.1 adds
rk3399-u-boot.dtsibut keeps the u-boot,dm-pre-reloc in each device since rk3399-u-boot won't be included.
This would keep sdmmc node only which is included by the new boards on that series only.
Quoted 3 lines
- Your new series allows
rk3399-u-boot.dtsito be included automatically, so we can move the per-common-device-dts u-boot,dm-pre- reloc tork3399-u-boot.dtsi
No, automatically I'm explicit including on respective -u-boot.dtsi
Quoted 4 lines
If that's correct, then it indeed makes sense the way it is proposed. Your commit messages just lack a clear explanation of what is going on here, since it's not quite trivial for anyone but you.
Please don't through stone, explain where it lacks. thanks.
Look like you seems confusing or unclear, here is bit more explanation. The existing boards have u-boot,dm-pre-reloc for sdmmc on their individual dts(i) files, my series add added initial rk3399-u-boot.dtsi by including sdmmc node to use u-boot,dm-pre-reloc which is what in v3.1 and the same included by board dts files which I added on next patches.
Jagan.
Hi,
Quoted 68 lines · Jagan Teki
Quoted 66 lines · Paul Kocialkowski
Hi,
Quoted 62 lines · Jagan Teki
Quoted 44 lines · Paul Kocialkowski
Hi,
Quoted 32 lines · Jagan Teki
Quoted 30 lines · Paul Kocialkowski
Hi,
Quoted 26 lines · Jagan Teki
Quoted 12 lines · Paul Kocialkowski
Hi,
Quoted 9 lines · Jagan Teki
u-boot,dm-pre-reloc is required for SDMMC booted rk3399 boards and which is U-Boot specific devicetrees binding.
Move it on global
rk3399-u-boot.dtsifile and rest of the U-Boot bindings will move it future based on the requirement.This would help to sync the devicetrees from Linux whenever required instead of adding specific nodes.
Quoted 8 lines
Quoted 2 lines
Signed-off-by Jagan Teki <[email protected]>Reviewed-by Paul Kocialkowski <[email protected]>Since your patch has changed significantly, you can no longer include a Reviewed-by that was given on a previous iteration.
It looks like we are still missing bits to have
rk3399-u-boot.dtsiincluded, so this patch does not get my Reviewed-by tag.It will include
rockchip-u-boot.dtsiautomatically and I made the receptive changes to include other files in this patch [1] and sure I will ask Philipp to remove the reviewed-by tag, thanks.Quoted 8 lines
Quoted 3 lines
Most importantly (now that I see the new series), you should certainly have sent that patch as part of your new series because we now have an inter-dependency between both series.
It is not like an inter-dependency the previous
rk3399-u-boot.dtsiis not included by these files so they would work as before. and now this series would need this change to includerk3399-u-boot.dtsisince the goal here to add binman node to common for all rk3399 dts files.Quoted 8 lines
Well, what I mean is that the latest series you sent mentions a dependency on the first one, when it really should be the other way
round: you need the rework to make things in your first series work at all, since that dm-pre-reloc is necessary.We don't want to merge one broken series and then the fix for it later, even if it would still build in all cases. Here there is a clear logical dependency, in the reverse ordre to the one you are describing.
I don't understand your point, sorry.
This patch [1] will make use of the new boards added on that series it will not effect existing or previous rk3399 boards. in that case why it is broken patch or series could you elaborate? the existing boards are already supported dm-pre-reloc on their respective devicetree files.
Quoted 8 lines
Quoted 5 lines
On looks like I still didn't really get what you are trying to do. Let's try and recap the situation:
- Currently, we have rk3399 boards with u-boot,dm-pre-reloc in their shared dtsi;
No, the existing boards don't have shared dtsi that have u-boot,dm-pre-reloc instead they included on respective dts files.
I mean shared with Linux, so respective per-device dts files yes. Sorry, that was definitely unclear wording on my side.
Quoted 11 lines
Quoted 2 lines
- Your v3.1 adds
rk3399-u-boot.dtsibut keeps the u-boot,dm-pre-reloc in each device since rk3399-u-boot won't be included.This would keep sdmmc node only which is included by the new boards on that series only.
Quoted 3 lines
- Your new series allows
rk3399-u-boot.dtsito be included automatically, so we can move the per-common-device-dts u-boot,dm-pre- reloc tork3399-u-boot.dtsiNo, automatically I'm explicit including on respective
-u-boot.dtsi
Yes you're right, though the result is the same.
Quoted 5 lines
Quoted 3 lines
If that's correct, then it indeed makes sense the way it is proposed. Your commit messages just lack a clear explanation of what is going on here, since it's not quite trivial for anyone but you.
Please don't through stone, explain where it lacks. thanks.
It's the same issue as before, you are not putting enough context in the descriptions and they are only clear to someone who has already understood the issue. You need to make sure that someone who did not know about the issue has a clear idea of it after reading the commit log.
I'm already trying to help by discussing the issue and presenting my understanding so you can get an idea of what point where unclear, but it's ultimately up to you to provide understandable commit messages for reviewers.
Quoted 6 lines
Look like you seems confusing or unclear, here is bit more explanation. The existing boards have u-boot,dm-pre-reloc for sdmmc on their individual dts(i) files, my series add added initial
rk3399-u-boot.dtsiby including sdmmc node to use u-boot,dm-pre-reloc which is what in v3.1 and the same included by board dts files which I added on next patches.
Okay so I think I have a clear idea of what is going on now.
Cheers,
Paul
Signature · 8 lines
Paul Kocialkowski, Bootlin Embedded Linux and kernel engineering https://bootlin.com _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot