linux-kernel - Re: [PATCH] OMAP: hwmod: add kernel cmdline flag to avoid resetting IP blocks during init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 6 Jul 2011 15:01:49 -0600 (MDT)
From:	Paul Walmsley <paul@...an.com>
To:	Tony Lindgren <tony@...mide.com>
cc:	linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	Aaro Koskinen <aaro.koskinen@...ia.com>,
	Rajendra Nayak <rnayak@...com>,
	Benoît Cousson <b-cousson@...com>,
	Michael Buesch <mb@...sch.de>
Subject: Re: [PATCH] OMAP: hwmod: add kernel cmdline flag to avoid resetting
 IP blocks during init

On Tue, 5 Jul 2011, Tony Lindgren wrote:

> * Paul Walmsley <paul@...an.com> [110705 18:55]:
> > On Tue, 5 Jul 2011, Paul Walmsley wrote:
> > 
> > > For this case, we probably need some board file function to tell the 
> > > hwmod code to disregard a device completely, to tell the kernel to 
> > > pretend that the device does not exist.
> > 
> > ... and the other problem here is that we currently probe devices via an 
> > arch_initcall(), and the board file init_machine is also an arch_initcall.
> > Either we'll need to be very careful about Makefile ordering, or we should 
> > just call omap2_init_devices() from the board file init_machine directly.
> > The latter makes the most sense to me.
> 
> And that can then be passed the list of devices with the special flags
> for noreset, disabled and reserved. Then the late_initcall can optionally
> reset the rest of the devices.

'disabled' can probably be the default for a device that doesn't have a 
driver associated with it, once the runtime PM conversion is complete.  
That's what the late_initcall would do.  Then if a driver is dynamically 
loaded for one of those devices, the hwmod code would just re-enable it.


- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/