From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: "Shuming [范書銘]" <shumingf@realtek.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"Flove(HsinFu)" <flove@realtek.com>,
"Oder Chiou" <oder_chiou@realtek.com>,
"Jack Yu" <jack.yu@realtek.com>,
"Derek [方德義]" <derek.fang@realtek.com>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.dev>
Subject: Re: [PATCH] ASoC: rt766: add RT766/RT767 SDCA driver
Date: Tue, 21 Jul 2026 11:29:14 +0100 [thread overview]
Message-ID: <al9J+uxU5sJ/i7Dz@opensource.cirrus.com> (raw)
In-Reply-To: <3f470a3c2e2f4123b93c5671dd92fae9@realtek.com>
On Tue, Jul 21, 2026 at 07:10:00AM +0000, Shuming [范書銘] wrote:
> > > + if (ret)
> > > + return ret;
> > > +
> > > + interrupt->priv = rt766;
> > > + ret = sdca_irq_request(dev, info, irq,
> > interrupt->name,
> > > +
> > handler, interrupt);
> > > + if (ret) {
> > > + dev_err(dev, "failed to
> > request irq %s: %d\n",
> > > + interrupt->name,
> > ret);
> > > + return ret;
> > > + }
> > > + dev_dbg(dev, "Requesting IRQ %d
> > InterruptName=%s\n", irq, interrupt->name);
> > > + } else {
> > > + sdca_irq_free(dev, info, irq,
> > interrupt->name, interrupt);
> > > + dev_dbg(dev, "Freeing IRQ %d\n", irq);
> > > + }
> > > + }
> > > + }
> > > +
> > > + return 0;
> > > +}
> >
> > Hmm... yeah this is moving in a slightly different direction from where I was
> > going with the core code. Let me think about that and update tomorrow.
>
> Sorry, I don't quite follow the point.
> Do you mean that it will not work with this patch (ASoC: SDCA: Populate IRQ data earlier)?
Mostly, the issue here is you are calling things at different
times to the class driver, so the devm allocations will probably
leak but I think I will update my patch chain to drop the devm
allocations to keep things flexible. There are some minor updates
required to this patch for my core changes but that is the only
one that doesn't work I think.
I will send out a new spin later today and CC you on it.
Thanks,
Charles
prev parent reply other threads:[~2026-07-21 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 9:06 [PATCH] ASoC: rt766: add RT766/RT767 SDCA driver shumingf
2026-07-20 14:38 ` Pierre-Louis Bossart
2026-07-21 7:09 ` Shuming [范書銘]
2026-07-20 16:21 ` Charles Keepax
2026-07-21 7:10 ` Shuming [范書銘]
2026-07-21 10:29 ` Charles Keepax [this message]
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=al9J+uxU5sJ/i7Dz@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=shumingf@realtek.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.