lkml.org 
[lkml]   [2009]   [May]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC] [PATCH] Device Tree on ARM platform
    On Wed, May 27, 2009 at 02:54:10PM -0600, Grant Likely wrote:
    > On Wed, May 27, 2009 at 2:19 PM, Jean-Christophe PLAGNIOL-VILLARD
    > <plagnioj@jcrosoft.com> wrote:
    > >> One option that has been suggested (more than once) is to make the
    > >> adapter code an of_platform_driver which translates the device tree
    > >> data and then registers the appropriate platform_devices.  This neatly
    > >> solves the problem, but I don't like the overhead involved in
    > >> registering 2 struct devices with the kernel for every device node in
    > >> the device tree.
    > > but simplify the dev and maintaining is also an important goal.
    > >
    > > Have to duplicated ressource handling via ifdef in every drivers is also an
    > > overhead which need to be avoided
    >
    > agreed. I don't have a best of both worlds answer here.

    I do. As intimated other places in this thread, I think the right
    approach is to register constructor functions that will be used during
    boot to traverse the OF devtree and instantiate platform devices (or
    other device types in some cases, e.g. i2c). The driver will then
    bind to the platform device this created.

    --
    David Gibson | I'll have my music baroque, and my code
    david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
    | _way_ _around_!
    http://www.ozlabs.org/~dgibson
    --
    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: 2009-05-28 05:09    [W:0.024 / U:63.120 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site