From: Gaston Gonzalez <gascoar@gmail.com>
To: kernel-list@raspberrypi.com, mchehab@kernel.org,
florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, rjui@broadcom.com,
sbranden@broadcom.com, linux-media@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: gascoar@gmail.com
Subject: [PATCH 2/2] media: bcm2835-unicam: remove reference to dropped driver in Kconfig
Date: Fri, 30 Jan 2026 17:45:43 -0300 [thread overview]
Message-ID: <20260130204628.312246-5-gascoar@gmail.com> (raw)
In-Reply-To: <20260130204628.312246-1-gascoar@gmail.com>
The bcm2835-camera driver was dropped in commit <90204a38a760>.
Remove the paragraph in Kconfig making reference to it.
Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
---
drivers/media/platform/broadcom/Kconfig | 5 -----
1 file changed, 5 deletions(-)
diff --git a/drivers/media/platform/broadcom/Kconfig b/drivers/media/platform/broadcom/Kconfig
index 32b76ebfcd9a..93ba565d9a02 100644
--- a/drivers/media/platform/broadcom/Kconfig
+++ b/drivers/media/platform/broadcom/Kconfig
@@ -14,10 +14,5 @@ config VIDEO_BCM2835_UNICAM
This is a V4L2 driver that controls the CSI-2 receiver directly,
independently from the VC4 firmware.
- This driver is mutually exclusive with the use of bcm2835-camera. The
- firmware will disable all access to the peripheral from within the
- firmware if it finds a DT node using it, and bcm2835-camera will
- therefore fail to probe.
-
To compile this driver as a module, choose M here. The module will be
called bcm2835-unicam.
--
2.52.0
next prev parent reply other threads:[~2026-01-30 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 20:45 [PATCH 0/2] media: bcm2835-unicam: remove mentions to dropped driver Gaston Gonzalez
2026-01-30 20:45 ` [PATCH 1/2] media: bcm2835-unicam: remove obsolete comment Gaston Gonzalez
2026-01-30 20:45 ` Gaston Gonzalez [this message]
2026-02-02 7:10 ` [PATCH 0/2] media: bcm2835-unicam: remove mentions to dropped driver Jai Luthra
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=20260130204628.312246-5-gascoar@gmail.com \
--to=gascoar@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=kernel-list@raspberrypi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/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