From: broonie@opensource•wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: 3ds_debugboard: Let ethernet be functional again
Date: Wed, 29 Feb 2012 10:00:28 +0000 [thread overview]
Message-ID: <20120229100027.GA3182@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120229083317.GT3852@pengutronix.de>
On Wed, Feb 29, 2012 at 09:33:17AM +0100, Sascha Hauer wrote:
> On Tue, Feb 28, 2012 at 10:52:22AM +0000, Mark Brown wrote:
> > Can you be more specific about what you think would break here please?
> We started this discussion with a patch of mine in which I wanted to add
> a helper function to register a fixed regulator. You asked me to drop
> the voltage parameter in the helper function as this is mainly used as
> a dummy regulator. I then tried to remove the voltage parameter and it
> turned out that the regulator core needs a voltage because otherwise it
> bails out in machine_constraints_voltage(), more specifically in
> ops->list_voltage(rdev, i) returing 0 for a dummy fixed regulator. You
> then answered that the fixed regulator should be fixed to return an error
> if it hasn't got a voltage configured. At this point the circle is
> complete and we can start the discussion again.
I'm sorry but you're still not explaining what the problem is - what
makes you say that reporting errors and so on instead of zero volts
would cause a problem?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120229/4cde0fad/attachment.sig>
next prev parent reply other threads:[~2012-02-29 10:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 20:27 [PATCH] ARM: 3ds_debugboard: Let ethernet be functional again Fabio Estevam
2012-02-13 8:27 ` Sascha Hauer
2012-02-13 12:18 ` Fabio Estevam
2012-02-13 14:48 ` Mark Brown
2012-02-14 10:58 ` Sascha Hauer
2012-02-14 17:29 ` Mark Brown
2012-02-16 7:32 ` Sascha Hauer
2012-02-16 7:58 ` Mark Brown
2012-02-16 9:13 ` Sascha Hauer
2012-02-16 16:27 ` Mark Brown
2012-02-17 7:40 ` Sascha Hauer
2012-02-17 16:29 ` Mark Brown
2012-02-27 9:04 ` Sascha Hauer
2012-02-27 13:29 ` Mark Brown
2012-02-27 17:20 ` Sascha Hauer
2012-02-27 23:54 ` Mark Brown
2012-02-28 8:27 ` Sascha Hauer
2012-02-28 10:52 ` Mark Brown
2012-02-29 8:33 ` Sascha Hauer
2012-02-29 10:00 ` Mark Brown [this message]
2012-03-01 10:08 ` Sascha Hauer
2012-03-01 10:52 ` Mark Brown
2012-03-01 18:20 ` Sascha Hauer
2012-03-01 18:21 ` Mark Brown
2012-03-01 18:30 ` Sascha Hauer
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=20120229100027.GA3182@opensource.wolfsonmicro.com \
--to=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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