U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: rafael@beims.me,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	Rafael Beims <rafael.beims@toradex.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH] toradex: apalis-imx6: Fix build failure when CONFIG_VIDEO_IPUV3 is enabled
Date: Mon, 31 Mar 2025 08:11:15 -0600	[thread overview]
Message-ID: <20250331141115.GU93000@bill-the-cat> (raw)
In-Reply-To: <20250330185632.GA6356@francesco-nb>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

On Sun, Mar 30, 2025 at 08:56:32PM +0200, Francesco Dolcini wrote:
> On Fri, Mar 28, 2025 at 10:05:57AM -0600, Tom Rini wrote:
> > On Fri, Mar 28, 2025 at 11:20:40AM +0100, rafael@beims.me wrote:
> > 
> > > From: Rafael Beims <rafael.beims@toradex.com>
> > > 
> > > If CONFIG_VIDEO_IPUV3 is enabled without also having CONFIG_IMX_HDMI
> > > enabled, the build fails for the Apalis iMX6 board.
> > > 
> > > Fixes: 592f4aed6db7 ("arm: imx: initial support for apalis imx6")
> > > Signed-off-by: Rafael Beims <rafael.beims@toradex.com>
> > > ---
> > >  board/toradex/apalis_imx6/apalis_imx6.c | 14 ++++++++++++--
> > >  1 file changed, 12 insertions(+), 2 deletions(-)
> > 
> > Is there a reason why this requirement isn't enforced at the Kconfig
> > level? In other words is (CONFIG_VIDEO_IPUV3=y && CONFIG_IMX_HDMI=n) an
> > otherwise useful and valid configuration?
> 
> I would say no. You can have the display output over DPI or LVDS, with
> HDMI non being required at all.

And so yes, it's a useful and valid configuration. OK, thanks.

Reviewed-by: Tom Rini <trini@konsulko.com>

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2025-03-31 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 10:20 [PATCH] toradex: apalis-imx6: Fix build failure when CONFIG_VIDEO_IPUV3 is enabled rafael
2025-03-28 12:52 ` Francesco Dolcini
2025-03-28 16:05 ` Tom Rini
2025-03-30 18:56   ` Francesco Dolcini
2025-03-31 14:11     ` Tom Rini [this message]
2025-04-11 14:16 ` Fabio Estevam

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=20250331141115.GU93000@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=francesco@dolcini.it \
    --cc=rafael.beims@toradex.com \
    --cc=rafael@beims.me \
    --cc=u-boot@lists.denx.de \
    /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