From: rogerq@ti.com (Roger Quadros)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: am437x-gp-evm: Add wakeup interrupt source for pixcir_i2c_ts
Date: Wed, 14 Oct 2015 11:46:19 +0300 [thread overview]
Message-ID: <561E165B.3000907@ti.com> (raw)
In-Reply-To: <1444801956-17817-1-git-send-email-vigneshr@ti.com>
+Dave
On 14/10/15 08:52, Vignesh R wrote:
> On am437x-gp-evm, pixcir_i2c_ts can wakeup the system from lower power
> state via pinctrl and IO daisy chain using generic wakeirq framework.
> With commit 3fffd1283927 ("i2c: allow specifying separate wakeup
> interrupt in device tree") i2c core allows optional wakeirq to be
> specified via device tree. Add wakeup irq entry to enable pixcir_i2c_ts
> to wake the system from low power state.
>
> Signed-off-by: Vignesh R <vigneshr@ti.com>
> ---
> arch/arm/boot/dts/am437x-gp-evm.dts | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am437x-gp-evm.dts b/arch/arm/boot/dts/am437x-gp-evm.dts
> index 22038f21f228..69e93af7df0d 100644
> --- a/arch/arm/boot/dts/am437x-gp-evm.dts
> +++ b/arch/arm/boot/dts/am437x-gp-evm.dts
> @@ -581,8 +581,13 @@
>
> attb-gpio = <&gpio3 22 GPIO_ACTIVE_HIGH>;
>
> + interrupts-extended = <&gpio3 22 GPIO_ACTIVE_HIGH>,
> + <&am43xx_pinmux 0x264>;
How does this work?
interrupts-extended property must have
1) interrupt parent
2) interrupt number
3) interrupt flags
Your change doesn't seem to comply with those requirements.
> + interrupt-names = "tsc", "wakeup";
> +
> touchscreen-size-x = <1024>;
> touchscreen-size-y = <600>;
> + wakeup-source;
> };
>
> ov2659 at 30 {
>
cheers,
-roger
next prev parent reply other threads:[~2015-10-14 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 5:52 [PATCH] ARM: dts: am437x-gp-evm: Add wakeup interrupt source for pixcir_i2c_ts Vignesh R
2015-10-14 8:46 ` Roger Quadros [this message]
2015-10-14 9:12 ` Vignesh R
2015-10-14 11:04 ` Roger Quadros
2015-10-14 11:37 ` Vignesh R
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=561E165B.3000907@ti.com \
--to=rogerq@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).