summaryrefslogtreecommitdiffstats
path: root/include/sound
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2024-08-08 21:57:13 +0100
committerMark Brown <broonie@kernel.org>2024-08-08 21:57:13 +0100
commit5db564d4242e12c1de9ef294d7252dbb90898922 (patch)
treeb033a3c3389d1d33e672694c3132e3d6025dfa80 /include/sound
parent001f8443d480773117a013a07f774d252f369bea (diff)
parentcaab9a1cbb9a9fca24ceabeef57b3764d861ad32 (diff)
downloadlinux-stable-5db564d4242e12c1de9ef294d7252dbb90898922.tar.gz
linux-stable-5db564d4242e12c1de9ef294d7252dbb90898922.tar.bz2
linux-stable-5db564d4242e12c1de9ef294d7252dbb90898922.zip
ASoC: tas*: Fix up GPIO usage
Merge series from Linus Walleij <linus.walleij@linaro.org>: The TI TAS drivers use some legacy GPIO code and headers, this series fixes it up. The TAS2781 is a special case since it adds a handful of lines of deviating code to reconfigure a GPIO line for IRQ mode and then never actually use the IRQ obtained in the code. Is the line used by autonomous hardware? I'm puzzled by this. Anyways the patch suggest how to solve this properly by fixing the parent irqchip and I'm happy to help.
Diffstat (limited to 'include/sound')
-rw-r--r--include/sound/tas2781.h7
1 files changed, 1 insertions, 6 deletions
diff --git a/include/sound/tas2781.h b/include/sound/tas2781.h
index 18161d02a96f..dbda552398b5 100644
--- a/include/sound/tas2781.h
+++ b/include/sound/tas2781.h
@@ -81,11 +81,6 @@ struct tasdevice {
bool is_loaderr;
};
-struct tasdevice_irqinfo {
- int irq_gpio;
- int irq;
-};
-
struct calidata {
unsigned char *data;
unsigned long total_sz;
@@ -93,7 +88,6 @@ struct calidata {
struct tasdevice_priv {
struct tasdevice tasdevice[TASDEVICE_MAX_CHANNELS];
- struct tasdevice_irqinfo irq_info;
struct tasdevice_rca rcabin;
struct calidata cali_data;
struct tasdevice_fw *fmw;
@@ -115,6 +109,7 @@ struct tasdevice_priv {
unsigned int chip_id;
unsigned int sysclk;
+ int irq;
int cur_prog;
int cur_conf;
int fw_state;