All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: sameo@linux.intel.com, lee.jones@linaro.org,
	linux-kernel@vger.kernel.org, kyungmin.park@samsung.com
Subject: Re: [PATCH] mfd: max77693: Fix up bug of wrong interrupt number
Date: Mon, 04 Nov 2013 10:58:20 +0900	[thread overview]
Message-ID: <5276FF3C.9050304@samsung.com> (raw)
In-Reply-To: <1381367155-4888-1-git-send-email-cw00.choi@samsung.com>

Ping!

Thanks,
Chanwoo Choi

On 10/10/2013 10:05 AM, Chanwoo Choi wrote:
> The max77693 MFD device use irq domain method which has hardware interrupt number
> and virtual interrupt number getting through irq domain mapping. This patch
> use hardware interrupt number instead of virtual interrupt number to get
> struct irq_data.
> 
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
>  drivers/mfd/max77693-irq.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/mfd/max77693-irq.c b/drivers/mfd/max77693-irq.c
> index 1029d01..66b58fe 100644
> --- a/drivers/mfd/max77693-irq.c
> +++ b/drivers/mfd/max77693-irq.c
> @@ -128,7 +128,8 @@ static void max77693_irq_sync_unlock(struct irq_data *data)
>  static const inline struct max77693_irq_data *
>  irq_to_max77693_irq(struct max77693_dev *max77693, int irq)
>  {
> -	return &max77693_irqs[irq];
> +	struct irq_data *data = irq_get_irq_data(irq);
> +	return &max77693_irqs[data->hwirq];
>  }
>  
>  static void max77693_irq_mask(struct irq_data *data)
> 


  reply	other threads:[~2013-11-04  1:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10  1:05 [PATCH] mfd: max77693: Fix up bug of wrong interrupt number Chanwoo Choi
2013-11-04  1:58 ` Chanwoo Choi [this message]
2013-11-04  8:42   ` Samuel Ortiz
2013-11-04 10:01     ` Chanwoo Choi

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=5276FF3C.9050304@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.