Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933987AbcK3KCY (ORCPT ); Wed, 30 Nov 2016 05:02:24 -0500 Received: from mailout1.w1.samsung.com ([210.118.77.11]:48893 "EHLO mailout1.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754482AbcK3J1k (ORCPT ); Wed, 30 Nov 2016 04:27:40 -0500 X-AuditID: cbfec7f5-f79ce6d000004c54-e4-583e9b874507 Subject: Re: [PATCH V3] leds: pca955x: Add ACPI support for pca955x To: Phong Vo Cc: Mika Westerberg , "Rafael J. Wysocki" , Richard Purdie , linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, Loc Ho , Thang Nguyen , patches , Tin Huynh , peda@axentia.se From: Jacek Anaszewski Message-id: Date: Wed, 30 Nov 2016 10:27:34 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-version: 1.0 In-reply-to: <328afec669295cbc3a4338a4347e7067@mail.gmail.com> Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHKsWRmVeSWpSXmKPExsWy7djPc7rts+0iDBY8tbRoudXLYrF8Xz+j xeVdc9gstr5Zx2gxZfsRdovmM9/YLPYems9o0bHmG6PFmdOXWC1273rKanGsM8rid8dkVgce j4/rPzF6TDswm91j3slAjy1X21k89sz/werxeZNcAFsUl01Kak5mWWqRvl0CV8apDxfZC/7p Vlx6fpO5gXGZShcjJ4eEgInEnC+tjBC2mMSFe+vZuhi5OIQEljJKPN97mwXC+cwo8fXhTzaY js8ty9ghEssYJbZ/vsUI4TxjlFg17ysrSJWwgLPE4y/vwWwRASmJphOPwIqYBR4xScz89psd JMEmYCjx88Vrpi5GDg5eATuJrXfkQcIsAqoSV3ZMYAYJiwpESOy+mwoS5hUQlPgx+R4LiM0J VH354Ckwm1nASuLZv1ZWCFteYvOat8wgqyQErrFLdP49AzZeQkBWYtMBZogHXCSOdL1gh7CF JV4d3wJly0h0dhxkguidzChx8dhNVghnNaPExs5OFogqa4mG/7+gNvNJTNo2nRliAa9ER5sQ RImHxJO2e9AwdZQ4t/UaNBinsUh03zvMPoFRfhaSh2YheWIWkicWMDKvYhRJLS3OTU8tNtUr TswtLs1L10vOz93ECExFp/8d/7qDcekxq0OMAhyMSjy8LybYRgixJpYVV+YeYpTgYFYS4d06 yy5CiDclsbIqtSg/vqg0J7X4EKM0B4uSOO+eBVfChQTSE0tSs1NTC1KLYLJMHJxSDYyXp517 vNPdvH8Nj76o4KOj4XaeLxaefPcvZ+n7PXsy96qs+LPao/rhaheleztNAg2NL7jlmSqlVvvo CdbabpriYv7KsMxVq+TH1f2x3e/M7xeuutH/t6XmfoPbCQ2pdCF9pdftu160tddztD5b5nF+ 4eYQhp0cW+4/0M+P/eA1/fKldFHbS6+UWIozEg21mIuKEwH6jfuMQQMAAA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLIsWRmVeSWpSXmKPExsVy+t/xK7ozZttFGOz9qGjRcquXxWL5vn5G i8u75rBZbH2zjtFiyvYj7BbNZ76xWew9NJ/RomPNN0aLM6cvsVrs3vWU1eJYZ5TF747JrA48 Hh/Xf2L0mHZgNrvHvJOBHluutrN47Jn/g9Xj8ya5ALYoN5uM1MSU1CKF1Lzk/JTMvHRbpdAQ N10LJYW8xNxUW6UIXd+QICWFssScUiDPyAANODgHuAcr6dsluGWc+nCRveCfbsWl5zeZGxiX qXQxcnJICJhIfG5Zxg5hi0lcuLeerYuRi0NIYAmjxIWWHUwgCSGBZ4wSM096g9jCAs4Sj7+8 ZwWxRQSkJJpOPGKEaJjBInH94CR2EIdZ4BGTxPq9x8DGsgkYSvx88RpoEgcHr4CdxNY78iBh FgFViSs7JjCD2KICERK3Vn1kBLF5BQQlfky+xwJicwKVXz54CsxmFjCT+PLyMCuELS+xec1b 5gmMArOQtMxCUjYLSdkCRuZVjCKppcW56bnFhnrFibnFpXnpesn5uZsYgVG57djPzTsYL20M PsQowMGoxMM7oc82Qog1say4MvcQowQHs5II7/GZdhFCvCmJlVWpRfnxRaU5qcWHGE2BnpjI LCWanA9MGHkl8YYmhuaWhkbGFhbmRkZK4rwlH66ECwmkJ5akZqemFqQWwfQxcXBKNTD2ze3Z FKoXqv2LTzZ4t0UKr8vv6b+nHNd+s0orUvdsffesP00WlxRXHp8oUfw3WNOd1VlxX9SxsBk9 X42uJ9QeSzt1cdNRye+3ytaL/9TLWJPi/+o8T4eN3YvoF6syunwWnpqkwr1p/Xof1g4N0/aq fR8/efFv6HhQ1F0gV504zevzJ6N3N64rsRRnJBpqMRcVJwIA0wtAW+ACAAA= X-MTR: 20000000000000000@CPGS X-CMS-MailID: 20161130092735eucas1p193f86f2429fdba3ef040725f8a997249 X-Msg-Generator: CA X-Sender-IP: 182.198.249.179 X-Local-Sender: =?UTF-8?B?SmFjZWsgQW5hc3pld3NraRtTUlBPTC1TeXN0ZW0gRlcgIChN?= =?UTF-8?B?Qikb7IK87ISx7KCE7J6QG1NlbmlvciBTb2Z0d2FyZSBFbmdpbmVlcg==?= X-Global-Sender: =?UTF-8?B?SmFjZWsgQW5hc3pld3NraRtTUlBPTC1TeXN0ZW0gRlcgIChN?= =?UTF-8?B?QikbU2Ftc3VuZyBFbGVjdHJvbmljcxtTZW5pb3IgU29mdHdhcmUgRW5naW5l?= =?UTF-8?B?ZXI=?= X-Sender-Code: =?UTF-8?B?QzEwG0VIURtDMTBDRDAyQ0QwMjc1MjY=?= CMS-TYPE: 201P X-HopCount: 7 X-CMS-RootMailID: 20161130030845epcas5p2369d1c7cabb765ef0039b8e8d5aaa965 X-RootMTR: 20161130030845epcas5p2369d1c7cabb765ef0039b8e8d5aaa965 References: <1480475311-14385-1-git-send-email-tnhuynh@apm.com> <302ebc57-6f52-b0ff-e354-0c67556a88ed@samsung.com> <7efcf021-72c9-328a-ad88-4c226e8b5d6d@samsung.com> <10443ff4-67ff-d474-401f-21fa7f33a9a5@samsung.com> <328afec669295cbc3a4338a4347e7067@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5716 Lines: 168 On 11/30/2016 10:10 AM, Phong Vo wrote: > +-----Original Message----- > +From: Jacek Anaszewski [mailto:j.anaszewski@samsung.com] > +Sent: Wednesday, November 30, 2016 4:00 PM > +To: Phong Vo > +Cc: Mika Westerberg; Rafael J. Wysocki; Richard Purdie; linux- > +leds@vger.kernel.org; linux-kernel@vger.kernel.org; linux- > +acpi@vger.kernel.org; Loc Ho; Thang Nguyen; patches; Tin Huynh > +Subject: Re: [PATCH V3] leds: pca955x: Add ACPI support for pca955x > + > +Hi Phong, > + > +On 11/30/2016 09:23 AM, Phong Vo wrote: > +> +-----Original Message----- > +> +From: Jacek Anaszewski [mailto:j.anaszewski@samsung.com] > +> +Sent: Wednesday, November 30, 2016 3:18 PM > +> +To: Tin Huynh > +> +Cc: Mika Westerberg; Rafael J. Wysocki; Richard Purdie; linux- > +> +leds@vger.kernel.org; linux-kernel@vger.kernel.org; linux- > +> +acpi@vger.kernel.org; Loc Ho; Thang Nguyen; Phong Vo; patches > +> +Subject: Re: [PATCH V3] leds: pca955x: Add ACPI support for pca955x > +> + > +> +On 11/30/2016 09:06 AM, Tin Huynh wrote: > +> +> On Wed, Nov 30, 2016 at 3:01 PM, Jacek Anaszewski > +> +> wrote: > +> +>> > +> +>> On 11/30/2016 08:51 AM, Jacek Anaszewski wrote: > +> +>>> > +> +>>> Hi Tin, > +> +>>> > +> +>>> How this patch is different from the one already merged? > +> +>>> > +> +>>> Best regards, > +> +>>> Jacek Anaszewski > +> +>>> > +> > +> Hi Jacek, I am answering on behalf of Tin. > +> This patch is for the leds:pca955x driver while the previous one was > +> for leds:pca963x driver! > +> They are almost the same in the coding construct, but different > +drivers. > + > +Ah, indeed, that's why I got lost with patch version numbering :-) > + > +> +>>> On 11/30/2016 04:08 AM, Tin Huynh wrote: > +> +>>>> > +> +>>>> This patch enables ACPI support for leds-pca955x driver. > +> +>>>> > +> +>>>> Signed-off-by: Tin Huynh > +> +>>>> --- > +> +>>>> drivers/leds/leds-pca955x.c | 22 +++++++++++++++++++++- > +> +>>>> 1 files changed, 21 insertions(+), 1 deletions(-) > +> +>>>> > +> +>>>> Change from V2: > +> +>>>> -Correct coding conventions. > +> +>>>> > +> +>>>> Change from V1: > +> +>>>> -Remove CONFIG_ACPI. > +> +>>>> > +> +>>>> diff --git a/drivers/leds/leds-pca955x.c > +> +>>>> b/drivers/leds/leds-pca955x.c index 840401a..b168ebe 100644 > +> +>>>> --- a/drivers/leds/leds-pca955x.c > +> +>>>> +++ b/drivers/leds/leds-pca955x.c > +> +>>>> @@ -40,6 +40,7 @@ > +> +>>>> * bits the chip supports. > +> +>>>> */ > +> +>>>> > +> +>>>> +#include > +> +>>>> #include > +> +>>>> #include > +> +>>>> #include > +> +>>>> @@ -100,6 +101,15 @@ struct pca955x_chipdef { }; > +> +>>>> MODULE_DEVICE_TABLE(i2c, pca955x_id); > +> +>>>> > +> +>>>> +static const struct acpi_device_id pca955x_acpi_ids[] = { > +> +>>>> + { .id = "PCA9550", .driver_data = pca9550 }, > +> +>>>> + { .id = "PCA9551", .driver_data = pca9551 }, > +> +>>>> + { .id = "PCA9552", .driver_data = pca9552 }, > +> +>>>> + { .id = "PCA9553", .driver_data = pca9553 }, > +> +>>>> + { } > +> +>> > +> +>> > +> +>> OK, I see that you brought back explicit properties in the > +> +>> structure initializer. Is there some vital reason for that? > +> > +> It's not vital, but to make it consistent with what was done for > +> pca963x, > + > +For pca963x I applied the version without explicit properties. > +Note that this is consistent with pca963x_id array above the added > +pca963x_acpi_ids. For pca955x the situation is the same. > + > +> and also per suggestion by Mika on reviewing a different driver > +> mux:954x in another thread. > + > +Could you give a reference to that thread? In the review of V1 of this > +patch Mika mentioned "{ "PCA9553", pca9553 }" scheme. > + > > Actually it was Peter Rosin (not Mika) on linux-i2c and the reference to > that is follows > > https://lkml.org/lkml/2016/11/18/732 > > I am including Robin here. > > Thanks. Thanks for the link. I prefer to stick to the style of the surrounding code, so let's drop ".id =" and ".driver_data =" from the initializers. Best regards, Jacek Anaszewski > +> I would think this would make the definition clearer. > +> > +> +>> You're mentioning "correcting coding conventions" in the patch > +> +>> changelog. checkpatch.pl --strict doesn't complain about that, so > +> +>> what coding conventions you have on mind? > +> +> > +> +> > +> +>> > +> +>> > +> +>>>> +MODULE_DEVICE_TABLE(acpi, pca955x_acpi_ids); > +> +>>>> + > +> +>>>> struct pca955x { > +> +>>>> struct mutex lock; > +> +>>>> struct pca955x_led *leds; > +> +>>>> @@ -250,7 +260,16 @@ static int pca955x_probe(struct i2c_client > +> +*client, > +> +>>>> struct led_platform_data *pdata; > +> +>>>> int i, err; > +> +>>>> > +> +>>>> - chip = &pca955x_chipdefs[id->driver_data]; > +> +>>>> + if (id) { > +> +>>>> + chip = &pca955x_chipdefs[id->driver_data]; > +> +>>>> + } else { > +> +>>>> + const struct acpi_device_id *acpi_id; > +> +> > +> +> I added '{}' follow if > +> + > +> +You had it already in V1. Please verify if the patch applied to the > +> +for- next branch of linux-leds.git has the shape you intended: > +> + > +> +https://git.kernel.org/cgit/linux/kernel/git/j.anaszewski/linux- > +> +leds.git/commit/?h=for-next&id=e46895b71a26da404c4d95cb2bab1a67cf8b20 > +> +bc > +> + > +> +-- > +> +Best regards, > +> +Jacek Anaszewski > +> -- > +> To unsubscribe from this list: send the line "unsubscribe linux-leds" > +> in the body of a message to majordomo@vger.kernel.org More majordomo > +> info at http://vger.kernel.org/majordomo-info.html > +> > +> > +> > + > + > +-- > +Best regards, > +Jacek Anaszewski > > >