DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=pacbell.net;
  h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id;
  b=FsmhxPdWbB6MYdtZe3KdLQTgfzXK3F7mvz+oCSRNXztqY7FoRLj6VhI6NlPMuMnLxznyWJfwPJxrLVoU/RoZ2hZ3UdvBeOUraPimXCDltlMHKmc/MvwZpHNtFtfD/7JBLUX4c6y2BtvhHN2Bex82G2dFaqhkYNaeJcMmsluexNE=  ;
From: David Brownell <david-b@pacbell.net>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH, RFC] Earlier I2C initialization
Date: Thu, 12 Jun 2008 13:21:03 -0700
User-Agent: KMail/1.9.9
Cc: Jean Delvare <khali@linux-fr.org>, Ryan Mallon <ryan@bluewatersys.com>,
       Uli Luckas <u.luckas@road.de>,
       Russell King - ARM Linux <linux@arm.linux.org.uk>, i2c@lm-sensors.org,
       linux-kernel@vger.kernel.org
References: <200806091541.43899.u.luckas@road.de> <20080611225416.169574a0@hyperion.delvare> <Pine.LNX.4.55.0806112226060.14077@cliff.in.clinika.pl>
In-Reply-To: <Pine.LNX.4.55.0806112226060.14077@cliff.in.clinika.pl>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Message-Id: <200806121321.03429.david-b@pacbell.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1722
Lines: 42

On Wednesday 11 June 2008, Maciej W. Rozycki wrote:
> > That being said, I'm not sure if the comparison with the PCI subsystem
> > holds... I am under the impression that PCI bus handling doesn't
> > require dedicated drivers? At least I can't see any under drivers/pci.
> 
> ?Of course it does require them. ?It is just due to their very nature they
> tend to be placed under arch/,

PCI root hubs, yes.  The drivers/pci/hotplug bridges are slightly
more generic, ditto drivers/pci/pcie and the CardBus bridges in
drivers/pcmcia.  At one point, lack of a generic (non-hotplug) PCI
bridge driver was viewed as a weakness of that driver stack.

Also, drivers/acpi/pci_root.c binds the root at subsys_initcall.
That's done *after* some earlier PCI magic; I never bothered
to sort through that little maze.


> although there are some cases where the 
> same system controller can be used for a range of processors (e.g. some
> Marvell chips can be used either with MIPS or PowerPC CPUs) and they might
> be arguably put in a place more suitable for sharing between
> architectures. ?See arch/mips/pci/ for an example of a generous bunch of
> PCI host drivers.

Which, for the record, get very early initialization using two
different mechanisms:

  - many use arch_initcall()

  - the "arch" subtree is linked before the "drivers" subtree

I don't think I2C needs to worry about arch_initcall just now,
but if necessary it could initialize earlier than subsys_initcall.

- Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/