From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Karel Kulhavy <clock@twibright.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pcf8591 boot time parameters
Date: Thu, 30 Dec 2004 21:21:09 -0800 [thread overview]
Message-ID: <41D4E1C5.3040804@osdl.org> (raw)
In-Reply-To: <20041227140309.GA3361@beton.cybernet.src>
Karel Kulhavy wrote:
> Is it possible to configure pcf8591 driver using boot time commandline
> parameters?
>
> If yes, where are they described? I didn't find it. (<Help> doesn't say
> anything). also /linux-2.6.10/Documentation/i2c$ fgrep PCF * didn't reveal
> anything related.
>
> I only found documentation for module parameters by means of modinfo pcf8591
and what did it tell you? I see (when built as a loadable module,\
but they are still valid when built in-kernel):
parm: force:List of adapter,address pairs to boldly assume
to be present
parm: force_pcf8591:List of adapter,address pairs which are
unquestionably assumed to contain a `pcf8591' chip
parm: probe:List of adapter,address pairs to scan additionally
parm: ignore:List of adapter,address pairs not to scan
parm: input_mode:Analog input mode:
0 = four single ended inputs
1 = three differential inputs
2 = single ended and differential mixed
3 = two differential inputs
It seems that there is a list of i2c client parameters in
Documentation/i2c/writing-clients .
I don't know i2c, but any driver that #includes
linux/i2c.h has defined for it these parameters:
probe, probe_range
ignore, ignore_range
force
and any driver that #includes linux/i2c-sensor.h
has defined for it these parameters:
force_<driver_basename>
probe
ignore
force
but it would be better for someone who is familiar with those
twisted macros to document all of this.
--
~Randy
prev parent reply other threads:[~2004-12-31 5:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 14:03 pcf8591 boot time parameters Karel Kulhavy
2004-12-31 5:21 ` Randy.Dunlap [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=41D4E1C5.3040804@osdl.org \
--to=rddunlap@osdl.org \
--cc=clock@twibright.com \
--cc=linux-kernel@vger.kernel.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