From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Florian Fainelli <f.fainelli@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
Michal Simek <michal.simek@xilinx.com>
Cc: alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Prabhakar <prabhakar.csengg@gmail.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [PATCH 0/2] sound/soc: Use platform_get_irq() to fetch IRQ's
Date: Sun, 19 Dec 2021 18:10:37 +0000 [thread overview]
Message-ID: <20211219181039.24812-1-prabhakar.mahadev-lad.rj@bp.renesas.com> (raw)
Hi All,
This patch series aims to drop using platform_get_resource() for IRQ types
in preparation for removal of static setup of IRQ resource from DT core
code.
Dropping usage of platform_get_resource() was agreed based on
the discussion [0].
[0] https://patchwork.kernel.org/project/linux-renesas-soc/
patch/20211209001056.29774-1-prabhakar.mahadev-lad.rj@bp.renesas.com/
Note: I have just build tested the patches.
Cheers,
Prabhakar
Lad Prabhakar (2):
ASoC: xlnx: Use platform_get_irq() to get the interrupt
ASoC: bcm: Use platform_get_irq() to get the interrupt
sound/soc/bcm/bcm63xx-i2s.h | 1 -
sound/soc/bcm/bcm63xx-pcm-whistler.c | 12 +++++-------
sound/soc/xilinx/xlnx_spdif.c | 10 +++-------
3 files changed, 8 insertions(+), 15 deletions(-)
--
2.17.1
next reply other threads:[~2021-12-19 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 18:10 Lad Prabhakar [this message]
2021-12-19 18:10 ` [PATCH 1/2] ASoC: xlnx: Use platform_get_irq() to get the interrupt Lad Prabhakar
2021-12-19 18:10 ` [PATCH 2/2] ASoC: bcm: " Lad Prabhakar
2021-12-19 18:20 ` Florian Fainelli
2021-12-20 18:30 ` Mark Brown
2021-12-21 19:12 ` [PATCH 0/2] sound/soc: Use platform_get_irq() to fetch IRQ's Mark Brown
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=20211219181039.24812-1-prabhakar.mahadev-lad.rj@bp.renesas.com \
--to=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=perex@perex.cz \
--cc=prabhakar.csengg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).