linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap: dra7xx: Set OPT_CLKS_IN_RESET flag for gpio1
Date: Tue, 19 Sep 2017 10:44:45 -0700	[thread overview]
Message-ID: <20170919174444.GA5024@atomide.com> (raw)
In-Reply-To: <c8768202-96e1-8bda-7e09-ddf296c19c57@ti.com>

* Keerthy <j-keerthy@ti.com> [170918 04:40]:
> 
> 
> On Wednesday 06 September 2017 04:03 PM, Keerthy wrote:
> > gpio1 soft reset fails in the kexec path as the optional clock
> > is not enabled hence enable the HWMOD_CONTROL_OPT_CLKS_IN_RESET
> > flag for gpio1 hwmod.
> 
> A gentle ping on this as well.

With v4.14-rc1 now out, applying into omap-for-v4.14/fixes.
I usually don't start applying fixes during the merge window
unless really needed.

Regards,

Tony


> > Signed-off-by: Keerthy <j-keerthy@ti.com>
> > ---
> >  arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c b/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
> > index 7cc3247..6ae729a 100644
> > --- a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
> > +++ b/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
> > @@ -1037,6 +1037,7 @@ struct omap_hwmod dra7xx_sha0_hwmod = {
> >  	.name		= "gpio1",
> >  	.class		= &dra7xx_gpio_hwmod_class,
> >  	.clkdm_name	= "wkupaon_clkdm",
> > +	.flags		= HWMOD_CONTROL_OPT_CLKS_IN_RESET,
> >  	.main_clk	= "wkupaon_iclk_mux",
> >  	.prcm = {
> >  		.omap4 = {
> > 

      reply	other threads:[~2017-09-19 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06 10:33 [PATCH] arm: omap: dra7xx: Set OPT_CLKS_IN_RESET flag for gpio1 Keerthy
2017-09-18 11:39 ` Keerthy
2017-09-19 17:44   ` Tony Lindgren [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=20170919174444.GA5024@atomide.com \
    --to=tony@atomide.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).