From: Johan Hovold <johan@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Dikshita Agarwal <quic_dikshita@quicinc.com>,
quic_vgarodia@quicinc.com, quic_abhinavk@quicinc.com,
mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
p.zabel@pengutronix.de, sebastian.fricke@collabora.com,
bryan.odonoghue@linaro.org, dmitry.baryshkov@linaro.org,
neil.armstrong@linaro.org, nicolas@ndufresne.ca,
u.kleine-koenig@baylibre.com, stefan.schmidt@linaro.org,
lujianhua000@gmail.com, linux-arm-msm@vger.kernel.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, krzysztof.kozlowski@linaro.org
Subject: Re: [RFC PATCH v10 27/28] media: iris: enable video driver probe of SM8250 SoC
Date: Wed, 5 Feb 2025 15:21:26 +0100 [thread overview]
Message-ID: <Z6Nz5r8Z1BhtD2KZ@hovoldconsulting.com> (raw)
In-Reply-To: <a3cafc25-3453-4a2d-81fb-71730982ddc0@xs4all.nl>
On Wed, Feb 05, 2025 at 02:15:25PM +0100, Hans Verkuil wrote:
> This discussion about probing the driver is holding up the merging of this
> driver unnecessarily. For now, only support the iris driver for SM8250 SoC
> if the venus driver is not enabled:
>
> #if !IS_REACHABLE(CONFIG_VIDEO_QCOM_VENUS)
>
> That should be uncontroversial, and allows us to merge the iris driver.
Sounds good to me, but that should be IS_ENABLED() as otherwise which
driver ends up binding depends on whether venus is built as a module or
not.
Johan
next prev parent reply other threads:[~2025-02-05 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 7:02 [RFC PATCH v10 27/28] media: iris: enable video driver probe of SM8250 SoC Dikshita Agarwal
2025-01-16 9:45 ` Bryan O'Donoghue
2025-01-16 9:51 ` Dikshita Agarwal
2025-01-16 11:09 ` Bryan O'Donoghue
2025-01-16 10:20 ` Dmitry Baryshkov
2025-01-16 10:21 ` Dikshita Agarwal
2025-01-16 10:38 ` Dmitry Baryshkov
2025-02-05 13:15 ` Hans Verkuil
2025-02-05 14:21 ` Johan Hovold [this message]
2025-02-05 14:32 ` Hans Verkuil
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=Z6Nz5r8Z1BhtD2KZ@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=hverkuil@xs4all.nl \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lujianhua000@gmail.com \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_dikshita@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=robh@kernel.org \
--cc=sebastian.fricke@collabora.com \
--cc=stefan.schmidt@linaro.org \
--cc=u.kleine-koenig@baylibre.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