All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Liviu Dudau <liviu.dudau@arm.com>
Cc: Carsten Haitzler <carsten.haitzler@foss.arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	carsten.haitzler@arm.com, soc@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] arm64: defconfig: Enable modules for arm displays
Date: Wed, 11 May 2022 14:13:03 +0100	[thread overview]
Message-ID: <Ynu2X/SwS7XqEEEs@sirena.org.uk> (raw)
In-Reply-To: <YnrF3Nc7NbcX6v3b@e110455-lin.cambridge.arm.com>

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

On Tue, May 10, 2022 at 09:06:52PM +0100, Liviu Dudau wrote:

> The quickest way is to harmonise the treatment of IRQs between tda998x and tda9950.
> The former treats the IRQ as optional, the later as mandatory. Given that (according
> to comments in the code) TDA998X is actually a TDA9989+TDA9950, it makes sense to
> treat the lack of IRQ the same way (make it optional, IMHO).

The check in tda9950 is sensible enough, the device relies on interrupts
to report the status of CEC operations so we'd need to poll constantly
which doesn't seem great.  It wouldn't be *so* bad for things initiated
by the device but given that CEC is a network and we might get messages
from other devices in the system at any time we'd need to poll
constantly even when otherwise idle which doesn't seem good.  I sent a
patch to lower the level of the log message, hopefully that's OK for
people.

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

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Liviu Dudau <liviu.dudau@arm.com>
Cc: Carsten Haitzler <carsten.haitzler@foss.arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	carsten.haitzler@arm.com, soc@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] arm64: defconfig: Enable modules for arm displays
Date: Wed, 11 May 2022 14:13:03 +0100	[thread overview]
Message-ID: <Ynu2X/SwS7XqEEEs@sirena.org.uk> (raw)
In-Reply-To: <YnrF3Nc7NbcX6v3b@e110455-lin.cambridge.arm.com>


[-- Attachment #1.1: Type: text/plain, Size: 897 bytes --]

On Tue, May 10, 2022 at 09:06:52PM +0100, Liviu Dudau wrote:

> The quickest way is to harmonise the treatment of IRQs between tda998x and tda9950.
> The former treats the IRQ as optional, the later as mandatory. Given that (according
> to comments in the code) TDA998X is actually a TDA9989+TDA9950, it makes sense to
> treat the lack of IRQ the same way (make it optional, IMHO).

The check in tda9950 is sensible enough, the device relies on interrupts
to report the status of CEC operations so we'd need to poll constantly
which doesn't seem great.  It wouldn't be *so* bad for things initiated
by the device but given that CEC is a network and we might get messages
from other devices in the system at any time we'd need to poll
constantly even when otherwise idle which doesn't seem good.  I sent a
patch to lower the level of the log message, hopefully that's OK for
people.

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-05-11 13:13 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 12:55 [PATCH] arm64: defconfig: Enable modules for arm displays carsten.haitzler
2022-05-09 12:55 ` carsten.haitzler
2022-05-10 11:15 ` Sudeep Holla
2022-05-10 11:15   ` Sudeep Holla
2022-05-10 11:27   ` Mark Brown
2022-05-10 11:27     ` Mark Brown
2022-05-10 11:56     ` Robin Murphy
2022-05-10 11:56       ` Robin Murphy
2022-05-10 12:01       ` Sudeep Holla
2022-05-10 12:01         ` Sudeep Holla
2022-05-10 12:07     ` Sudeep Holla
2022-05-10 12:07       ` Sudeep Holla
2022-05-10 12:34       ` Carsten Haitzler
2022-05-10 12:34         ` Carsten Haitzler
2022-05-10 14:51         ` Sudeep Holla
2022-05-10 14:51           ` Sudeep Holla
2022-05-10 14:53           ` Carsten Haitzler
2022-05-10 14:53             ` Carsten Haitzler
2022-05-10 12:55   ` Liviu Dudau
2022-05-10 12:55     ` Liviu Dudau
2022-05-10 13:05     ` Mark Brown
2022-05-10 13:05       ` Mark Brown
2022-05-10 14:05       ` Carsten Haitzler
2022-05-10 14:05         ` Carsten Haitzler
2022-05-10 16:19         ` Liviu Dudau
2022-05-10 16:19           ` Liviu Dudau
2022-05-10 16:31           ` Mark Brown
2022-05-10 16:31             ` Mark Brown
2022-05-10 20:06             ` Liviu Dudau
2022-05-10 20:06               ` Liviu Dudau
2022-05-11 13:13               ` Mark Brown [this message]
2022-05-11 13:13                 ` Mark Brown
2022-05-11 13:15                 ` Carsten Haitzler
2022-05-11 13:15                   ` Carsten Haitzler
2022-05-11 11:00             ` Carsten Haitzler
2022-05-11 11:00               ` Carsten Haitzler
  -- strict thread matches above, loose matches on Subject: below --
2022-04-27 11:42 carsten.haitzler
2022-04-27 11:42 ` carsten.haitzler
2022-05-09 14:34 ` Arnd Bergmann
2022-05-09 14:34   ` Arnd Bergmann
2022-05-10 12:42   ` Carsten Haitzler
2022-05-10 12:42     ` Carsten Haitzler
2022-01-28 10:07 carsten.haitzler
2022-01-28 10:07 ` carsten.haitzler
2022-04-21 12:09 ` Carsten Haitzler
2022-04-21 12:09   ` Carsten Haitzler
2022-04-21 12:18   ` Krzysztof Kozlowski
2022-04-21 12:18     ` Krzysztof Kozlowski

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=Ynu2X/SwS7XqEEEs@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=carsten.haitzler@arm.com \
    --cc=carsten.haitzler@foss.arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=liviu.dudau@arm.com \
    --cc=robin.murphy@arm.com \
    --cc=soc@kernel.org \
    --cc=sudeep.holla@arm.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 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.