From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Conor Dooley <conor@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Jassi Brar <jassisinghbrar@gmail.com>,
Bjorn Andersson <quic_bjorande@quicinc.com>,
Maximilian Luz <luzmaximilian@gmail.com>,
Ard Biesheuvel <ardb@kernel.org>,
Johan Hovold <johan+linaro@kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Conor Dooley <conor.dooley@microchip.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
"open list:COMMON CLK FRAMEWORK" <linux-clk@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Stefan Wahren <wahrenst@gmx.net>
Subject: Re: [PATCH 1/3] mailbox: Make BCM2835_MBOX default to ARCH_BCM2835
Date: Tue, 14 May 2024 09:20:06 -0700 [thread overview]
Message-ID: <b422f395-7554-4596-b779-268718b34383@broadcom.com> (raw)
In-Reply-To: <20240514-amiable-unequal-d4133956c80c@spud>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
On 5/14/24 05:29, Conor Dooley wrote:
> On Mon, May 13, 2024 at 04:52:32PM -0700, Florian Fainelli wrote:
>> This driver is depended on by CONFIG_FIRMWARE_RASPBERRYPI which provides
>> a number of essential services, including but not limited to a Linux
>> common clock framework provider. Make sure that enable
>> CONFIG_ARCH_BCM2835 does enable the corresponding mailbox driver.
>>
>> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
>> ---
>> drivers/mailbox/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/mailbox/Kconfig b/drivers/mailbox/Kconfig
>> index 42940108a187..2b4cde562a90 100644
>> --- a/drivers/mailbox/Kconfig
>> +++ b/drivers/mailbox/Kconfig
>> @@ -109,6 +109,7 @@ config ALTERA_MBOX
>> config BCM2835_MBOX
>> tristate "BCM2835 Mailbox"
>> depends on ARCH_BCM2835
>> + default ARCH_BCM2835
>
> This is just "default y", since I doubt ARCH_BCM2835 can be a module?
Right, although I intend to also add COMPILE_TEST, by then, it might be
preferable to have it "default ARCH_BCM2835".
>
> If so, patch 2 could also just be "default y" and I think patch 3 can
> have the same logic applied to it, given you're defaulting it to a
> dependency also?
Right.
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
next prev parent reply other threads:[~2024-05-14 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 23:52 [PATCH 0/3] ARCH_BCM2835 Kconfig changes Florian Fainelli
2024-05-13 23:52 ` [PATCH 1/3] mailbox: Make BCM2835_MBOX default to ARCH_BCM2835 Florian Fainelli
2024-05-14 12:29 ` Conor Dooley
2024-05-14 16:20 ` Florian Fainelli [this message]
2024-05-15 7:54 ` Conor Dooley
2024-05-31 21:36 ` Florian Fainelli
2024-05-13 23:52 ` [PATCH 2/3] firmware: Default RASPBERRYPI_FIRMWARE " Florian Fainelli
2024-05-13 23:52 ` [PATCH 3/3] clk: bcm: Make CLK_RASPBERRYPI default to RASPBERRYPI_FIRMWARE Florian Fainelli
2024-05-14 21:06 ` Stephen Boyd
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=b422f395-7554-4596-b779-268718b34383@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=ardb@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=johan+linaro@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=mst@redhat.com \
--cc=mturquette@baylibre.com \
--cc=quic_bjorande@quicinc.com \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.com \
--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