From: Mark Brown <broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
To: Jonathan Cameron <jic23-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
eric miao <eric.y.miao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Subject: Re: RFC: Working around dynamic device allocation in i2c. Interaction with other subystems.
Date: Mon, 19 Jan 2009 19:37:05 +0000 [thread overview]
Message-ID: <20090119193704.GA16803@sirena.org.uk> (raw)
In-Reply-To: <4974D20F.20209-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org>
On Mon, Jan 19, 2009 at 07:18:39PM +0000, Jonathan Cameron wrote:
> 1) Relax the constraints that the token used for device identification
> in subsystems using the regulators approach to a void * and use
> the platform data pointer of an i2c device. Note this requires
> every device which may need a regulator to have platform data.
> Whilst this would work, it is far from ideal.
This would also remove the ability of the APIs using this to use the
struct device for other things like showing what they're doing in sysfs
or use dev_printk.
next prev parent reply other threads:[~2009-01-19 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 19:18 RFC: Working around dynamic device allocation in i2c. Interaction with other subystems Jonathan Cameron
[not found] ` <4974D20F.20209-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org>
2009-01-19 19:37 ` Mark Brown [this message]
2009-01-22 12:55 ` Jonathan Cameron
[not found] ` <49786CA6.8010303-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org>
2009-01-23 6:14 ` David Brownell
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=20090119193704.GA16803@sirena.org.uk \
--to=broonie-gfdadszt00ze9xe1eozjha@public.gmane.org \
--cc=eric.y.miao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jic23-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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