Re: [RFC] ARM: OMAP2+: hwmod: don't touch hwmod if disabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Tony Lindgren <tony@xxxxxxxxxxx> [170814 13:29]:
> * Dave Gerlach <d-gerlach@xxxxxx> [170814 12:53]:
> > Again, I am not saying touching status disabled nodes is the right way to do it,
> > just that currently we do for the reasons described above and if we stop
> > touching the nodes marked disabled we need a new solution.
> 
> Well I see the solution being the following steps:
> 
> 1. Fix up the few problem drivers to be able to bail out if
>    it's essential resources are missing
> 
> 2. Remove use of status = "disabled" unless the SoC internal
>    device is truly not accessible for the kernel
> 
> 3. Start using "fail-incomplete" so drivers know to bail
>    out early in a generic way if set

And if really needed, we can specifically tell to kill some hwmod.
We already have "ti,no-reset-on-init", "ti,no-idle-on-init",
and "ti,no-idle". So we could add "ti,disable-on-init" or
something similar. I'd rather see that as the default though
for devices that are accessible, so not sure if that is needed.

Anyways, just something to consider.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux