public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Jangam <ashish.jangam@kpitcummins.com>
Cc: linux-kernel@vger.kernel.org, David Dajun Chen <dchen@diasemi.com>
Subject: Re: virtual irq isssue - regmap_irq
Date: Thu, 7 Mar 2013 22:22:21 +0800	[thread overview]
Message-ID: <20130307142218.GA19401@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1362657155.1796.4.camel@dhruva>

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

On Thu, Mar 07, 2013 at 05:22:35PM +0530, Ashish Jangam wrote:
> On Thu, 2013-03-07 at 15:13 +0800, Mark Brown wrote:

> > This is a bug in your platform which will affect anything using a linear
> > domain.  The platform isn't setting up its interrupts correctly so that
> > the core knows that those interrupts are reserved, ideally the platform
> > would just use domains for everything but at least irq_alloc_decs()
> > needs to know what is going on.

> Thanks I got this, however in this case should regmap handle such
> condition where domain is unknown?

There is no "condition" or unknown domain for regmap to handle.  regmap
asked its irqdomain for an interrupt number and was given one, it's got
no way of validating what it gets back and we don't want to end up
having workaround code all over the kernel for broken platforms.

> By the way, I was testing on smdkv6410 where Dialog device is not a
> component of the board.

The board is broken anyway; fix the board.

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

      reply	other threads:[~2013-03-07 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07  6:57 virtual irq isssue - regmap_irq Ashish Jangam
2013-03-07  7:13 ` Mark Brown
2013-03-07 11:52   ` Ashish Jangam
2013-03-07 14:22     ` 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=20130307142218.GA19401@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ashish.jangam@kpitcummins.com \
    --cc=dchen@diasemi.com \
    --cc=linux-kernel@vger.kernel.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