From: Samuel Ortiz <sameo@linux.intel.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: gg@slimlogic.co.uk, broonie@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org, swarren@nvidia.com,
ian@slimlogic.co.uk
Subject: Re: [PATCH V2] mfd: palmas: provide irq flags through DT/platform data
Date: Wed, 13 Mar 2013 09:37:20 +0100 [thread overview]
Message-ID: <20130313083720.GD21994@zurbaran> (raw)
In-Reply-To: <1362149026-21170-1-git-send-email-ldewangan@nvidia.com>
Hi Laxman,
On Fri, Mar 01, 2013 at 08:13:46PM +0530, Laxman Dewangan wrote:
> Currently driver sets the irq type to IRQF_TRIGGER_LOW which is
> causing interrupt registration failure in ARM based SoCs as:
> [ 0.208479] genirq: Setting trigger mode 8 for irq 118 failed (gic_set_type+0x0/0xf0)
> [ 0.208513] dummy 0-0059: Failed to request IRQ 118: -22
>
> Provide the irq flags through platform data if device is registered
> through board file or get the irq type from DT node property in place
> of hardcoding the irq flag in driver to support multiple platforms.
>
> Also configure the device to generate the interrupt signal according to
> flag type.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> Changes from V1:
> - Use palmas_update_bits() for rea/modiy/write.
>
> drivers/mfd/palmas.c | 36 +++++++++++++++++++++++++++++++++---
> include/linux/mfd/palmas.h | 1 +
> 2 files changed, 34 insertions(+), 3 deletions(-)
Patch applied to my mfd-fixes tree now.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2013-03-13 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 14:43 Laxman Dewangan
2013-03-13 8:37 ` Samuel Ortiz [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=20130313083720.GD21994@zurbaran \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=ian@slimlogic.co.uk \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®