From: "Michael Büsch" <mb@bu3sch•de>
To: George Kashperko <george@znau•edu.ua>
Cc: linux-next@vger•kernel.org
Subject: Re: [PATCH] Fix SSB chipcommon HT/ALP avail bits layout and usage
Date: Mon, 07 Feb 2011 20:55:56 +0100 [thread overview]
Message-ID: <1297108556.18125.1.camel@maggie> (raw)
In-Reply-To: <1297107730.32607.10.camel@dev.znau.edu.ua> (sfid-20110207_204928_918460_412E3BD6)
On Mon, 2011-02-07 at 21:42 +0200, George Kashperko wrote:
> BCM4328 chipcommon have different CLKCTLST register HT and ALP availability
> bits' layout comparing to other BCM chips. 4328 HT/ALP availability bits are
> 16/17 whereas other BCM chips' HT/ALP availability bits are 17/16. Therefore
> current pmu pll initialization code forces active low power clock for all
> non-4328 chips instead of switching HT clock on.
> Patch also fixes typo in ALP avail define description.
Where did you get the knowledge that the bits are swapped on 4328 from?
--
Greetings Michael.
next prev parent reply other threads:[~2011-02-07 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 19:42 [PATCH] Fix SSB chipcommon HT/ALP avail bits layout and usage George Kashperko
2011-02-07 19:55 ` Michael Büsch [this message]
2011-02-07 21:14 ` George Kashperko
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=1297108556.18125.1.camel@maggie \
--to=mb@bu3sch$(echo .)de \
--cc=george@znau$(echo .)edu.ua \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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