From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, wahrenst@gmx.net,
"open list:PWM SUBSYSTEM" <linux-pwm@vger.kernel.org>
Subject: Re: [PATCH] pwm: bcm2835: Allow building for ARCH_BRCMSTB
Date: Mon, 30 Dec 2019 11:33:04 -0800 [thread overview]
Message-ID: <73451521-a4d3-d945-2c86-cceef4cc6781@broadcom.com> (raw)
In-Reply-To: <20191210065229.hopmnq5qlwtl7gzw@pengutronix.de>
On 12/9/19 10:52 PM, Uwe Kleine-König wrote:
> On Mon, Dec 09, 2019 at 03:25:03PM -0800, Florian Fainelli wrote:
>> BCM7211 is supported using ARCH_BRCMSTB and uses this PWM controller
>> driver, make it possible to build it.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> drivers/pwm/Kconfig | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig
>> index bd21655c37a6..0bb8a40c8d6c 100644
>> --- a/drivers/pwm/Kconfig
>> +++ b/drivers/pwm/Kconfig
>> @@ -100,7 +100,7 @@ config PWM_BCM_KONA
>>
>> config PWM_BCM2835
>> tristate "BCM2835 PWM support"
>> - depends on ARCH_BCM2835
>> + depends on ARCH_BCM2835 || ARCH_BRCMSTB
>
> It would be nice to allow this driver to be compiled with COMPILE_TEST,
> too. But also without this:
>
> Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Krysztof just submitted a patch doing that [1], which will conflict with
this one. Thierry would you be able to resolve that conflict while applying?
[1]:
https://lore.kernel.org/linux-arm-kernel/20191230172113.17222-2-krzk@kernel.org/
--
Florian
prev parent reply other threads:[~2019-12-30 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 23:25 Florian Fainelli
2019-12-10 6:52 ` Uwe Kleine-König
2019-12-30 19:33 ` Florian Fainelli [this message]
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=73451521-a4d3-d945-2c86-cceef4cc6781@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wahrenst@gmx.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
all inboxes | Powered by JetHome®