[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1352815439-26040-1-git-send-email-ldewangan@nvidia.com>
Date: Tue, 13 Nov 2012 19:33:55 +0530
From: Laxman Dewangan <ldewangan@...dia.com>
To: <sameo@...ux.intel.com>
CC: <broonie@...nsource.wolfsonmicro.com>, <swarren@...dia.com>,
<linux-kernel@...r.kernel.org>,
Laxman Dewangan <ldewangan@...dia.com>
Subject: [PATCH V3 RESEND 0/4] mfd: tps65910: use regmap irq framework for interrupt
This patch series has following change:
- Use regmap irq framework for interrupt registration. Corrected the
register bit definition for interrupts.
- Move the irq table to tps65910.c and get rid of tps65910-irq.c.
- Raarrange the init sequence of different sub moduled of tps65910 like
irq, clock and then mfd devices.
- Export the irq domain handle from regmap to use in mfd driver.
- Pass the irq domain in mfd_add_devices to have proper interrupt mapping
for sub devices like RTC.
Changes from V1:
- rearrange patch on which older patch3 become the new patch 1.
- Add stub for new api in the regmap.
- Add empty line if paragraph change in description.
Changes from V2:
- Remove the older 4th patch where API for getting irq_domain was added
in regmap. It is already taken care by Mark B.
Laxman Dewangan (4):
mfd: tps65910: Initialize mfd devices after all initialization done
mfd: tps65910: use regmap irq framework for interrupt support
mfd: tps65910: move interrupt implementation code to mfd file
mfd: tps65910: pass irq_domain when adding mfd sub devices
drivers/mfd/Makefile | 2 +-
drivers/mfd/tps65910-irq.c | 260 ------------------------------------------
drivers/mfd/tps65910.c | 233 ++++++++++++++++++++++++++++++++++++--
include/linux/mfd/tps65910.h | 143 ++++++++++++++++-------
4 files changed, 325 insertions(+), 313 deletions(-)
delete mode 100644 drivers/mfd/tps65910-irq.c
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists