public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "J, KEERTHY" <j-keerthy@ti.com>
Cc: daniel.lezcano@linaro.org, tglx@linutronix.de,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	baolin.wang@linaro.org, d-gerlach@ti.com,
	grygorii.strashko@ti.com, t-kristo@ti.com,
	Lokesh Vutla <lokeshvutla@ti.com>
Subject: Re: [PATCH] clocksource: ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs
Date: Wed, 8 Aug 2018 06:50:31 -0700	[thread overview]
Message-ID: <20180808135031.GT99251@atomide.com> (raw)
In-Reply-To: <0f6601d6-5b14-8d1f-65db-2b8b5a50397d@ti.com>

* J, KEERTHY <j-keerthy@ti.com> [180808 13:14]:
> 
> 
> On 8/8/2018 12:28 PM, Tony Lindgren wrote:
> > * Keerthy <j-keerthy@ti.com> [180807 09:29]:
> > > The 32k clocksource is NONSTOP for non-am43 SoCs. Hence
> > > add the flag for all the other SoCs.
> > > 
> > > Reported-by: Tony Lindgren <tony@atomide.com>
> > > Signed-off-by: Keerthy <j-keerthy@ti.com>
> > 
> > Acked-by: Tony Lindgren <tony@atomide.com>
> 
> Thanks Tony. Lokesh pointed out about am43x-epos. So will make a minor
> correction to this patch with compatible. I searched all the am4 boards &
> seems like ti,am43 is the most generic compatible cover am43x-epos as well.
> So i will retain your ack and send a v2 with am43 compatible changed to a
> more generic ti,am43.

OK makes sense to me thanks.

Tony

      reply	other threads:[~2018-08-08 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07  9:25 [PATCH] clocksource: ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs Keerthy
2018-08-08  6:58 ` Tony Lindgren
2018-08-08 13:10   ` J, KEERTHY
2018-08-08 13:50     ` 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=20180808135031.GT99251@atomide.com \
    --to=tony@atomide.com \
    --cc=baolin.wang@linaro.org \
    --cc=d-gerlach@ti.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=grygorii.strashko@ti.com \
    --cc=j-keerthy@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=t-kristo@ti.com \
    --cc=tglx@linutronix.de \
    /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