From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
To: linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: [PATCH] ssb: Add support for new ChipCommon
Date: Sat, 26 Aug 2006 13:31:00 +0200 [thread overview]
Message-ID: <200608261331.00527.mb@bu3sch.de> (raw)
In-Reply-To: <200608261233.32336.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
Oops, sorry. Please drop this.
This patch is wrong and I will submit a correct one, soon.
a 0x900 core does not exist. Instead the meaning of the
revision bits changed slightly.
On Saturday 26 August 2006 12:33, Michael Buesch wrote:
> Hi John,
>
> Please apply this to wireless-dev.
>
> --
>
> This adds support for the new 0x900 ChipCommon core.
>
> Signed-off-by: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
>
> Index: wireless-dev/drivers/misc/ssb.c
> ===================================================================
> --- wireless-dev.orig/drivers/misc/ssb.c 2006-08-24 22:33:44.000000000 +0200
> +++ wireless-dev/drivers/misc/ssb.c 2006-08-26 12:28:31.000000000 +0200
> @@ -648,7 +648,7 @@
>
> ssb->chipcommon_capabilities = 0;
> ssb->nr_cores = 0;
> - if (cc == SSB_CC_CHIPCOMMON) {
> + if (cc == SSB_CC_CHIPCOMMON || cc == SSB_CC_CHIPCOMMON2) {
> tmp = ssb_read32(ssb, SSB_CHIPCOMMON_CHIPID);
>
> ssb->chip_id = (tmp & SSB_CHIPCOMMON_IDMASK);
> @@ -656,7 +656,7 @@
> SSB_CHIPCOMMON_REVSHIFT;
> ssb->chip_package = (tmp & SSB_CHIPCOMMON_PACKMASK) >>
> SSB_CHIPCOMMON_PACKSHIFT;
> - if (rev >= 4) {
> + if (rev >= 4 || cc == SSB_CC_CHIPCOMMON2) {
> ssb->nr_cores = (tmp & SSB_CHIPCOMMON_NRCORESMASK) >>
> SSB_CHIPCOMMON_NRCORESSHIFT;
> }
> Index: wireless-dev/include/linux/ssb.h
> ===================================================================
> --- wireless-dev.orig/include/linux/ssb.h 2006-08-24 22:28:03.000000000 +0200
> +++ wireless-dev/include/linux/ssb.h 2006-08-26 12:26:11.000000000 +0200
> @@ -251,6 +251,7 @@
> #define SSB_CC_MINI_MACPHY 0x823
> #define SSB_CC_ARM_1176 0x824
> #define SSB_CC_ARM_7TDMI 0x825
> +#define SSB_CC_CHIPCOMMON2 0x900
>
>
> /* ChipCommon core registers. */
>
>
--
Greetings Michael.
prev parent reply other threads:[~2006-08-26 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-26 10:33 [PATCH] ssb: Add support for new ChipCommon Michael Buesch
[not found] ` <200608261233.32336.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-08-26 11:31 ` Michael Buesch [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=200608261331.00527.mb@bu3sch.de \
--to=mb-fseuscv1ubazqb+pc5nmwq@public.gmane.org \
--cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@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 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.