[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121101135148.382aec00@pyramind.ukuu.org.uk>
Date: Thu, 1 Nov 2012 13:51:48 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Pantelis Antoniou <panto@...oniou-consulting.com>
Cc: <balbi@...com>, "Cousson, Benoit" <b-cousson@...com>,
Tony Lindgren <tony@...mide.com>,
<linux-kernel@...r.kernel.org>,
Koen Kooi <koen@...inion.thruhere.net>,
Matt Porter <mporter@...com>, Russ Dill <Russ.Dill@...com>,
<linux-omap@...r.kernel.org>, Kevin Hilman <khilman@...com>,
Paul Walmsley <paul@...an.com>
Subject: Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2
> What they want, and what every user wants, is I plug this board in, and
> the driver make sure everything is loaded and ready. No, the end users
> don't want to see any of the implementation details of how the bitfile
> is transported; the driver can handle it.
That doesn't necessarily make it a bus merely some kind of hotplug
enumeration of devices. That should all work properly both for devices
and busses with spi and i²c as the final bits needed for it got fixed
some time ago.
In an ideal world you don't want to be writing custom drivers for stuff.
If your cape routes an i²c serial device to the existing system i²c
busses then you want to just create an instance of any existing driver on
the existing i²c bus not create a whole new layer of goop.
It does need to do the plumbing and resource management for the plumbing
but thats not the same as being a bus.
Alan
--
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