Hello Krzysztof, On 06/09/2014 12:22 PM, Krzysztof Kozlowski wrote: > On pon, 2014-06-09 at 11:37 +0200, Javier Martinez Canillas wrote: >> Maxim MAX77802 is a power management chip that contains 10 high >> efficiency Buck regulators, 32 Low-dropout (LDO) regulators used >> to power up application processors and peripherals, a 2-channel >> 32kHz clock outputs, a Real-Time-Clock (RTC) and a I2C interface >> to program the individual regulators, clocks outputs and the RTC. >> >> This patch adds the core support for MAX77802 PMIC and is based >> on a driver added by Simon Glass to the Chrome OS kernel 3.8 tree. >> >> Signed-off-by: Javier Martinez Canillas <javier.martinez@xxxxxxxxxxxxxxx> > > (...) > > >> diff --git a/drivers/mfd/max77802-irq.c b/drivers/mfd/max77802-irq.c >> new file mode 100644 >> index 0000000..38a8ce7 >> --- /dev/null >> +++ b/drivers/mfd/max77802-irq.c >> @@ -0,0 +1,332 @@ >> +/* >> + * max77802-irq.c - Interrupt controller support for MAX77802 >> + * >> + * Copyright (C) 2013-2014 Google, Inc >> + * >> + * Copyright (C) 2012 Samsung Electronics Co.Ltd >> + * Chiwoong Byun <woong.byun@xxxxxxxxxxx> >> + * >> + * This program is free software; you can redistribute it and/or modify >> + * it under the terms of the GNU General Public License as published by >> + * the Free Software Foundation; either version 2 of the License, or >> + * (at your option) any later version. >> + * >> + * This program is distributed in the hope that it will be useful, >> + * but WITHOUT ANY WARRANTY; without even the implied warranty of >> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the >> + * GNU General Public License for more details. >> + * >> + * This driver is based on max8997-irq.c >> + */ >> + >> +#include <linux/err.h> >> +#include <linux/irq.h> >> +#include <linux/interrupt.h> >> +#include <linux/gpio.h> >> +#include <linux/mfd/max77802.h> >> +#include <linux/mfd/max77802-private.h> >> +#include <linux/irqdomain.h> >> +#include <linux/regmap.h> >> + >> +enum { >> + MAX77802_DEBUG_IRQ_INFO = 1 << 0, >> + MAX77802_DEBUG_IRQ_MASK = 1 << 1, >> + MAX77802_DEBUG_IRQ_INT = 1 << 2, >> +}; >> + >> +static int debug_mask = 0; >> +module_param(debug_mask, int, 0); >> +MODULE_PARM_DESC(debug_mask, "Set debug_mask : 0x0=off 0x1=IRQ_INFO 0x2=IRQ_MASK 0x4=IRQ_INI)"); >> + >> +static const u8 max77802_mask_reg[] = { >> + [PMIC_INT1] = MAX77802_REG_INT1MSK, >> + [PMIC_INT2] = MAX77802_REG_INT2MSK, >> + [RTC_INT] = MAX77802_RTC_INTM, >> +}; >> + >> +struct max77802_irq_data { >> + int mask; >> + enum max77802_irq_source group; >> +}; >> + >> +#define DECLARE_IRQ(idx, _group, _mask) \ >> + [(idx)] = { .group = (_group), .mask = (_mask) } >> +static const struct max77802_irq_data max77802_irqs[] = { >> + DECLARE_IRQ(MAX77802_PMICIRQ_PWRONF, PMIC_INT1, 1 << 0), >> + DECLARE_IRQ(MAX77802_PMICIRQ_PWRONR, PMIC_INT1, 1 << 1), >> + DECLARE_IRQ(MAX77802_PMICIRQ_JIGONBF, PMIC_INT1, 1 << 2), >> + DECLARE_IRQ(MAX77802_PMICIRQ_JIGONBR, PMIC_INT1, 1 << 3), >> + DECLARE_IRQ(MAX77802_PMICIRQ_ACOKBF, PMIC_INT1, 1 << 4), >> + DECLARE_IRQ(MAX77802_PMICIRQ_ACOKBR, PMIC_INT1, 1 << 5), >> + DECLARE_IRQ(MAX77802_PMICIRQ_ONKEY1S, PMIC_INT1, 1 << 6), >> + DECLARE_IRQ(MAX77802_PMICIRQ_MRSTB, PMIC_INT1, 1 << 7), >> + DECLARE_IRQ(MAX77802_PMICIRQ_140C, PMIC_INT2, 1 << 0), >> + DECLARE_IRQ(MAX77802_PMICIRQ_120C, PMIC_INT2, 1 << 1), >> + DECLARE_IRQ(MAX77802_RTCIRQ_RTC60S, RTC_INT, 1 << 0), >> + DECLARE_IRQ(MAX77802_RTCIRQ_RTCA1, RTC_INT, 1 << 1), >> + DECLARE_IRQ(MAX77802_RTCIRQ_RTCA2, RTC_INT, 1 << 2), >> + DECLARE_IRQ(MAX77802_RTCIRQ_SMPL, RTC_INT, 1 << 3), >> + DECLARE_IRQ(MAX77802_RTCIRQ_RTC1S, RTC_INT, 1 << 4), >> + DECLARE_IRQ(MAX77802_RTCIRQ_WTSR, RTC_INT, 1 << 5), >> +}; > > Why just not use two regmap_irq_chips (for PMIC and RTC blocks) > replacing whole max77802-irq.c file? > Great, I was not aware about regmap_irq_chip. I'll take a look to it for v2. > Best regards, > Krzysztof > > Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html