linux-kernel - Re: [PATCH] Fix platform data in leds-pca955x.c

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]

Date:   Wed, 4 Jul 2018 20:04:30 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Rob Landley <rob@...dley.net>
Cc:     clg@...d.org, Jacek Anaszewski <jacek.anaszewski@...il.com>,
        Pavel Machek <pavel@....cz>, Andrew Jeffery <andrew@...id.au>,
        Linux LED Subsystem <linux-leds@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Fix platform data in leds-pca955x.c

On Wed, Jul 4, 2018 at 8:00 PM, Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Wed, Jul 4, 2018 at 3:46 AM, Rob Landley <rob@...dley.net> wrote:

> For now, you can switch to unified device properties API (basically
> un-ifdef pca955x_pdata_of_init() and replacing of_* by device_* or
> fwnode_* compatible calls) and providing a static table of built-in
> device properties in the platform code in question.
> (see include/linux/property.h, for example users of
> PROPERTY_ENTRY_U*() macros, like arch/arm/mach-pxa/raumfeld.c)

Taking into consideration that device is enumerated by i2c core, which
is being aware of device properties (1), better example might be
drivers/platform/x86/intel_cht_int33fe.c

(1)
commit d3e1b617ae20c459627f501b4bc55b1ea91f662b
Author: Dmitry Torokhov <dmitry.torokhov@...il.com>
Date:   Thu Feb 2 17:41:28 2017 -0800

   i2c: allow specify device properties in i2c_board_info

-- 
With Best Regards,
Andy Shevchenko