From: "Michael Büsch" <mb@bu3sch.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: George Kashperko <george@znau.edu.ua>,
linux-wireless@vger.kernel.org,
b43-dev <b43-dev@lists.infradead.org>
Subject: Re: [RFC] How to rename SSB_TMSLOW_*, B43_TMSLOW_*?
Date: Wed, 16 Feb 2011 23:17:37 +0100 [thread overview]
Message-ID: <1297894657.32237.2.camel@maggie> (raw)
In-Reply-To: <AANLkTimKE+WqChVf0XpeHsfHxT8=3vbnBh=Lo+1tLSwj@mail.gmail.com> (sfid-20110216_141342_431478_3C8E43BA)
On Wed, 2011-02-16 at 14:13 +0100, Rafał Miłecki wrote:
> Except for following 3 defines:
> #define SSB_TMSLOW_RESET 0x00000001 /* Reset */
> #define SSB_TMSLOW_REJECT_22 0x00000002 /* Reject (Backplane rev 2.2) */
> #define SSB_TMSLOW_REJECT_23 0x00000004 /* Reject (Backplane rev 2.3) */
>
> All our SSB_TMSLOW_* and B43_TMSLOW_* defines are some core control
> bits. As we now know, core control bits are not SSB specific or TMSLOW
> specific.
>
> Should we (and how) define that names in this situation?
>
> For b43 I propose (quite obvious?) B43_CORE_CTL_*.
>
> However what about SSB_TMSLOW_*? George proposed SSB_CORECTL_*, but it
> contains "SSB", while that bits are not SSB specific. Same bits are
> used on AI bus. Should we use some SSBAI_CORE_CTL_* then? Any other
> ideas? Some better maybe?
>
> P.S.
> Personally I prefer CORE_CTL over CORECTL (George). Which one should we use?
Let's simply put those bits into the drivers and call them
DRIVERNAME_TMSLOW_FOOBAR
The "TMSLOW" part seems rather important to me, because that makes it
obvious what register these bits belong to. Note that's there's also
TMSHIGH. It also follows current naming convention.
--
Greetings Michael.
next prev parent reply other threads:[~2011-02-16 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 13:13 [RFC] How to rename SSB_TMSLOW_*, B43_TMSLOW_*? Rafał Miłecki
2011-02-16 14:58 ` George Kashperko
2011-02-16 22:17 ` Michael Büsch [this message]
2011-02-17 12:14 ` Rafał Miłecki
2011-02-17 22:00 ` Michael Büsch
2011-02-17 22:15 ` Rafał Miłecki
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=1297894657.32237.2.camel@maggie \
--to=mb@bu3sch.de \
--cc=b43-dev@lists.infradead.org \
--cc=george@znau.edu.ua \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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 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).