From: Nishanth Menon <nm@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Jyri Sarha <jsarha@ti.com>,
dri-devel@lists.freedesktop.org, airlied@linux.ie,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
bcousson@baylibre.com, alsa-devel@alsa-project.org,
Mike Turquette <mturquette@linaro.org>
Cc: tony@atomide.com, broonie@kernel.org,
liam.r.girdwood@linux.intel.com, peter.ujfalusi@ti.com,
detheridge@ti.com, t-kristo@ti.com
Subject: Re: [PATCH v3 1/5] clk: ti: add "ti,gpio-gate-clock" controlled clock
Date: Fri, 19 Sep 2014 08:12:40 -0500 [thread overview]
Message-ID: <541C2BC8.3020207@ti.com> (raw)
In-Reply-To: <541C2A77.9070406@ti.com>
On 09/19/2014 08:07 AM, Tomi Valkeinen wrote:
> On 16/09/14 23:40, Jyri Sarha wrote:
>> The added ti,gpio-gate-clock is a basic clock that can be enabled and
>> disabled trough a gpio output. The DT binding document for the clock
>> is also added. For EPROBE_DEFER handling the registering of the clock
>> has to be delayed until of_clk_get() call time.
>>
>> Signed-off-by: Jyri Sarha <jsarha@ti.com>
>> ---
>> .../bindings/clock/ti/gpio-gate-clock.txt | 21 ++
>> drivers/clk/ti/Makefile | 2 +-
>> drivers/clk/ti/gpio.c | 202 ++++++++++++++++++++
>> 3 files changed, 224 insertions(+), 1 deletion(-)
>> create mode 100644 Documentation/devicetree/bindings/clock/ti/gpio-gate-clock.txt
>> create mode 100644 drivers/clk/ti/gpio.c
>
> Why is this a TI clock? Sounds like a generic one to me.
Like thread: https://lkml.org/lkml/2014/9/5/284 ?
>
> In any case, this should go through Mike.
>
yep - should have been posted independent of this series :).
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-09-19 13:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 20:40 [PATCH v3 0/5] Beaglebone-Black HDMI audio Jyri Sarha
2014-09-16 20:40 ` [PATCH v3 1/5] clk: ti: add "ti,gpio-gate-clock" controlled clock Jyri Sarha
2014-09-19 13:07 ` Tomi Valkeinen
2014-09-19 13:12 ` Nishanth Menon [this message]
2014-09-19 13:25 ` Tomi Valkeinen
2014-09-26 23:56 ` Mike Turquette
2014-09-16 20:40 ` [PATCH v3 2/5] drm/tilcdc: Add I2S HDMI audio config for tda998x Jyri Sarha
[not found] ` <cover.1410898073.git.jsarha-l0cyMroinI0@public.gmane.org>
2014-09-16 20:40 ` [PATCH v3 3/5] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus Jyri Sarha
2014-09-16 20:40 ` [PATCH v3 5/5] ARM: dts: am335x-boneblack: Add HDMI audio support Jyri Sarha
2014-09-29 6:41 ` Jyri Sarha
2014-09-16 20:40 ` [PATCH v3 4/5] ASoC: davinci: HDMI audio build for AM33XX and TDA998x Jyri Sarha
2014-09-17 19:41 ` Mark Brown
2014-09-17 21:13 ` Jyri Sarha
2014-09-18 8:25 ` Jean-Francois Moine
2014-09-18 18:36 ` Jyri Sarha
2014-09-17 1:06 ` [alsa-devel] [PATCH v3 0/5] Beaglebone-Black HDMI audio Dave Airlie
[not found] ` <CAPM=9txRReSdcB5j+0dKmrDNM94zANu-q7ZfWHtP2iA54Dieig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-17 7:51 ` Jyri Sarha
2014-09-19 13:24 ` Tomi Valkeinen
2014-09-19 13:59 ` Jyri Sarha
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=541C2BC8.3020207@ti.com \
--to=nm@ti.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=bcousson@baylibre.com \
--cc=broonie@kernel.org \
--cc=detheridge@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@ti.com \
--cc=tomi.valkeinen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.