linux-kernel - Re: [PATCH v2 0/3] introduce External Connector Class (extcon)

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]

Message-ID: <20111220010109.GO2860@opensource.wolfsonmicro.com>
Date:	Tue, 20 Dec 2011 01:01:09 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	NeilBrown <neilb@...e.de>
Cc:	MyungJoo Ham <myungjoo.ham@...sung.com>,
	linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...otime.net>,
	Mike Lockwood <lockwood@...roid.com>,
	Arve Hjønnevåg <arve@...roid.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Donggeun Kim <dg77.kim@...sung.com>, Greg KH <gregkh@...e.de>,
	Arnd Bergmann <arnd@...db.de>,
	MyungJoo Ham <myungjoo.ham@...il.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Morten CHRISTIANSEN <morten.christiansen@...ricsson.com>
Subject: Re: [PATCH v2 0/3] introduce External Connector Class (extcon)

On Sun, Dec 18, 2011 at 06:15:50PM +1100, NeilBrown wrote:
> On Thu, 15 Dec 2011 14:51:55 +0800 Mark Brown

> > Grant has a proposal for this which revolves around devices trying to
> > acquire their resources and returning a "please retry" error code if
> > they don't have all their dependencies.  Half the problem here is that

> A possibility I have been thinking about is to multithread do_initcalls() and
> have the various request functions (gpio_request, regulator_get, request_irq,
> etc) optionally block if the resource isn't available.

That seems to be logically the same in terms of what it actually does
but introduces concurrency which wasn't there before which means that
things could get reordered for random reasons.  That seems like it'd not
be great for robustness.

> Do we need to talk about devices that haven't been enumerated yet? or was
> that just if we wanted to create an explicit dependency graph?

You need to know about devices that aren't enumerated yet.
--
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/