From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"Eric Piel" <eric.piel@tremplin-utc.net>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Tony Lindgren" <tony@atomide.com>
Subject: Re: Driver lis3lv02d_i2c not working on Nokia RX-51
Date: Tue, 26 Mar 2013 17:08:41 +0000 [thread overview]
Message-ID: <20130326170841.GG18316@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CA+55aFwYvq5fZawbDVDPBu0ox2W7DQf5JmmyQHJYpBTOOTu_nQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]
On Tue, Mar 26, 2013 at 09:08:08AM -0700, Linus Torvalds wrote:
> This is a regression, and it needs to be fixed. The "device needs
This isn't a regression, the commit they're complaining about (ec400c)
was added in October 2011 with a note about all the in-tree users having
been looked after and then the commit adding the registration of the
device (3b511201) was added in May 2012 - the device has just never,
ever worked in mainline on this board as far as I can tell. It's not
like this was even two commits going in in the same release cycle.
As far as I can tell what's happened here is that someone got round to
testing what was sent upstream for the board and noticed that it never
worked.
> power" crap is just that - crap. Nobody cares. OF COURSE all devices
> need power, but that is totally irrelevant for a driver. The SSD in my
> system "needs power", but I have absolutely zero regulator information
> for it NOR DO I F*CKING NEED ANY!
Right, and this is why the core provides facilities for stubbing things
out. There's no point in every single driver going and implementing the
same code for handling this stuff, it's repetitive at best.
> I'm going to revert that commit unless you can fix it some other way
> (dummy regulators when you can't find a real one or whatever). The
That's pretty much what I'm telling them to do - put the stub regulators
in if they don't know how things are connected on their board (there's
helpers to make this easier).
There is also an existing Kconfig option to just stub out any missing
regulator which people can use but it's not recommended for production
since it confuses things that may really have optional supplies and want
to handle that.
> notion that you have to have regulator information in order to use
> some random device is insanity. I don't understand how you can even
> start to make excuses like that. It's so obviously bogus that it's not
> even funny.
There's definitely room for improving the stubs, I would like to see
something which lets boards say "these specific regulators are mapped,
these supplies don't exist and stub anything else out with a dummy", but
users like rx51 should be well enough catered for at the minute.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-26 17:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 23:46 Driver lis3lv02d_i2c not working on Nokia RX-51 Pali Rohár
2013-02-17 16:25 ` Mark Brown
2013-02-17 16:40 ` Pali Rohár
2013-02-17 18:17 ` Mark Brown
2013-03-24 14:50 ` Pali Rohár
2013-03-24 21:21 ` Mark Brown
2013-03-24 21:27 ` Pali Rohár
2013-03-24 22:14 ` Mark Brown
2013-03-24 22:44 ` Pali Rohár
2013-03-24 23:04 ` Mark Brown
2013-03-26 15:02 ` Pali Rohár
2013-03-26 15:44 ` Mark Brown
2013-03-26 16:08 ` Linus Torvalds
2013-03-26 17:08 ` Mark Brown [this message]
2013-03-26 20:53 ` Aaro Koskinen
2013-03-26 21:19 ` Mark Brown
2013-03-28 14:11 ` Pali Rohár
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130326170841.GG18316@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=aaro.koskinen@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=tony@atomide.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox