From: Peter Ujfalusi <peter.ujfalusi@ti.com> To: Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>, Mark Brown <broonie@opensource.wolfsonmicro.com>, Samuel Ortiz <sameo@linux.intel.com>, Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org, Misael Lopez Cruz <misael.lopez@ti.com>, Felipe Balbi <balbi@ti.com> Subject: [PATCH v2 0/5] MFD/input/ASoC: twl6040: irq registration changes Date: Tue, 5 Jul 2011 16:49:30 +0300 [thread overview] Message-ID: <1309873775-17927-1-git-send-email-peter.ujfalusi@ti.com> (raw) Hello, Changes since v1: - IRQ number is passed with resource to the slave devices Intro mail froim v1: As Samuel, and Felipe requested for the twl6040 MFD series: http://marc.info/?l=linux-kernel&m=130978512225430&w=2 http://marc.info/?l=linux-omap&m=130978403224218&w=2 This is the update to remove the obfuscation around the threaded irq request in the twl6040 driver and it's slaves. With this change the slaves uses directly the threaded irq request, and the core driver passes the irq number for the slaves to use (configured runtime, so machine drivers do not need to be updated). Regards, Peter PS: for the remaining comments from Samuel I have changed the series, since the requested change was small. I'm not intended to send the series again, unless it is requested (again the change from v6 is minimal - few lines has been removed/replaced). --- Peter Ujfalusi (5): MFD: twl6040: Use resource to provide irq number for slaves input: twl6040-vibra: Do not use wrapper for irq request ASoC: twl6040: Do not use wrapper for irq request MFD: twl6040: Demand valid interrupt configuration MFD: twl6040: Remove wrapper for threaded irq request drivers/input/misc/twl6040-vibra.c | 17 ++++++--- drivers/mfd/twl6040-core.c | 69 ++++++++++++++++++++++++----------- drivers/mfd/twl6040-irq.c | 16 +-------- include/linux/mfd/twl6040.h | 22 ----------- sound/soc/codecs/twl6040.c | 19 +++++++--- 5 files changed, 74 insertions(+), 69 deletions(-) -- 1.7.6
WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi@ti.com> To: Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>, Mark Brown <broonie@opensource.wolfsonmicro.com>, Samuel Ortiz <sameo@linux.intel.com>, Dmitry Torokhov <dmitry.torokhov@> Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, Felipe Balbi <balbi@ti.com>, Misael Lopez Cruz <misael.lopez@ti.com> Subject: [PATCH v2 0/5] MFD/input/ASoC: twl6040: irq registration changes Date: Tue, 5 Jul 2011 16:49:30 +0300 [thread overview] Message-ID: <1309873775-17927-1-git-send-email-peter.ujfalusi@ti.com> (raw) Hello, Changes since v1: - IRQ number is passed with resource to the slave devices Intro mail froim v1: As Samuel, and Felipe requested for the twl6040 MFD series: http://marc.info/?l=linux-kernel&m=130978512225430&w=2 http://marc.info/?l=linux-omap&m=130978403224218&w=2 This is the update to remove the obfuscation around the threaded irq request in the twl6040 driver and it's slaves. With this change the slaves uses directly the threaded irq request, and the core driver passes the irq number for the slaves to use (configured runtime, so machine drivers do not need to be updated). Regards, Peter PS: for the remaining comments from Samuel I have changed the series, since the requested change was small. I'm not intended to send the series again, unless it is requested (again the change from v6 is minimal - few lines has been removed/replaced). --- Peter Ujfalusi (5): MFD: twl6040: Use resource to provide irq number for slaves input: twl6040-vibra: Do not use wrapper for irq request ASoC: twl6040: Do not use wrapper for irq request MFD: twl6040: Demand valid interrupt configuration MFD: twl6040: Remove wrapper for threaded irq request drivers/input/misc/twl6040-vibra.c | 17 ++++++--- drivers/mfd/twl6040-core.c | 69 ++++++++++++++++++++++++----------- drivers/mfd/twl6040-irq.c | 16 +-------- include/linux/mfd/twl6040.h | 22 ----------- sound/soc/codecs/twl6040.c | 19 +++++++--- 5 files changed, 74 insertions(+), 69 deletions(-) -- 1.7.6
next reply other threads:[~2011-07-05 13:49 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-05 13:49 Peter Ujfalusi [this message] 2011-07-05 13:49 ` [PATCH v2 0/5] MFD/input/ASoC: twl6040: irq registration changes Peter Ujfalusi 2011-07-05 13:49 ` [PATCH v2 1/5] MFD: twl6040: Use resource to provide irq number for slaves Peter Ujfalusi 2011-07-05 13:49 ` Peter Ujfalusi 2011-07-05 13:49 ` [PATCH v2 2/5] input: twl6040-vibra: Do not use wrapper for irq request Peter Ujfalusi 2011-07-05 13:49 ` Peter Ujfalusi 2011-07-05 13:57 ` Felipe Balbi 2011-07-05 14:10 ` Péter Ujfalusi 2011-07-05 14:10 ` Péter Ujfalusi 2011-07-05 13:49 ` [PATCH v2 3/5] ASoC: twl6040: " Peter Ujfalusi 2011-07-05 13:49 ` Peter Ujfalusi 2011-07-05 17:59 ` Mark Brown 2011-07-05 17:59 ` Mark Brown 2011-07-05 22:38 ` Felipe Balbi 2011-07-05 13:49 ` [PATCH v2 4/5] MFD: twl6040: Demand valid interrupt configuration Peter Ujfalusi 2011-07-05 13:49 ` Peter Ujfalusi 2011-07-05 13:49 ` [PATCH v2 5/5] MFD: twl6040: Remove wrapper for threaded irq request Peter Ujfalusi 2011-07-05 13:49 ` Peter Ujfalusi
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=1309873775-17927-1-git-send-email-peter.ujfalusi@ti.com \ --to=peter.ujfalusi@ti.com \ --cc=alsa-devel@alsa-project.org \ --cc=balbi@ti.com \ --cc=broonie@opensource.wolfsonmicro.com \ --cc=dmitry.torokhov@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=lrg@ti.com \ --cc=misael.lopez@ti.com \ --cc=sameo@linux.intel.com \ --cc=tony@atomide.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: linkBe 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.