From: Florian Fainelli <florian.fainelli@broadcom.com>
To: linux-kernel@vger.kernel.org
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
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>,
linux-clk@vger.kernel.org (open list:COMMON CLK FRAMEWORK),
Stefan Wahren <wahrenst@gmx.net>
Subject: [PATCH v2 0/3] ARCH_BCM2835 Kconfig changes
Date: Fri, 31 May 2024 14:29:39 -0700 [thread overview]
Message-ID: <20240531212942.3340484-1-florian.fainelli@broadcom.com> (raw)
This patch series updates a number of Kconfig entries such that enable
ARCH_BCM2835 guarantees that essential drivers are also enabled, saves a
lot of configuration and troubleshooting time for when they are not.
Changes in v2:
- used "default y" instead of "default ARCH_BCM2835" per Conor's
suggestion
- added Stephen's ack to the clock driver
Florian Fainelli (3):
mailbox: Make BCM2835_MBOX default to ARCH_BCM2835
firmware: Default RASPBERRYPI_FIRMWARE to y
clk: bcm: Make CLK_RASPBERRYPI default to RASPBERRYPI_FIRMWARE
drivers/clk/bcm/Kconfig | 1 +
drivers/firmware/Kconfig | 1 +
drivers/mailbox/Kconfig | 1 +
3 files changed, 3 insertions(+)
--
2.34.1
next reply other threads:[~2024-05-31 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 21:29 Florian Fainelli [this message]
2024-05-31 21:29 ` [PATCH v2 1/3] mailbox: Make BCM2835_MBOX default to ARCH_BCM2835 Florian Fainelli
2024-05-31 21:29 ` [PATCH v2 2/3] firmware: Default RASPBERRYPI_FIRMWARE to y Florian Fainelli
2024-05-31 21:29 ` [PATCH v2 3/3] clk: bcm: Make CLK_RASPBERRYPI default to RASPBERRYPI_FIRMWARE Florian Fainelli
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=20240531212942.3340484-1-florian.fainelli@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=ardb@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=conor.dooley@microchip.com \
--cc=jassisinghbrar@gmail.com \
--cc=johan+linaro@kernel.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
all inboxes | Powered by JetHome®