From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv11 2/8] ARM: OMAP2+: hwmod: Add API to check IO PAD wakeup status
Date: Wed, 14 Dec 2011 12:13:09 +0200 [thread overview]
Message-ID: <1323857589.14920.6.camel@sokoban> (raw)
In-Reply-To: <alpine.DEB.2.00.1112132002070.12046@utopia.booyaka.com>
On Tue, 2011-12-13 at 20:04 -0700, Paul Walmsley wrote:
> Hi Tero
>
> looking at this patch:
>
> On Mon, 12 Dec 2011, Tero Kristo wrote:
>
> > From: R, Govindraj <govindraj.raja@ti.com>
> >
> > Add API to determine IO-PAD wakeup event status for a given
> > hwmod dynamic_mux pad.
> >
> > Signed-off-by: Govindraj.R <govindraj.raja@ti.com>
>
> It seems that your last patch drops the following code that this patch
> adds:
Hmm yea true, it seems like the code in patch 2 does not exist anymore
after patch 8, and well, the code in patch 2 was never used for anything
anyway. Sorry for not spotting this myself, I added patch 8 in hurry to
this set.
>
> > diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c
> > index 8d37d83..d7f4623 100644
> > --- a/arch/arm/mach-omap2/omap_hwmod.c
> > +++ b/arch/arm/mach-omap2/omap_hwmod.c
> > @@ -2721,3 +2721,10 @@ int omap_hwmod_no_setup_reset(struct omap_hwmod *oh)
> >
> > return 0;
> > }
> > +
> > +int omap_hwmod_pad_get_wakeup_status(struct omap_hwmod *oh)
> > +{
> > + if (oh && oh->mux)
> > + return omap_hwmod_mux_get_wake_status(oh->mux);
> > + return -EINVAL;
> > +}
> > diff --git a/arch/arm/plat-omap/include/plat/omap_hwmod.h b/arch/arm/plat-omap/include/plat/omap_hwmod.h
> > index 8b372ed..1b81dfb 100644
> > --- a/arch/arm/plat-omap/include/plat/omap_hwmod.h
> > +++ b/arch/arm/plat-omap/include/plat/omap_hwmod.h
> > @@ -604,6 +604,7 @@ int omap_hwmod_get_context_loss_count(struct omap_hwmod *oh);
> >
> > int omap_hwmod_no_setup_reset(struct omap_hwmod *oh);
> >
> > +int omap_hwmod_pad_get_wakeup_status(struct omap_hwmod *oh);
> > /*
> > * Chip variant-specific hwmod init routines - XXX should be converted
> > * to use initcalls once the initial boot ordering is straightened out
>
> It's best in these circumstances to modify this patch not to add the code
> in the first place. Otherwise this creates needless churn which plenty of
> people are quite sensitized to. So, dropping these from patch 2.
Yeah, good call.
-Tero
next prev parent reply other threads:[~2011-12-14 10:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 18:15 [PATCHv11 0/8] OMAP3+: PRCM chain handler Tero Kristo
2011-12-12 18:15 ` [PATCHv11 1/8] ARM: OMAP2+: hwmod: Add API to enable IO ring wakeup Tero Kristo
2011-12-13 20:51 ` Paul Walmsley
2011-12-13 21:04 ` Paul Walmsley
2011-12-13 21:33 ` Paul Walmsley
2011-12-14 2:34 ` Paul Walmsley
2011-12-14 10:02 ` Tero Kristo
2011-12-12 18:15 ` [PATCHv11 2/8] ARM: OMAP2+: hwmod: Add API to check IO PAD wakeup status Tero Kristo
2011-12-13 0:28 ` Tony Lindgren
2011-12-13 22:16 ` Paul Walmsley
2011-12-13 22:28 ` Tony Lindgren
2011-12-13 22:38 ` Paul Walmsley
2011-12-13 22:48 ` Tony Lindgren
2011-12-14 2:22 ` Paul Walmsley
2011-12-14 10:17 ` Tero Kristo
2011-12-14 3:04 ` Paul Walmsley
2011-12-14 10:13 ` Tero Kristo [this message]
2011-12-12 18:15 ` [PATCHv11 3/8] ARM: OMAP: prm: add support for chain interrupt handler Tero Kristo
2011-12-13 0:27 ` Tony Lindgren
2011-12-12 18:15 ` [PATCHv11 4/8] ARM: OMAP: prcm: add suspend prepare / finish support Tero Kristo
2011-12-12 18:15 ` [PATCHv11 5/8] ARM: OMAP2+: mux: add support for PAD wakeup interrupts Tero Kristo
2011-12-13 0:24 ` Tony Lindgren
2011-12-12 18:15 ` [PATCHv11 6/8] ARM: OMAP3: pm: use prcm chain handler Tero Kristo
2011-12-12 18:15 ` [PATCHv11 7/8] ARM: OMAP3: pm: do not enable PRCM MPU interrupts manually Tero Kristo
2011-12-12 18:15 ` [PATCHv11 8/8] ARM: OMAP: mux: add support for selecting mpu_irq for each wakeup pad Tero Kristo
2011-12-13 0:25 ` Tony Lindgren
2011-12-13 0:33 ` [PATCHv11 0/8] OMAP3+: PRCM chain handler Kevin Hilman
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=1323857589.14920.6.camel@sokoban \
--to=t-kristo@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).