All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Mark Brown <broonie@kernel.org>
Cc: David Airlie <airlied@linux.ie>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i2c: tda9950: Lower severity of log message about missing interrupts
Date: Mon, 6 Jun 2022 18:42:26 +0100	[thread overview]
Message-ID: <Yp48gqLTp8Bwu7rG@shell.armlinux.org.uk> (raw)
In-Reply-To: <20220606171436.2438051-1-broonie@kernel.org>

On Mon, Jun 06, 2022 at 06:14:36PM +0100, Mark Brown wrote:
> The tda9950 driver prints an error message if it is instantiated without
> an interrupt being available since the device is non-functional in that
> case. Unfortunately due to packaging of tda9950 with tda998x series devices
> the tda998x driver unconditionally instantiates a tda9950 so systems with a
> tda998x configured without an interrupt will trigger this error message
> during boot if tda9950 support is available. Reduce the severity to debug
> level so this is less likely to be presented to end users, the information
> is still there for system integrators who run into problems.
> 
> We could add a check for an interrupt to the tda998x driver instead but
> this feels better from an encapsulation point of view, there's still a log
> message to help anyone doing system integration.

As the tda998x also makes use of the interrupt, it would be trivial to
avoid instantiating the tda9950 device if there's no interrupt. tda9950
does require it, and if it's missing, then it isn't functional. No
point wasting memory on the struct device.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2022-06-06 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 17:14 [PATCH] drm/i2c: tda9950: Lower severity of log message about missing interrupts Mark Brown
2022-06-06 17:42 ` Russell King (Oracle) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-10 17:15 Mark Brown

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=Yp48gqLTp8Bwu7rG@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=airlied@linux.ie \
    --cc=broonie@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hverkuil-cisco@xs4all.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.