lkml.org 
[lkml]   [2006]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: what's a platform device?
Date
>>> This makes sense, but you seem to be talking about hierarchy more  
>>> the
>>> functionality. I agree in your description of hierarchy.
>>>
>>> I was looking at it from a functional point of view, maybe more from
>>> the device view then from the bus. I need a struct device type that
>>> contains resources, a name, an id. I'll do matching based on name.
>>> From a functional point of view platform does all this.
>>>
>>> Based on your description would you say that a platform_device's
>>> parent device should always be platform_bus? [I'm getting at the
>>> fact
>>> that we allow pdev->dev.parent to be set by the caller of
>>> platform_device_add].
>>>
>>> Hmm, as I think about this further, I think that its more
>>> coincidence
>>> that the functionality for the "kumar" bus is equivalent to that of
>>> the "platform" bus.
>>>
>>
>> What about a new bus_type that uses all the sematics of the
>> platform_bus.
>> Doing someting like the following which would allow the caller to
>> specify
>> their own bus_type.
>>
>> I'm just trying to avoid duplicating alot of code that already
>> exists in
>> base/platform.c
>
> I'm ok with this patch, Russell?

http://marc.theaimsgroup.com/?l=linux-kernel&m=114072367307531&w=2

Russell, comments?

- kumar
-
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/

\
 
 \ /
  Last update: 2006-02-27 23:28    [W:2.704 / U:0.504 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site