mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Jangam <ashish.jangam@kpitcummins.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: Thu, 24 Jan 2013 00:03:59 +0800	[thread overview]
Message-ID: <20130123160354.GE4565@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1358757312.11746.11.camel@dhruva>

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

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?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-01-23 16:04 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 ` Ashish Jangam
2013-01-23 16:03   ` Mark Brown [this message]
2013-01-25  8:26     ` Ashish Jangam
     [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=20130123160354.GE4565@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ashish.jangam@kpitcummins.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome