public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Uli Luckas <u.luckas-vFjI0mZ6VZs@public.gmane.org>
To: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: Grouping i2c bus drivers
Date: Mon, 30 Jun 2008 16:04:14 +0200	[thread overview]
Message-ID: <200806301604.15083.u.luckas@road.de> (raw)
In-Reply-To: <20080630145532.5a8452b5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>

On Monday, 30. June 2008, Jean Delvare wrote:
> On Mon, 30 Jun 2008 14:06:31 +0300, Riku Voipio wrote:
> > Jean Delvare wrote:
> >  > obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o
> >
> > I'm not sure if one would classify pa semi dualcore 2GHz systems
> > as "embedded", but this i2c controller is embedded into the
> > PA SEMI cpu..
>
> By "embedded", I had "embedded systems" in mind, not whether the I2C
> controller was part of the CPU. So it's down to: what systems are using
> the PA Semi hardware.
>
I think neither notion of 'embedded' really does the right seperation for the 
link order problem.
The actual question is: "do we need the bus for early system initialization". 
Therfore we should maybe call this group of drivers "I2C system bus drivers".

Uli


-- 

------- ROAD ...the handyPC Company - - -  ) ) )

Uli Luckas
Software Development

ROAD GmbH
Bennigsenstr. 14 | 12159 Berlin | Germany
fon: +49 (30) 230069 - 64 | fax: +49 (30) 230069 - 69
url: www.road.de

Amtsgericht Charlottenburg: HRB 96688 B
Managing directors: Hans-Peter Constien, Hubertus von Streit

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

  parent reply	other threads:[~2008-06-30 14:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 12:52 Grouping i2c bus drivers Jean Delvare
     [not found] ` <20080627145236.2a20aaad-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-27 13:44   ` Wolfram Sang
     [not found]     ` <20080627134436.GC3931-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-06-28  8:58       ` Jean Delvare
     [not found]         ` <20080628105850.2c56f1a2-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-30  9:01           ` Peter Korsgaard
     [not found]             ` <87d4lzjnzl.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>
2008-06-30 12:45               ` Jean Delvare
2008-06-30  9:56   ` Mike Rapoport
     [not found]     ` <4868ADCD.3080305-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2008-07-02 14:42       ` Jean Delvare
     [not found]         ` <20080702164207.76304a01-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-07-02 18:09           ` Uli Luckas
2008-06-30 11:06   ` Riku Voipio
     [not found]     ` <4868BE37.1090405-WgUW+8SLYMv1KXRcyAk9cg@public.gmane.org>
2008-06-30 12:55       ` Jean Delvare
     [not found]         ` <20080630145532.5a8452b5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-30 14:04           ` Uli Luckas [this message]
2008-06-30 20:27           ` Ryan Mallon
2008-06-30 11:46   ` Stefan Roese
     [not found]     ` <200806301346.53185.sr-ynQEQJNshbs@public.gmane.org>
2008-06-30 12:49       ` Jean Delvare
2008-06-30 15:29   ` Mark Brown

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=200806301604.15083.u.luckas@road.de \
    --to=u.luckas-vfji0mz6vzs@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@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