linux-kernel - Re: [RFC PATCH] slimbus: Linux driver framework for SLIMbus.

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: <20110824092147.GS9232@opensource.wolfsonmicro.com>
Date:	Wed, 24 Aug 2011 10:21:47 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Kenneth Heitke <kheitke@...eaurora.org>,
	sdharia@...eaurora.org, David Brown <davidb@...eaurora.org>,
	bryanh@...eaurora.org, linux-arm-msm@...r.kernel.org,
	rdunlap@...otime.net, rmk+kernel@....linux.org.uk,
	john.stultz@...aro.org, akpm@...ux-foundation.org, ohad@...ery.com,
	gregkh@...e.de, stefanr@...6.in-berlin.de, lethal@...ux-sh.org,
	linville@...driver.com, zajec5@...il.com,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] slimbus: Linux driver framework for SLIMbus.

On Wed, Aug 24, 2011 at 11:15:56AM +0200, Linus Walleij wrote:
> On Thu, Aug 18, 2011 at 5:00 AM, Mark Brown
> > On Wed, 2011-08-17 at 15:17 +0200, Linus Walleij wrote:

> >> And I guess there is nothing in the spec claiming that all devices
> >> be powered-on when you boot?

> > I don't believe so, and if there were I'd not expect anyone to pay a
> > blind bit of notice to it.

> That means that the regulators handling the slimbus devices
> will need to be enabled before the drivers issue regulator_get()
> and regulator_enable() on them.

What makes you say that?  We've been discussing how we register Slimbus
devices other than via hotplug.

> Does the regulator constraint .always_on have this semantic
> effect, so the regulator framework can power up the devices
> without their drivers claiming the regulators first?

It does have that effect but it would (as one might expect) force the
regulators to always be on which is unacceptable for actual systems.

> Or would we need a new .boot_enable flag to handle that?

There is such a flag already.

> > If my memory serves (I don't have access to the relevant documents right
> > now) the device announces itself when it detects that the bus is alive.
> > Slimbus is a relatively heavyweight interface so the extra cost of doing
> > this won't be too bad.

> OK so if we can just power the device the bus can probably
> autodetect all devices on it, it seems.

Should be able to, yes, though we'll still need to bind platform/OF data
to them.
--
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/