[ADI] ARM: dts: adi: Add support for SC598-HTOL board#3239
[ADI] ARM: dts: adi: Add support for SC598-HTOL board#3239ozan956 wants to merge 2 commits intoadsp-6.12.0-yfrom
Conversation
|
Are you planning to add the defconfig for the HTOL board in this PR as well? |
I believe there is no need for a separate config. We already have the device tree, and its enough to describe the system. Only possible disadvantage is that some unused drivers may still be compiled, which could slightly increase the size. However, since they are not referenced in the device tree, they will not cause any issues in the end. |
|
Okay, I would check the ARCH_SC5XX and ARCH_SC59X_64 symbols just to make sure there isn't anything there that we need, but otherwise LGTM. |
👍 one of my many things we will clean-up in the long run is to reduce the number of defconfigs in Linux (and U-Boot) to one for each architecture |
Thank you! 😄 CONFIG_ARCH_SC59X_64 is already enabled in both ezkit and ezlite defconfigs, which covers all the necessary platform drivers. The architecture selections are essentially the same across these SC598 boards, so HTOL has everything it needs. Ideally, in the future, we could unify these into a single architecture level defconfig since the core platform requirements are identical across all SC598 variants. The device tree already handles the board specific differences, so having separate defconfigs is somewhat redundant. |
| #size-cells = <0>; | ||
|
|
||
| adin1300: ethernet-phy@0 { | ||
| compatible = "ethernet-phy-ieee802.3-c22"; |
There was a problem hiding this comment.
Very interesting to see how this goes since it is currently misconfigured for at least SC598 (see #2883)
Add device tree support for SC598 HTOL SBC based on the reference board designs. Signed-off-by: Ozan Durgut <ozan.durgut@analog.com>
984f676 to
7ac1edd
Compare
Signed-off-by: Ozan Durgut <ozan.durgut@analog.com>
Add device tree and defconfig support for the ADI
SC598 HTOL SBC based on the reference board designs.
PR Description
necessary to understand them. List any dependencies required for this change.
any space), or simply check them after publishing the PR.
description and try to push all related PRs simultaneously.
PR Type
PR Checklist