Hi, On Thu, Aug 2, 2018 at 2:10 AM, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > Hi Jeremy, > > On Thu, Aug 2, 2018 at 2:04 AM Jeremy Linton <lintonrjeremy@xxxxxxxxx> wrote: (trimming) >> Sure, but those seem to have symbolic dependency chains/etc sufficient >> to get them loaded (aka include the clk driver and it pulls in the >> regulator or whatever). >> >> > SOFTDEP don't sounds like the solution to list all these. >> >> In the dw_mmc-k3 case, its really only the reset driver that isn't >> being picked up by the dependency detection, but I listed the clk >> driver as well since the two are fairly closely related on this >> platform. >> >> I'm open to other ideas for detecting these dependencies... > > We already have a description of the hardware and its dependencies in > arch/arm64/boot/dts/hisilicon/hi3660.dtsi: > (trimming dt) > > You can get inspiration to automate the above from my linux-config-from-dt > script at https://github.com/geertu/linux-scripts . Thanks for the suggestion. While technically workable, I don't think we want to further fragment this space for a subset of ARM machines. One of the overarching goals (as i'm sure your aware) is to bring arm64 closer to existing platforms by making it behave in a more regular manner so that we can stop dictating distro/kernel/etc versions to the end users. Thanks, -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
