linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Thierry Reding
	<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: tegra: Add clocks property to TWD node
Date: Tue, 12 Feb 2013 12:29:16 -0700	[thread overview]
Message-ID: <511A980C.5050405@wwwdotorg.org> (raw)
In-Reply-To: <1360684611-11152-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>

On 02/12/2013 08:56 AM, Thierry Reding wrote:
> The generic ARM TWD code has recently gained support for looking up the
> clock from DT. Adding the appropriate clocks property allows the driver
> to successfully register the clock event device.
> 
> Signed-off-by: Thierry Reding <thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
> ---
> Note that the binding documentation says that the twd clock is 132 on
> Tegra20, but according to drivers/clk/tegra/clk-tegra20.c it is in fact
> 130. The patch doesn't update the binding documentation because some
> other offsets are probably also wrong and I didn't have the time to go
> through all of them.

The driver is buggy in that it doesn't match the DT bindings. I'll send
a patch to fix that up very soon. Then this patch can be rebased.

      parent reply	other threads:[~2013-02-12 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 15:56 [PATCH] ARM: tegra: Add clocks property to TWD node Thierry Reding
     [not found] ` <1360684611-11152-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2013-02-12 19:29   ` Stephen Warren [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=511A980C.5050405@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.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).