lkml.org 
[lkml]   [2011]   [Apr]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH 07/19] timberdale: mfd_cell is now implicitly available to drivers
    From
    Date
    On Wed, 2011-04-06 at 19:51 +0200, Samuel Ortiz wrote:
    > Hi Ben,
    >
    > On Wed, Apr 06, 2011 at 06:16:49PM +0100, Ben Hutchings wrote:
    > > > So, adding an MFD cell pointer to the device structure allows us to cleanly
    > > > pass both pieces of information, while keeping all the MFD sub drivers
    > > > independant from the MFD core if they want/can.
    > >
    > > Why isn't an MFD the parent of its component devices?
    > It actually is. How would that help here ?

    I was thinking you could encode the component address in the
    platform_device name (just as the bus address is the name of a normal
    bus device). That plus the parent device pointer would be sufficient
    information to look up the mfd_cell.

    Ben.

    --
    Ben Hutchings, Senior Software Engineer, Solarflare
    Not speaking for my employer; that's the marketing department's job.
    They asked us to note that Solarflare product names are trademarked.



    \
     
     \ /
      Last update: 2011-04-06 20:09    [W:4.382 / U:0.028 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site