[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <501236D3.3050505@nvidia.com>
Date: Fri, 27 Jul 2012 12:06:03 +0530
From: Laxman Dewangan <ldewangan@...dia.com>
To: Stephen Warren <swarren@...dotorg.org>
CC: Samuel Ortiz <sameo@...ux.intel.com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Liam Girdwood <lrg@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
Gyungoh Yoo <jack.yoo@...im-ic.com>,
Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH] mfd: add MAX8907 core driver
On Friday 27 July 2012 01:10 AM, Stephen Warren wrote:
> From: Gyungoh Yoo<jack.yoo@...im-ic.com>
>
> +static int max8907_irq_set_wake(struct irq_data *data, unsigned int on)
> +{
> + /* Everything happens in max8907_irq_sync_unlock */
> +
Probably you need to call the wake_enable of irq which goes to the cpu here.
> + if (device_may_wakeup(chip->dev))
> + enable_irq_wake(i2c->irq);
> + else
> + disable_irq(i2c->irq);
I think lets sub devices decide the wakeups rather than it is done by
the core.
> + max8907->i2c_rtc = i2c_new_dummy(i2c->adapter, MAX8907_RTC_I2C_ADDR);
> + if (!max8907->i2c_rtc) {
> + ret = -ENOMEM;
> + goto err_dummy_rtc;
> + }
> + i2c_set_clientdata(max8907->i2c_rtc, max8907);
> + max8907->regmap_rtc = devm_regmap_init_i2c(i2c,
> +&max8907_regmap_rtc_config);
the argiment should be max8907->i2c_rtc rather than i2c here.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists