lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200806101146.11915.u.luckas@road.de>
Date:	Tue, 10 Jun 2008 11:46:11 +0200
From:	Uli Luckas <u.luckas@...d.de>
To:	Ryan Mallon <ryan@...ewatersys.com>
Cc:	Jean Delvare <khali@...ux-fr.org>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	i2c@...sensors.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH, RFC] Earlier I2C initialization

OT: David Brownell, I get bounces from your mail server refering me to a site 
that is down:
http://worldnet.att.net/general-info/bls_info/block_inquiry.html

On Tuesday, 10. June 2008, Ryan Mallon wrote:
> Jean Delvare wrote:
> > On Tue, 10 Jun 2008 09:27:34 +1200, Ryan Mallon wrote:
> >> David Brownell wrote:
> >>> On Monday 09 June 2008, Ryan Mallon wrote:
> >>>> We have made i2c the first driver subsystem to come up in our 2.6.20
> >>>> kernel since we use i2c io expanders for power domain control. All we
> >>>> did was change drivers/Makefile so that obj-$(CONFIG_I2C) += i2c/ is
> >>>> at the very top of the file. We didn't have any problems with doing
> >>>> this. YMMV of course.
> >
> > Why don't you simply initialize the drivers in question with
> > subsys_initcall()? That's what i2c-pnx, i2c-omap, i2c-davinci and
> > tps65010 are doing at the moment.
>
> How does this work for embedded devices where the same architecture is
> used in many different configurations? For example, we have a PXA270
> setup where we need i2c early, but many other PXA setups do not, so
> making i2c-pxa subsys_initcall to support a single board is maybe the
> wrong way to go?
>
Why would an architecture not want i2c to be available early? The only reason 
would be dependencies of the bus driver. These are constant over all pxa 
platforms though. So most likely the platforms that don't _need_ early i2c 
just don't care.

-- 

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ