linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] clk: tegra: fix blink clock rate
Date: Sun, 01 Dec 2013 12:21:17 -0700	[thread overview]
Message-ID: <529B8C2D.3000300@wwwdotorg.org> (raw)
In-Reply-To: <20131129152241.GM9712@ulmo.nvidia.com>

On 11/29/2013 08:22 AM, Thierry Reding wrote:
> On Wed, Nov 20, 2013 at 04:47:18PM -0700, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>> 
>> The blink clock rate needs to be configured, or it will run at
>> ~1Hz rather than the desired 32KHz. If it runs at the wrong rate,
>> e.g. the SDIO WiFi on Seaboard and Cardhu will fail to be
>> detected.
> 
> How is this related to WiFi?

The "blink" clock output from Tegra is connected to the WiFi module,
which then uses it for something; it probably has a PLL connected to
it that drives all the internal circuitry.

  parent reply	other threads:[~2013-12-01 19:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 23:47 [PATCH 1/5] clk: tegra: fix blink clock rate Stephen Warren
2013-11-20 23:47 ` [PATCH 2/5] clk: tegra: remove some redundant defines from Tegra114 Stephen Warren
2013-11-20 23:47 ` [PATCH 3/5] clk: tegra: remove some redundant defines from Tegra30 Stephen Warren
2013-11-20 23:47 ` [PATCH 4/5] clk: tegra: remove some redunant defines from Tegra20 Stephen Warren
2013-11-20 23:47 ` [PATCH 5/5] clk: tegra: remove some redundant defines from Tegra124 Stephen Warren
2013-11-22 13:45 ` [PATCH 1/5] clk: tegra: fix blink clock rate Peter De Schrijver
2013-11-29 15:22 ` Thierry Reding
2013-11-29 15:37   ` Thierry Reding
2013-12-01 19:21   ` Stephen Warren [this message]
2013-12-02  9:37     ` Thierry Reding

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=529B8C2D.3000300@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@lists.infradead.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).