lkml.org 
[lkml]   [2022]   [Sep]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] ARM: dts: turris-omnia: Add mcu node
    > > I'm also not sure what the DT people will say about the node name mcu.
    > > I don't see any examples of that in the binding documentation. They
    > > might request you rename it to gpio-controller, unless it does more
    > > than GPIO? And if it does do more than GPIO we are then into mfd
    > > territory, and the binding then becomes much more interesting. Then we
    > > start the questions, are you defining a ABI now, before there is even
    > > a driver for it?
    > >
    > > Andrew
    >
    > Yes, there is already driver. See my previous email, I mentioned it and
    > also I wrote link for this driver. Moreover now driver is merged in
    > upstream u-boot.

    I'm not comfortable accepting a DT binding for a driver which does not
    exist in Linux. As i said, there are interesting ABI issues here, and
    it could be the MFD, GPIO or reset Maintainers don't accept a binding
    until a Linux driver exists.

    At minimum, you need an Acked-by from the GPIO Maintainer, of the
    binding before this DT change is merged via MVEBU.

    Andrew

    \
     
     \ /
      Last update: 2022-09-04 03:05    [W:5.509 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site