From: Carsten Haitzler <carsten.haitzler@foss.arm.com>
To: Mark Brown <broonie@kernel.org>, Liviu Dudau <liviu.dudau@arm.com>
Cc: 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:15:09 +0100 [thread overview]
Message-ID: <ef15cca3-61fa-a01a-6050-c687e5328813@foss.arm.com> (raw)
In-Reply-To: <Ynu2X/SwS7XqEEEs@sirena.org.uk>
On 5/11/22 14:13, Mark Brown wrote:
> 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.
Ah - well either way- job done. :) No need to spin up a patch then :)
next prev parent reply other threads:[~2022-05-11 13:15 UTC|newest]
Thread overview: 21+ 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-10 11:15 ` Sudeep Holla
2022-05-10 11:27 ` Mark Brown
2022-05-10 11:56 ` Robin Murphy
2022-05-10 12:01 ` Sudeep Holla
2022-05-10 12:07 ` Sudeep Holla
2022-05-10 12:34 ` Carsten Haitzler
2022-05-10 14:51 ` Sudeep Holla
2022-05-10 14:53 ` Carsten Haitzler
2022-05-10 12:55 ` Liviu Dudau
2022-05-10 13:05 ` Mark Brown
2022-05-10 14:05 ` Carsten Haitzler
2022-05-10 16:19 ` Liviu Dudau
2022-05-10 16:31 ` Mark Brown
2022-05-10 20:06 ` Liviu Dudau
2022-05-11 13:13 ` Mark Brown
2022-05-11 13:15 ` Carsten Haitzler [this message]
2022-05-11 11:00 ` Carsten Haitzler
-- strict thread matches above, loose matches on Subject: below --
2022-04-27 11:42 carsten.haitzler
2022-05-09 14:34 ` Arnd Bergmann
2022-05-10 12:42 ` Carsten Haitzler
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=ef15cca3-61fa-a01a-6050-c687e5328813@foss.arm.com \
--to=carsten.haitzler@foss.arm.com \
--cc=broonie@kernel.org \
--cc=carsten.haitzler@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox