From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Pavel Machek <pavel@ucw.cz>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Richard Purdie <rpurdie@rpsys.net>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Fenglin Wu <fenglinw@codeaurora.org>
Subject: Re: [PATCH v3 2/3] leds: Add driver for Qualcomm LPG
Date: Tue, 21 Nov 2017 23:01:40 +0100 [thread overview]
Message-ID: <d291deae-d962-5ca1-2c84-721b90bd0bce@gmail.com> (raw)
In-Reply-To: <20171120232211.GC13906@amd>
On 11/21/2017 12:22 AM, Pavel Machek wrote:
> On Mon 2017-11-20 13:10:33, Bjorn Andersson wrote:
>> On Sun 19 Nov 13:36 PST 2017, Jacek Anaszewski wrote:
>>
>>> Hi Bjorn,
>>>
>>> Thanks for the patch. Please refer to my comments in the code.
>>>
>>> On 11/15/2017 08:13 AM, Bjorn Andersson wrote:
>> [..]
>>>> diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
>>>> index 52ea34e337cd..ccc3aa4b2474 100644
>>>> --- a/drivers/leds/Kconfig
>>>> +++ b/drivers/leds/Kconfig
>>>> @@ -651,6 +651,13 @@ config LEDS_POWERNV
>>>> To compile this driver as a module, choose 'm' here: the module
>>>> will be called leds-powernv.
>>>>
>>>> +config LEDS_QCOM_LPG
>>>> + tristate "LED support for Qualcomm LPG"
>>>> + depends on LEDS_CLASS
>>>
>>> You were mentioning that this driver is for a MFD child block,
>>> so we should probably depend on the parent MFD driver?
>>>
>>
>> There's no build time dependency between the two, so it's not strictly
>> necessary.
>>
>> Adding a dependency on MFD_SPMI_PMIC would indirectly add a dependency
>> on ARCH_QCOM, which limit build testing and stop some static code
>> checkers to check the driver.
>>
>> So, unless you strongly object I would prefer not to mention the
>> MFD.
>
> OTOH, this way even users that can't have qualcom LPG are asked the
> question.
>
> So right way is depends on LEdS_CLASS && (BUILD_TEST || MFD_SPMI_PMIC).
Ack.
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2017-11-21 22:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 7:13 [PATCH v3 0/3] Qualcomm Light Pulse Generator Bjorn Andersson
2017-11-15 7:13 ` [PATCH v3 1/3] leds: core: Introduce generic pattern interface Bjorn Andersson
2017-11-15 7:36 ` Greg KH
2017-11-20 23:20 ` Pavel Machek
2017-11-21 0:21 ` Bjorn Andersson
2017-12-08 14:27 ` Pavel Machek
2017-11-21 20:33 ` Jacek Anaszewski
2017-11-15 7:13 ` [PATCH v3 2/3] leds: Add driver for Qualcomm LPG Bjorn Andersson
2017-11-19 21:36 ` Jacek Anaszewski
2017-11-20 21:10 ` Bjorn Andersson
2017-11-20 23:22 ` Pavel Machek
2017-11-21 22:01 ` Jacek Anaszewski [this message]
2017-11-21 22:00 ` Jacek Anaszewski
2017-11-15 7:13 ` [PATCH v3 3/3] DT: leds: Add Qualcomm Light Pulse Generator binding Bjorn Andersson
2017-11-16 5:09 ` Rob Herring
2017-11-19 21:35 ` Jacek Anaszewski
2017-11-20 19:58 ` Bjorn Andersson
2017-11-20 20:35 ` Jacek Anaszewski
2017-11-20 21:45 ` Bjorn Andersson
2017-11-22 20:42 ` Jacek Anaszewski
2017-12-18 20:49 ` Bjorn Andersson
2017-12-19 21:30 ` Jacek Anaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d291deae-d962-5ca1-2c84-721b90bd0bce@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fenglinw@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome