[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEnQRZCnQAUVowOJw5aPe9rYWU5DKR4bFbmQLYV2BzYqOhRJmQ@mail.gmail.com>
Date: Thu, 5 Dec 2019 10:43:46 +0200
From: Daniel Baluta <daniel.baluta@...il.com>
To: Michael Walle <michael@...le.cc>
Cc: Linux-ALSA <alsa-devel@...a-project.org>,
linuxppc-dev@...ts.ozlabs.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Timur Tabi <timur@...nel.org>,
Nicolin Chen <nicoleotsuka@...il.com>,
Xiubo Li <Xiubo.Lee@...il.com>,
Fabio Estevam <festevam@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH] ASoC: fsl_sai: add IRQF_SHARED
On Fri, Nov 29, 2019 at 12:40 AM Michael Walle <michael@...le.cc> wrote:
>
> The LS1028A SoC uses the same interrupt line for adjacent SAIs. Use
> IRQF_SHARED to be able to use these SAIs simultaneously.
Hi Michael,
Thanks for the patch. We have a similar change inside our internal tree
(it is on my long TODO list to upstream :D).
We add the shared flag conditionally on a dts property.
Do you think it is a good idea to always add shared flag? I'm thinking
on SAI IP integrations where the interrupt is edge triggered.
AFAIK edge triggered interrupts do not get along very well
with sharing an interrupt line.
Powered by blists - more mailing lists