From: Pavel Machek <pavel@ucw.cz>
To: "Stephen Blackheath [to Foxconn]" <stephen@symmetric.co.nz>
Cc: David Sterba <dsterba@suse.cz>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
jkosina@suse.cz, benm@symmetric.co.nz
Subject: Re: [PATCH] ipwireless: driver for 3G PC Card
Date: Thu, 31 Jan 2008 00:15:21 +0100 [thread overview]
Message-ID: <20080130231521.GA5937@elf.ucw.cz> (raw)
In-Reply-To: <47A0EC3A.1040502@symmetric.co.nz>
On Thu 2008-01-31 10:29:30, Stephen Blackheath [to Foxconn] wrote:
> Pavel & all,
>
>
> Pavel Machek wrote:
>
> >> +/* I/O ports and bit definitions for version 2 of the hardware */
> >> +
> >> +struct MEMCCR {
> >> + unsigned short PCCOR; /* Configuration Option Register */
> >> + unsigned short PCCSR; /* Configuration and Status Register */
> >> + unsigned short PCPRR; /* Pin Replacemant Register */
> >> + unsigned short PCSCR; /* Socket and Copy Register */
> >> + unsigned short PCESR; /* Extendend Status Register */
> >> + unsigned short PCIOB; /* I/O Base Register */
> >> +};
> > Could we get better names? PCIOB is cryptic, pci_io_base is pretty
> > good.
> >
> >
> We should keep these names because they are part of the interface
> between host and card defined by the manufacturer.
No. Use sensible names, and put manufacturer-defined 5-letter crap in
the comments. Heck, notice that they just took first letter of each
word of good name....
> > Is some locking needed around *hw?
> >
> I don't think so, but I'm happy to be corrected.
You have a structure, and are accessing its fields from interrupts. I
assume you access the fields outside interrupt, too? As the fields are
not of atomic_t, I believe you need locking.
(Oh, and I should have said that earlier: Thanks for the driver and
congratulations for getting it this far).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-01-30 23:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 17:19 [PATCH] ipwireless: driver for 3G PC Card David Sterba
2008-01-28 17:53 ` Alexey Dobriyan
2008-01-30 13:28 ` Pavel Machek
2008-01-28 18:08 ` Randy Dunlap
2008-01-28 23:18 ` Jiri Slaby
2008-01-28 23:28 ` Randy Dunlap
2008-01-28 23:29 ` Jiri Slaby
2008-01-28 23:33 ` Randy Dunlap
2008-01-29 6:22 ` Pekka Enberg
2008-01-29 13:42 ` David Sterba
2008-01-29 13:40 ` David Sterba
2008-01-30 13:40 ` Pavel Machek
2008-01-30 21:29 ` Stephen Blackheath [to Foxconn]
2008-01-30 23:15 ` Pavel Machek [this message]
2008-02-01 15:21 ` David Sterba
2008-02-01 23:43 ` Pavel Machek
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=20080130231521.GA5937@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=benm@symmetric.co.nz \
--cc=dsterba@suse.cz \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=stephen@symmetric.co.nz \
--cc=torvalds@linux-foundation.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