linux-kernel - Re: [PATCH v5 0/7] mfd / platform: cros_ec: move cros

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190201081906.GB783@dell>
Date:   Fri, 1 Feb 2019 08:19:06 +0000
From:   Lee Jones <lee.jones@...aro.org>
To:     Enric Balletbo Serra <eballetbo@...il.com>
Cc:     Enric Balletbo i Serra <enric.balletbo@...labora.com>,
        Gwendal Grignou <gwendal@...omium.org>,
        Nicolas Boichat <drinkcat@...omium.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Guenter Roeck <groeck@...omium.org>, kernel@...labora.com,
        Benson Leung <bleung@...omium.org>
Subject: Re: [PATCH v5 0/7] mfd / platform: cros_ec: move cros_ec sysfs
 attributes to its own drivers.

On Thu, 31 Jan 2019, Enric Balletbo Serra wrote:
> Missatge de Lee Jones <lee.jones@...aro.org> del dia dc., 16 de gen.
> 2019 a les 19:31:
> > On Wed, 12 Dec 2018, Enric Balletbo i Serra wrote:
> > > This is another patchset to try to cleanup a bit more the crossed
> > > references for cros-ec driver between the MFD and the platform/chrome
> > > subsystems.
> > >
> > > The purpose of these patches is get rid of the different cros-ec attributes
> > > from mfd/cros_ec_dev to its own sub-driver in platform/chrome. cros_ec_dev
> > > continues instantiating the sub-devices but the sysfs attributes are owned
> > > by the platform driver.E.g. The lightbar driver should own his sysfs
> > > attributes and be instantiated only if the Embedded Controller has a
> > > lightbar.
> > >
> > > The patchset also adds the documentation of the sysfs attributes.
> > >
> > > Most of the patches touches mfd subsystem and platform/chrome so I'd
> > > suggest go all using and inmutable branch.
> > >
> > > Best regards,
> > >  Enric
> >
> > [...]
> >
> > > Enric Balletbo i Serra (7):
> > >   mfd / platform: cros_ec: use devm_mfd_add_devices
> > >   mfd / platform: cros_ec: move lightbar attributes to its own driver
> > >   mfd / platform: cros_ec: move vbc attributes to its own driver
> > >   mfd / platform: cros_ec: move debugfs attributes to its own driver
> > >   mfd / platform: cros_ec: move device sysfs attributes to its own
> > >     driver
> > >   mfd / platform: cros_ec_vbc: instantiate only if the EC has a VBC
> > >     NVRAM
> > >   platform/chrome: cros_ec_lightbar: instantiate only if the EC has a
> > >     lightbar
> >
> > These patches have been applied to my local MFD tree.  It will be
> > pushed when 5.0-rc3 has been released.  The MFD tree needs rebasing
> > onto it since it contains all of the MFD patches due for v5.0.
> 
> Do you mind to push the patches in your tree, I've some patches that
> depend on these to apply cleanly and I'd like to base my branch on top
> of yours.

Thanks for the reminder.  Will send it 1 min.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog