From: Paul Bolle <pebolle@tiscali.nl>
To: Martyn Welch <martyn.welch@ge.com>
Cc: gregkh@suse.de, Grant Likely <grant.likely@secretlab.ca>,
devel@driverdev.osuosl.org, manohar.vanga@cern.ch,
cota@braap.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Driver for GE PIO2 VME Card
Date: Mon, 07 Nov 2011 10:55:29 +0100 [thread overview]
Message-ID: <1320659729.14409.349.camel@x61.thuisdomein> (raw)
In-Reply-To: <4EB7A60D.801@ge.com>
On Mon, 2011-11-07 at 09:34 +0000, Martyn Welch wrote:
> On 04/11/11 19:55, Paul Bolle wrote:
> >> + implementing 32 solid-state relay switched IO lines, in 4 groups of 8.
> >> + The IO lines are provided as input, output or both as a build time
> >> + option.
> >
> > What option would that be?
>
> I think "Each bank of IO lines is pre-configured as input, output or both
> depending on the variant of the card" may be a bit clearer?
So this concerns a physical build option! Anything that makes that clear
(like your alternative does) is fine with me. (Perhaps "is
pre-configured" could be "functions", as that's less ambiguous in a
Kconfig file, but that's debatable.)
> > All module parameters have a sysfs visibility (or permission) of zero.
> > Why is that? (This might very well be a naive question. But I often
> > wonder why a certain parameter's permission isn't at least 400, just to
> > allow a quick check of that parameter.) Are arrays tricky in sysfs?
>
> Hadn't really thought about it to be honest. There seems to be plenty of
> examples where it's set to non-zero.
(Perhaps you meant to write "set to zero" here.)
Greg already explained that it's OK to leave the code as is for now
(since all these control knobs need to be provided via "real" sysfs
files in the long run anyhow).
Paul Bolle
next prev parent reply other threads:[~2011-11-07 9:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 17:33 Martyn Welch
2011-11-04 17:38 ` Martyn Welch
2011-11-04 19:55 ` Paul Bolle
2011-11-04 20:00 ` Greg KH
2011-11-07 10:37 ` Martyn Welch
2011-11-07 23:05 ` Greg KH
2011-11-07 9:34 ` Martyn Welch
2011-11-07 9:55 ` Paul Bolle [this message]
2011-11-07 11:10 ` Martyn Welch
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=1320659729.14409.349.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=cota@braap.org \
--cc=devel@driverdev.osuosl.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manohar.vanga@cern.ch \
--cc=martyn.welch@ge.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
all inboxes | Powered by JetHome®