devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Qing Xu <qingx@marvell.com>
Cc: "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	"haojian.zhuang@gmail.com" <haojian.zhuang@gmail.com>,
	Chao Xie <cxie4@marvell.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"sameo@linux.intel.com" <sameo@linux.intel.com>
Subject: Re: [PATCH 3/7] mfd: max8925: fix onkey driver irq base
Date: Thu, 22 Nov 2012 23:41:58 -0800	[thread overview]
Message-ID: <20121123074158.GD12631@core.coreip.homeip.net> (raw)
In-Reply-To: <50AF23AB.3010002@marvell.com>

Hi Qing,

On Fri, Nov 23, 2012 at 03:20:11PM +0800, Qing Xu wrote:
> On 11/06/2012 03:39 PM, Qing Xu wrote:
> >From: Qing Xu <qingx@marvell.com>
> >
> >update onkey driver's irq base, it should get from max8925,
> >but not save in a private value
> >
> >Signed-off-by: Qing Xu <qingx@marvell.com>
> >---
> >  drivers/input/misc/max8925_onkey.c |    3 ---
> >  drivers/mfd/max8925-core.c         |    2 +-
> >  2 files changed, 1 insertions(+), 4 deletions(-)
> >
> >diff --git a/drivers/input/misc/max8925_onkey.c b/drivers/input/misc/max8925_onkey.c
> >index 0a12b74..6527789 100644
> >--- a/drivers/input/misc/max8925_onkey.c
> >+++ b/drivers/input/misc/max8925_onkey.c
> >@@ -100,9 +100,6 @@ static int __devinit max8925_onkey_probe(struct platform_device *pdev)
> >  	input->dev.parent = &pdev->dev;
> >  	input_set_capability(input, EV_KEY, KEY_POWER);
> >-	irq[0] += chip->irq_base;
> >-	irq[1] += chip->irq_base;
> >-
> >  	error = request_threaded_irq(irq[0], NULL, max8925_onkey_handler,
> >  				     IRQF_ONESHOT, "onkey-down", info);
> >  	if (error < 0) {
> >diff --git a/drivers/mfd/max8925-core.c b/drivers/mfd/max8925-core.c
> >index b1eacae..37a372d 100644
> >--- a/drivers/mfd/max8925-core.c
> >+++ b/drivers/mfd/max8925-core.c
> >@@ -881,7 +881,7 @@ int __devinit max8925_device_init(struct max8925_chip *chip,
> >  	ret = mfd_add_devices(chip->dev, 0, &onkey_devs[0],
> >  			      ARRAY_SIZE(onkey_devs),
> >-			      NULL, 0, NULL);
> >+			      NULL, chip->irq_base, NULL);
> >  	if (ret < 0) {
> >  		dev_err(chip->dev, "Failed to add onkey subdev\n");
> >  		goto out_dev;
> Hi Dmitry,
> 
> Could you help to review my patch? Thanks a lot!
> 

Looks good to me.

Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

Thanks.

-- 
Dmitry

      reply	other threads:[~2012-11-23  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-06  7:39 [PATCH 3/7] mfd: max8925: fix onkey driver irq base Qing Xu
2012-11-23  7:20 ` Qing Xu
2012-11-23  7:41   ` Dmitry Torokhov [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=20121123074158.GD12631@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=cxie4@marvell.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qingx@marvell.com \
    --cc=rob.herring@calxeda.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;
as well as URLs for NNTP newsgroup(s).