From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stephen Warren <swarren@nvidia.com>,
Linus Walleij <linus.walleij@stericsson.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Grant Likely <grant.likely@secretlab.ca>,
Barry Song <21cnbao@gmail.com>,
Shawn Guo <shawn.guo@freescale.com>
Subject: Re: [PATCH v2] pinctrl: add a generic pin config interface
Date: Thu, 24 Nov 2011 15:18:13 +0000 [thread overview]
Message-ID: <20111124151812.GN8470@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkdb78AAM-9JasxQ2pRLwVGj0n64bqo82oVbpaFKsMNqnaA@mail.gmail.com>
On Thu, Nov 24, 2011 at 03:19:39PM +0100, Linus Walleij wrote:
> On Tue, Nov 22, 2011 at 2:59 PM, Mark Brown
> > I'd second this - in my experience detailed setup for these settings
> > usually comes from hardware engineers in the form of "set register X to
> > value Y". Having to decode the sematics does make things that little
> > bit harder.
> I'm a bit reluctant, since the above is sometimes referred to as
> "throw over the wall engineering" and is generally considered a bad
> way of doing things.
Well, another way of describing the above situation would be the
software engineers going to the hardware engineer and saying that
they've got ringing on a signal (or something) and the hardware
engineer coming back with a suggested fix.
prev parent reply other threads:[~2011-11-24 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 8:31 [PATCH v2] pinctrl: add a generic pin config interface Linus Walleij
2011-11-11 11:26 ` Thomas Abraham
2011-11-14 9:36 ` Linus Walleij
2011-11-14 14:24 ` Thomas Abraham
2011-11-14 19:44 ` Stephen Warren
2011-11-17 13:26 ` Linus Walleij
2011-11-18 22:32 ` Stephen Warren
2011-11-21 19:29 ` Linus Walleij
2011-11-21 23:22 ` Stephen Warren
2011-11-22 13:59 ` Mark Brown
2011-11-24 14:19 ` Linus Walleij
2011-11-24 15:18 ` Mark Brown [this message]
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=20111124151812.GN8470@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=21cnbao@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.guo@freescale.com \
--cc=swarren@nvidia.com \
/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