From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Alexander Holler <holler@ahsoftware.de>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
Till Harbaum <till@harbaum.org>
Subject: Re: [PATCH] i2c: i2c-tiny-usb: Add parameter for optional i2c-devices.
Date: Tue, 13 Nov 2012 22:42:51 +0000 [thread overview]
Message-ID: <20121113224251.20b52f34@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1352839940-7559-1-git-send-email-holler@ahsoftware.de>
On Tue, 13 Nov 2012 21:52:20 +0100
Alexander Holler <holler@ahsoftware.de> wrote:
> Make it possible to define i2c-devices at the kernel command line
> or as a module parameter.
>
> Format is devname1@addr1,devname2@addr2,...
Why not do this with your initrd, you can deal with your rtc
before mounting the real root fs.
Alan
next prev parent reply other threads:[~2012-11-13 22:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 18:06 [PATCH 1/2] i2c: Add possibility for user-defined (i2c-)devices for bus-drivers Alexander Holler
2012-11-13 18:06 ` [PATCH 2/2] i2c: i2c-tiny-usb: Add parameter for optional user-defined devices Alexander Holler
2012-11-13 18:55 ` [PATCH 1/2] i2c: Add possibility for user-defined (i2c-)devices for bus-drivers Jean Delvare
2012-11-13 20:23 ` Alexander Holler
2012-11-13 20:52 ` [PATCH] i2c: i2c-tiny-usb: Add parameter for optional i2c-devices Alexander Holler
2012-11-13 22:42 ` Alan Cox [this message]
2012-11-13 23:41 ` Alexander Holler
2012-11-13 21:08 ` [PATCH 1/2] i2c: Add possibility for user-defined (i2c-)devices for bus-drivers Jean Delvare
2012-11-13 21:24 ` Alexander Holler
2012-11-13 21:42 ` Jean Delvare
2012-11-13 23:38 ` Alexander Holler
2012-11-14 9:40 ` Jean Delvare
2012-11-14 12:38 ` Alexander Holler
2012-11-14 19:22 ` till
2012-11-14 23:34 ` Alexander Holler
[not found] ` <1639554.ZUOmHr6Yka@lxtiha>
2012-11-15 11:44 ` Alexander Holler
2012-11-19 13:38 ` Alexander Holler
2012-11-23 14:35 ` Alexander Holler
2012-11-14 2:47 ` Alexander Holler
2012-11-14 9:08 ` Alexander Holler
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=20121113224251.20b52f34@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=holler@ahsoftware.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=till@harbaum.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
all inboxes | Powered by JetHome®