From: Pantelis Antoniou <panto@antoniou-consulting.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: <balbi@ti.com>, "Cousson, Benoit" <b-cousson@ti.com>,
Tony Lindgren <tony@atomide.com>, <linux-kernel@vger.kernel.org>,
Koen Kooi <koen@dominion.thruhere.net>,
Matt Porter <mporter@ti.com>, Russ Dill <Russ.Dill@ti.com>,
<linux-omap@vger.kernel.org>, Kevin Hilman <khilman@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2
Date: Thu, 1 Nov 2012 15:59:50 +0200 [thread overview]
Message-ID: <9F25E89E-9194-4725-8A8C-053DCBADA1DB@antoniou-consulting.com> (raw)
In-Reply-To: <20121101135148.382aec00@pyramind.ukuu.org.uk>
Hi Alan,
On Nov 1, 2012, at 3:51 PM, Alan Cox wrote:
>> 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
Fair enough. But there's no such thing a 'hotplug enumeration construct' in Linux
yet, and a bus is the closest thing to it. It does take advantage of the nice
way device code matches drivers and devices though.
I'm afraid that having the I2C/SPI drivers doing the detection won't work.
The capes can have arbitrary I2C/SPI devices (and even more weird components).
There is no way to assure for example that the I2C device responding to address 'foo'
in cape A is the same I2C device responding to the same address in cape B.
In a nutshell, no, I'm not writing any custom drivers for the stuff that exists
already. There is no extra layer after the device is created and operates as it was
located in the proper place in the DTS.
The custom drivers are only needed for complex capes where you can't
have the device simply work by creating the devices.
Regards
-- Pantelis
WARNING: multiple messages have this Message-ID (diff)
From: Pantelis Antoniou <panto@antoniou-consulting.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: balbi@ti.com, "Cousson, Benoit" <b-cousson@ti.com>,
Tony Lindgren <tony@atomide.com>,
linux-kernel@vger.kernel.org,
Koen Kooi <koen@dominion.thruhere.net>,
Matt Porter <mporter@ti.com>, Russ Dill <Russ.Dill@ti.com>,
linux-omap@vger.kernel.org, Kevin Hilman <khilman@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2
Date: Thu, 1 Nov 2012 15:59:50 +0200 [thread overview]
Message-ID: <9F25E89E-9194-4725-8A8C-053DCBADA1DB@antoniou-consulting.com> (raw)
In-Reply-To: <20121101135148.382aec00@pyramind.ukuu.org.uk>
Hi Alan,
On Nov 1, 2012, at 3:51 PM, Alan Cox wrote:
>> 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
Fair enough. But there's no such thing a 'hotplug enumeration construct' in Linux
yet, and a bus is the closest thing to it. It does take advantage of the nice
way device code matches drivers and devices though.
I'm afraid that having the I2C/SPI drivers doing the detection won't work.
The capes can have arbitrary I2C/SPI devices (and even more weird components).
There is no way to assure for example that the I2C device responding to address 'foo'
in cape A is the same I2C device responding to the same address in cape B.
In a nutshell, no, I'm not writing any custom drivers for the stuff that exists
already. There is no extra layer after the device is created and operates as it was
located in the proper place in the DTS.
The custom drivers are only needed for complex capes where you can't
have the device simply work by creating the devices.
Regards
-- Pantelis
next prev parent reply other threads:[~2012-11-01 13:59 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 15:17 [PATCH 0/3] capebus moving omap_devices to mach-omap2 Pantelis Antoniou
2012-10-31 17:52 ` Tony Lindgren
2012-10-31 18:04 ` Pantelis Antoniou
2012-10-31 18:09 ` Tony Lindgren
2012-10-31 18:24 ` Pantelis Antoniou
2012-10-31 19:55 ` Benoit Cousson
2012-10-31 19:55 ` Benoit Cousson
2012-10-31 20:12 ` Pantelis Antoniou
2012-10-31 20:12 ` Pantelis Antoniou
2012-10-31 21:26 ` Tony Lindgren
2012-10-31 21:36 ` Pantelis Antoniou
2012-10-31 21:43 ` Tony Lindgren
2012-10-31 22:00 ` Pantelis Antoniou
2012-10-31 22:16 ` Tony Lindgren
2012-10-31 22:14 ` Felipe Balbi
2012-10-31 22:14 ` Felipe Balbi
2012-11-01 7:02 ` Pantelis Antoniou
2012-11-01 7:02 ` Pantelis Antoniou
2012-11-01 10:23 ` Cousson, Benoit
2012-11-01 10:23 ` Cousson, Benoit
2012-11-01 10:39 ` Pantelis Antoniou
2012-11-01 10:39 ` Pantelis Antoniou
2012-11-01 11:04 ` Felipe Balbi
2012-11-01 11:04 ` Felipe Balbi
2012-11-01 11:26 ` Pantelis Antoniou
2012-11-01 11:26 ` Pantelis Antoniou
2012-11-01 12:40 ` Felipe Balbi
2012-11-01 12:40 ` Felipe Balbi
2012-11-01 12:57 ` Pantelis Antoniou
2012-11-01 12:57 ` Pantelis Antoniou
2012-11-01 13:16 ` Felipe Balbi
2012-11-01 13:16 ` Felipe Balbi
2012-11-01 13:35 ` Pantelis Antoniou
2012-11-01 13:35 ` Pantelis Antoniou
2012-11-01 13:51 ` Alan Cox
2012-11-01 13:51 ` Alan Cox
2012-11-01 13:59 ` Pantelis Antoniou [this message]
2012-11-01 13:59 ` Pantelis Antoniou
2012-11-01 22:05 ` Felipe Balbi
2012-11-01 22:05 ` Felipe Balbi
2012-11-01 23:49 ` Russ Dill
2012-11-02 8:57 ` Felipe Balbi
2012-11-02 8:57 ` Felipe Balbi
2012-11-02 9:42 ` Russ Dill
2012-11-02 10:39 ` Koen Kooi
2012-11-02 10:39 ` Koen Kooi
2012-11-02 11:00 ` Felipe Balbi
2012-11-02 11:00 ` Felipe Balbi
2012-11-02 16:44 ` Russ Dill
2012-11-02 11:21 ` Alan Cox
2012-11-02 12:32 ` Pantelis Antoniou
2012-11-05 0:37 ` Grant Likely
2012-11-05 15:37 ` Pantelis Antoniou
2012-11-05 15:37 ` Pantelis Antoniou
2012-11-05 19:10 ` Grant Likely
2012-11-05 19:54 ` Pantelis Antoniou
2012-11-05 19:54 ` Pantelis Antoniou
2012-11-05 20:14 ` Grant Likely
2012-11-05 22:59 ` Joel A Fernandes
2012-11-05 23:58 ` Grant Likely
2012-11-05 23:58 ` Grant Likely
2012-11-06 3:06 ` Joel A Fernandes
2012-11-06 8:14 ` Pantelis Antoniou
2012-11-06 8:14 ` Pantelis Antoniou
2012-11-06 11:16 ` Grant Likely
2012-11-06 13:54 ` Pantelis Antoniou
2012-11-06 13:54 ` Pantelis Antoniou
2012-11-02 16:07 ` Jason Kridner
2012-11-02 16:07 ` Jason Kridner
2012-11-02 16:28 ` Alan Cox
2012-11-05 1:05 ` Grant Likely
2012-11-01 11:26 ` Cousson, Benoit
2012-11-01 11:26 ` Cousson, Benoit
2012-11-01 11:39 ` Pantelis Antoniou
2012-11-01 11:39 ` Pantelis Antoniou
2012-11-01 12:00 ` Koen Kooi
2012-11-01 12:00 ` Koen Kooi
2012-11-01 13:06 ` Felipe Balbi
2012-11-01 13:06 ` Felipe Balbi
2012-11-01 13:33 ` Koen Kooi
2012-11-01 13:33 ` Koen Kooi
2012-11-02 8:15 ` Cousson, Benoit
2012-11-02 8:15 ` Cousson, Benoit
2012-11-02 8:43 ` Pantelis Antoniou
2012-11-03 8:23 ` Kevin Hilman
2012-11-05 0:22 ` Grant Likely
2012-11-05 0:22 ` Grant Likely
2012-11-05 13:25 ` Pantelis Antoniou
2012-11-05 13:25 ` Pantelis Antoniou
2012-11-05 14:34 ` Grant Likely
2012-11-05 15:34 ` Tony Lindgren
2012-11-05 15:34 ` Tony Lindgren
2012-11-05 15:56 ` Rob Herring
2012-11-05 15:56 ` Rob Herring
2012-11-05 19:40 ` Grant Likely
2012-11-01 15:18 ` [PATCH 1/3] omap-device: Remove __init from omap_device_build family functions Pantelis Antoniou
2012-11-01 15:18 ` [PATCH 2/3] da8xx-dt: Create da8xx DT adapter device Pantelis Antoniou
2012-11-01 14:36 ` Tomi Valkeinen
2012-11-01 14:38 ` Pantelis Antoniou
2012-11-01 15:18 ` [PATCH 3/3] ti-tscadc-dt: Create ti-tscadc-dt " Pantelis Antoniou
2012-11-01 18:50 [PATCH 0/3] capebus moving omap_devices to mach-omap2 Jason Kridner
2012-11-01 19:07 ` Tony Lindgren
2012-11-02 9:26 ` Cousson, Benoit
2012-11-02 9:26 ` Cousson, Benoit
2012-11-02 10:19 ` Koen Kooi
2012-11-02 10:19 ` Koen Kooi
2012-11-05 0:32 ` Grant Likely
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=9F25E89E-9194-4725-8A8C-053DCBADA1DB@antoniou-consulting.com \
--to=panto@antoniou-consulting.com \
--cc=Russ.Dill@ti.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=khilman@ti.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mporter@ti.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.