[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <399d6e4fcbaa590bcd92869e7d02402a9226cad2.camel@opensource.cirrus.com>
Date: Wed, 22 Nov 2023 15:51:06 +0000
From: Maciej Strozek <mstrozek@...nsource.cirrus.com>
To: Charles Keepax <ckeepax@...nsource.cirrus.com>
CC: Mark Brown <broonie@...nel.org>,
James Schulman <james.schulman@...rus.com>,
David Rhodes <david.rhodes@...rus.com>,
"Liam Girdwood" <lgirdwood@...il.com>,
<alsa-devel@...a-project.org>, <patches@...nsource.cirrus.com>,
<linux-sound@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4] ASoC: cs43130: Allow driver to work without IRQ
connection
W dniu śro, 22.11.2023 o godzinie 15∶42 +0000, użytkownik Charles
Keepax napisał:
> On Wed, Nov 22, 2023 at 02:34:59PM +0000, Maciej Strozek wrote:
> > Add a polling mechanism that will keep the driver operational even
> > in
> > absence of physical IRQ connection. If IRQ line is detected, the
> > driver
> > will continue working as usual, in case of missing IRQ line it will
> > fallback to the polling mechanism introduced in this change.
> > This will support users which choose not to connect an IRQ line as
> > it
> > is not critical to part's operation.
> >
> > Signed-off-by: Maciej Strozek <mstrozek@...nsource.cirrus.com>
> > ---
>
> Apologies Maciej, should have spotted this when I had a look this
> morning but I have just spotted one more thing, we should actually
> remove the polling for the hpload detect. The hpload detect can
> actually only be triggered by the IRQ handler anyway so that code
> will never run, and there would be much more work required to get
> the jack detect working without the IRQ.
>
> Thanks,
> Charles
No problem, will send V5 with the hpload detect deleted tomorrow
Powered by blists - more mailing lists