linux-kernel - Re: [PATCH 2/3] regulator: add a subdriver for TI TPS6105x regulator portions

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] [day] [month] [year] [list]

Message-ID: <AANLkTi=oP8dgGVZVT4FbfHjrN6vjFhDmTwJrKacv_94-@mail.gmail.com>
Date:	Tue, 8 Mar 2011 14:34:38 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Linus Walleij <linus.walleij@...ricsson.com>,
	Liam Girdwood <lrg@...mlogic.co.uk>,
	linux-kernel@...r.kernel.org, Lee Jones <lee.jones@...aro.org>,
	Samuel Ortiz <samuel.ortiz@...el.com>,
	Ola Lilja <ola.o.lilja@...ricsson.com>
Subject: Re: [PATCH 2/3] regulator: add a subdriver for TI TPS6105x regulator portions

On Tue, Mar 8, 2011 at 2:29 PM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:

>> So the fact that the regulator driver doesn't probe doesn't mean any
>> failure, some other driver will likely probe successfully for the chip.
>
> The general approach other MFDs have taken to this is to pay attention
> to the platform data when registering subdevices so that you don't get
> inappropriate subdevices registered in the first place.

Ah, clever. I'll fix.

Yours,
Linus Walleij
--
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/