From: Ashish Jangam <ashish.jangam@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@ti.com>, Samuel Ortiz <sameo@linux.intel.com>,
<linux-kernel@vger.kernel.org>,
David Dajun Chen <dchen@diasemi.com>
Subject: Re: [patch v1 2/5] regulator: da9055 change irq state to default
Date: Fri, 25 Jan 2013 13:56:40 +0530 [thread overview]
Message-ID: <1359102400.6620.3.camel@dhruva> (raw)
In-Reply-To: <20130123160354.GE4565@opensource.wolfsonmicro.com>
On Thu, 2013-01-24 at 00:03 +0800, Mark Brown wrote:
> On Mon, Jan 21, 2013 at 02:05:12PM +0530, Ashish Jangam wrote:
>
> > > What makes you say that there is a dependency here? It's really not at
> > > all obvious why a change to the primary IRQ signalling mechanism would
> > > affect the internal interrupts of the device.
>
> > Yes, functionally this dependency should not matter.However, if
> > mfd/primary irq state is low and its components are high then it shall
> > not look good. Therefore the term dependency was used, probably I should
> > have written it in a different manner.
>
> This logic doesn't follow terribly directly - looking at what you've
> posted it in fact seems that the trigger type is irrelevant in the
> function drivers?
Though it is functionally irrelevant but in the code setting the primary
irq to low and functional driver to high may confuse the code reader.
However I leave this decision to you.
next prev parent reply other threads:[~2013-01-25 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C3AE124F08223B42BC95AEB82F0F6CED4313C7F1@KCHJEXMB03.kpit.com>
2013-01-21 8:35 ` [patch v1 2/5] regulator: da9055 change irq state to default Ashish Jangam
2013-01-23 16:03 ` Mark Brown
2013-01-25 8:26 ` Ashish Jangam [this message]
[not found] <C3AE124F08223B42BC95AEB82F0F6CED4313C79B@KCHJEXMB03.kpit.com>
2013-01-21 8:04 ` Ashish Jangam
2013-01-21 8:13 ` Mark Brown
2013-01-18 5:22 Ashish Jangam
2013-01-18 7:23 ` Mark Brown
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=1359102400.6620.3.camel@dhruva \
--to=ashish.jangam@kpitcummins.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dchen@diasemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sameo@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.