From: Stephen Warren <swarren@wwwdotorg.org>
To: Prashant Gaikwad <pgaikwad@nvidia.com>
Cc: mturquette@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: Add missing cdev1 and cdev2 clocks
Date: Thu, 04 Apr 2013 12:18:59 -0600 [thread overview]
Message-ID: <515DC413.8050600@wwwdotorg.org> (raw)
In-Reply-To: <1365066333-2361-1-git-send-email-pgaikwad@nvidia.com>
On 04/04/2013 03:05 AM, Prashant Gaikwad wrote:
> Register cdev1 and cdev2 peripheral clocks.
Can you please explain the relationship between the following clocks:
cdev1
extern1
clk_out1
The latter two clocks already exist in this driver. I think that
clk_out1 is meant to represent cdev1 already, although it's set up to
point at some PMC registers, rather than the CAR CLK_ENB registers.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: tegra: Add missing cdev1 and cdev2 clocks
Date: Thu, 04 Apr 2013 12:18:59 -0600 [thread overview]
Message-ID: <515DC413.8050600@wwwdotorg.org> (raw)
In-Reply-To: <1365066333-2361-1-git-send-email-pgaikwad@nvidia.com>
On 04/04/2013 03:05 AM, Prashant Gaikwad wrote:
> Register cdev1 and cdev2 peripheral clocks.
Can you please explain the relationship between the following clocks:
cdev1
extern1
clk_out1
The latter two clocks already exist in this driver. I think that
clk_out1 is meant to represent cdev1 already, although it's set up to
point at some PMC registers, rather than the CAR CLK_ENB registers.
next prev parent reply other threads:[~2013-04-04 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 9:05 [PATCH] clk: tegra: Add missing cdev1 and cdev2 clocks Prashant Gaikwad
2013-04-04 9:05 ` Prashant Gaikwad
2013-04-04 9:05 ` Prashant Gaikwad
2013-04-04 18:18 ` Stephen Warren [this message]
2013-04-04 18:18 ` Stephen Warren
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=515DC413.8050600@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pgaikwad@nvidia.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.