From: Kevin Hilman <khilman@ti.com>
To: Keerthy <j-keerthy@ti.com>
Cc: linux-omap@vger.kernel.org, tony@atomide.com, rnayak@ti.com
Subject: Re: [RFC PATCH 1/6 V2] OMAP4: Clock: Associate clocks for OMAP temperature sensor
Date: Mon, 29 Aug 2011 14:47:21 -0700 [thread overview]
Message-ID: <87bov7rity.fsf@ti.com> (raw)
In-Reply-To: <1313664735-8917-2-git-send-email-j-keerthy@ti.com> (Keerthy's message of "Thu, 18 Aug 2011 16:22:10 +0530")
Keerthy <j-keerthy@ti.com> writes:
> div_ts_ck feeds only the temperature sensor functional clock
> and also has a clksel associated (for divider selection). Mapping this
> as the functional clock for the temperature sensor in clkdev table,
> so a clk_set_rate() in the driver would have the effect of changing the
> temperature sensor clock rate indirectly.
>
> Reviewd-by: Rajendra Nayak <rnayak@ti.com>
s/Reviewd/Reviewed/
next prev parent reply other threads:[~2011-08-29 21:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 10:52 [RFC PATCH 0/6 V2] OMAP4: Temperature sensor driver Keerthy
2011-08-18 10:52 ` [RFC PATCH 1/6 V2] OMAP4: Clock: Associate clocks for OMAP temperature sensor Keerthy
2011-08-29 21:47 ` Kevin Hilman [this message]
2011-08-18 10:52 ` [RFC PATCH 2/6 V2] OMAP4: Adding the temperature sensor register set bit fields Keerthy
2011-08-29 21:52 ` Kevin Hilman
2011-08-18 10:52 ` [RFC PATCH 3/6 V2] OMAP4460: Temperature sensor data Keerthy
2011-08-18 11:32 ` Felipe Balbi
2011-08-18 10:52 ` [RFC PATCH 4/6 V2] OMAP4: Hwmod: OMAP temperature sensor Keerthy
2011-08-18 10:52 ` [RFC PATCH 5/6 V2] OMAP4: Temperature sensor device support Keerthy
2011-08-19 5:47 ` Todd Poynor
2011-08-18 10:52 ` [RFC PATCH 6/6 V2] hwmon: OMAP4: On die temperature sensor driver Keerthy
2011-08-18 11:37 ` Felipe Balbi
2011-08-22 4:29 ` J, KEERTHY
2011-08-22 9:24 ` Felipe Balbi
2011-08-19 2:13 ` Guenter Roeck
2011-08-19 6:04 ` J, KEERTHY
2011-08-19 6:17 ` Guenter Roeck
2011-08-19 13:01 ` J, KEERTHY
2011-08-19 13:48 ` Guenter Roeck
2011-08-19 9:04 ` J, KEERTHY
2011-08-19 12:53 ` J, KEERTHY
2011-08-19 5:34 ` Todd Poynor
2011-08-22 4:40 ` J, KEERTHY
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=87bov7rity.fsf@ti.com \
--to=khilman@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
--cc=tony@atomide.com \
/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).