Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp5171031ybl; Tue, 10 Dec 2019 01:33:19 -0800 (PST) X-Google-Smtp-Source: APXvYqwoiVjeTT7ABqethwDCUjhFNqz61eEjut9bxOTco/+H5L8gD0seIUmmhTF9Chc4T+ZrZnKz X-Received: by 2002:a9d:dc1:: with SMTP id 59mr17310027ots.250.1575970399154; Tue, 10 Dec 2019 01:33:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575970399; cv=none; d=google.com; s=arc-20160816; b=cSxsKZpLeyaL0h7QoosYPBTxbS6N7Z8NSQbzrKgCjwigCO1xRhSdhVXFg8XlByApVK fOg0xcqMIL3852nrcT2uTfXVbu5mDv4mXQEE75ZvIDkAVjREVAlcP6PeO1r4CLw4Oidp wQ3CZIMwFVujHk344mvh6XbK5yRa9Mx3DaTN2/1L9ZaD433nke6HYg/Xx5Hny38OG0AD Ux9ofaHUH4svUu9/mUHRaj7+wNIBnsIs7GZmx/GbDhHAsqFca+C3JpO0yXpnA8wLRnE3 oVNbfFmCpqjp2Rt8D8Fhlxyknp/gl8obOoE8KotgsDCjLlZ+bbzykHfUEWoJqY+QGiYt ExDA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=PSQScSDnlo93GQoR20fpTB0eabm3bHRkOsN6d+uG2Do=; b=Upv23JchkS4VQ3+bmZ4slwmcr9UfGDqCsZeJ4rlL6OzgzHkyZot6x32pPBlokwDmGk +GmtC9iYsdmZVWR4x8tsPntTZ8/Y2Tpyy9W/wZgC/6RoMygPUFOlmbu3jGmTq6RkVXze KgXJOsknnIcxSsFLl3TOe0YvfhRhvdtphCk/bLTYHNXMGvIW5Red1436ZtP69h7R2Yhp aA5d5O+Vkj2N0MMWf9n9NkdQK6CvTdEuWLfEvcqrL9o1vCyOF/G3FzTCD6hBp0cxt3d0 aB+nNySq/WlRnB9bhq1aUUpUAAfCMgJLBXKryTZP9Gnm9kfAGnk6mrvXFLInAEIOGYXJ ZJhA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=eNIDMvR7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a136si1621976oib.252.2019.12.10.01.33.06; Tue, 10 Dec 2019 01:33:19 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=eNIDMvR7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727306AbfLJJcd (ORCPT + 99 others); Tue, 10 Dec 2019 04:32:33 -0500 Received: from mail-wm1-f66.google.com ([209.85.128.66]:35821 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726915AbfLJJcd (ORCPT ); Tue, 10 Dec 2019 04:32:33 -0500 Received: by mail-wm1-f66.google.com with SMTP id c20so2309074wmb.0 for ; Tue, 10 Dec 2019 01:32:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=PSQScSDnlo93GQoR20fpTB0eabm3bHRkOsN6d+uG2Do=; b=eNIDMvR7jYjMDJ33K7agoubEz5UWh0Io+iFSLRF9tX5UlGsDktzRU0FsSJKS5TNhDd qlzsjbcqiNxRwHPUyzOfiW/xjVrOT7IYd7PwcsGg3vGI/IPjT4UKIhjz5w2JP8ToV1si cZg+la7VhwCun03B5aBU3ewEWjmWEL5W4OWNJ0Sb2ZL5KCCSf4FYxREbcOYL1I9L8wIX 2USnsNPJ13f9zZmRgzK7Br5OyU5kNS+VF4hokDJBl2ARoUAn6vaIlrqpHSwm/4BhIz5u 1mRXLGPXvGNYdg+npJP0+Gnuoz8JTm6CgmlmIJ/bFSKZ3zUuZN6dZy61nRO83mixc+r0 qdHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=PSQScSDnlo93GQoR20fpTB0eabm3bHRkOsN6d+uG2Do=; b=ZJfdbPx9vvW1efiCxOHPkIj3bopMxRCMcC5kfZkNNsc/n/YNJoyO2VBvam7pJML5JG +bHRDqR8sk55yflc9V7ug4mxFhaY/v0F+Eie9zH/kRuzTPg+mbO/xgqZQpVasJbHECbv isXLrwP52gxPlCU0cLXsq/LBTXG3itn5tXoaBgZmwQuBLWqkTNoogn8Ur13gmztJXoyn awtbyhvScp4208ujq/GlkbmlgVGF1R/lyU/mhf4sGG8eSJOWjN9UAWLZxPw1xvZmQKcd LFzyxS1gtWNfd2R+MwbllC9ochq7pduyoq5Ms7JpFYN/AVwa84qVJMNlQmrS89MFKmlD kYsw== X-Gm-Message-State: APjAAAVbGqKk0ySPE4V3Y5zxEuCiC49e+ZEcugL4XUfggczz/OxhYdfJ kMqtGucfSUpnWcAC/alRwqvMjA== X-Received: by 2002:a1c:407:: with SMTP id 7mr3889627wme.29.1575970351127; Tue, 10 Dec 2019 01:32:31 -0800 (PST) Received: from dell (h185-20-99-176.host.redstation.co.uk. [185.20.99.176]) by smtp.gmail.com with ESMTPSA id f1sm2517194wrp.93.2019.12.10.01.32.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 10 Dec 2019 01:32:30 -0800 (PST) Date: Tue, 10 Dec 2019 09:32:25 +0000 From: Lee Jones To: Andreas Kemnade Cc: robh+dt@kernel.org, mark.rutland@arm.com, a.zummo@towertech.it, alexandre.belloni@bootlin.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org, stefan@agner.ch, b.galvani@gmail.com, phh@phh.me, letux-kernel@openphoenux.org Subject: Re: [PATCH v3 3/6] mfd: rn5t618: add irq support Message-ID: <20191210093225.GT3468@dell> References: <20191129212045.18325-1-andreas@kemnade.info> <20191129212045.18325-4-andreas@kemnade.info> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20191129212045.18325-4-andreas@kemnade.info> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 29 Nov 2019, Andreas Kemnade wrote: > This adds support for irq handling in the rc5t619 which is required Please capitalise abbreviations and device names (as they do in the datasheet). > for properly implementing subdevices like rtc. "RTC" > For now only definitions for the variant rc5t619 are included. > > Signed-off-by: Andreas Kemnade > --- > Changes in v3: > alignment cleanup > > Changes in v2: > - no dead code, did some more testing and thinking for that > - remove extra empty lines > > drivers/mfd/Kconfig | 1 + > drivers/mfd/Makefile | 2 +- > drivers/mfd/rn5t618-core.c | 34 ++++++++++++++- > drivers/mfd/rn5t618-irq.c | 85 +++++++++++++++++++++++++++++++++++++ > include/linux/mfd/rn5t618.h | 16 +++++++ > 5 files changed, 136 insertions(+), 2 deletions(-) > create mode 100644 drivers/mfd/rn5t618-irq.c > > diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig > index ae24d3ea68ea..522e068d0082 100644 > --- a/drivers/mfd/Kconfig > +++ b/drivers/mfd/Kconfig > @@ -1057,6 +1057,7 @@ config MFD_RN5T618 > depends on OF > select MFD_CORE > select REGMAP_I2C > + select REGMAP_IRQ > help > Say yes here to add support for the Ricoh RN5T567, > RN5T618, RC5T619 PMIC. > diff --git a/drivers/mfd/Makefile b/drivers/mfd/Makefile > index 110ea700231b..2906d5db67d0 100644 > --- a/drivers/mfd/Makefile > +++ b/drivers/mfd/Makefile > @@ -217,7 +217,7 @@ obj-$(CONFIG_MFD_VIPERBOARD) += viperboard.o > obj-$(CONFIG_MFD_RC5T583) += rc5t583.o rc5t583-irq.o > obj-$(CONFIG_MFD_RK808) += rk808.o > > -rn5t618-objs := rn5t618-core.o > +rn5t618-objs := rn5t618-core.o rn5t618-irq.o > obj-$(CONFIG_MFD_RN5T618) += rn5t618.o > obj-$(CONFIG_MFD_SEC_CORE) += sec-core.o sec-irq.o > obj-$(CONFIG_MFD_SYSCON) += syscon.o > diff --git a/drivers/mfd/rn5t618-core.c b/drivers/mfd/rn5t618-core.c > index da5cd9c92a59..1e2326217681 100644 > --- a/drivers/mfd/rn5t618-core.c > +++ b/drivers/mfd/rn5t618-core.c > @@ -8,6 +8,7 @@ > > #include > #include > +#include > #include > #include > #include > @@ -105,7 +106,8 @@ static int rn5t618_i2c_probe(struct i2c_client *i2c, > > i2c_set_clientdata(i2c, priv); > priv->variant = (long)of_id->data; > - > + priv->chip_irq = i2c->irq; > + priv->dev = &i2c->dev; '\n' > priv->regmap = devm_regmap_init_i2c(i2c, &rn5t618_regmap_config); > if (IS_ERR(priv->regmap)) { > ret = PTR_ERR(priv->regmap); > @@ -137,6 +139,11 @@ static int rn5t618_i2c_probe(struct i2c_client *i2c, > return ret; > } > > + if (priv->chip_irq > 0) { > + if (rn5t618_irq_init(priv)) > + priv->chip_irq = 0; > + } > + > return 0; > } > > @@ -154,15 +161,40 @@ static int rn5t618_i2c_remove(struct i2c_client *i2c) > return 0; > } > > +static int __maybe_unused rn5t618_i2c_suspend(struct device *dev) > +{ > + struct rn5t618 *priv = dev_get_drvdata(dev); > + > + if (priv->chip_irq) > + disable_irq(priv->chip_irq); > + > + return 0; > +} > + > +static int __maybe_unused rn5t618_i2c_resume(struct device *dev) > +{ > + struct rn5t618 *priv = dev_get_drvdata(dev); > + > + if (priv->chip_irq) > + enable_irq(priv->chip_irq); > + > + return 0; > +} > + > static const struct i2c_device_id rn5t618_i2c_id[] = { > { } > }; > MODULE_DEVICE_TABLE(i2c, rn5t618_i2c_id); Not this patch I know, but it's strange to see this empty. > +static SIMPLE_DEV_PM_OPS(rn5t618_i2c_dev_pm_ops, > + rn5t618_i2c_suspend, > + rn5t618_i2c_resume); > + > static struct i2c_driver rn5t618_i2c_driver = { > .driver = { > .name = "rn5t618", > .of_match_table = of_match_ptr(rn5t618_of_match), > + .pm = &rn5t618_i2c_dev_pm_ops, > }, > .probe = rn5t618_i2c_probe, > .remove = rn5t618_i2c_remove, > diff --git a/drivers/mfd/rn5t618-irq.c b/drivers/mfd/rn5t618-irq.c Why does this need to be separate from the core file? > new file mode 100644 > index 000000000000..8a4c56429768 > --- /dev/null > +++ b/drivers/mfd/rn5t618-irq.c > @@ -0,0 +1,85 @@ > +// SPDX-License-Identifier: GPL-2.0+ > +/* > + * Copyright 2019 Andreas Kemnade > + */ > +#include > +#include > +#include > +#include > +#include > + > +#include > + > +static const struct regmap_irq rc5t619_irqs[] = { > + [RN5T618_IRQ_SYS] = { > + .reg_offset = 0, > + .mask = (0 << 1) > + }, > + [RN5T618_IRQ_DCDC] = { > + .reg_offset = 0, > + .mask = (1 << 1) BIT() > + }, > + [RN5T618_IRQ_RTC] = { > + .reg_offset = 0, > + .mask = (1 << 2) > + }, > + [RN5T618_IRQ_ADC] = { > + .reg_offset = 0, > + .mask = (1 << 3) > + }, > + [RN5T618_IRQ_GPIO] = { > + .reg_offset = 0, > + .mask = (1 << 4) > + }, > + [RN5T618_IRQ_CHG] = { > + .reg_offset = 0, > + .mask = (1 << 6), > + } > +}; There are probably macros available to tidy this up. Take a look in include/linux/regmap.h > +static const struct regmap_irq_chip rc5t619_irq_chip = { > + .name = "rc5t619", > + .irqs = rc5t619_irqs, > + .num_irqs = ARRAY_SIZE(rc5t619_irqs), > + .num_regs = 1, > + .status_base = RN5T618_INTMON, > + .mask_base = RN5T618_INTEN, > + .mask_invert = true, > +}; > + > +int rn5t618_irq_init(struct rn5t618 *rn5t618) > +{ > + const struct regmap_irq_chip *irq_chip; > + int ret; > + > + if (!rn5t618->chip_irq) > + return 0; > + > + switch (rn5t618->variant) { > + case RC5T619: > + irq_chip = &rc5t619_irq_chip; > + break; > + > + /* TODO: check irq definitions for other variants */ No need for this. It's implied. OOI, when support for more variants be added? > + default: > + irq_chip = NULL; > + break; > + } > + > + if (!irq_chip) { > + dev_err(rn5t618->dev, "no IRQ definition known for variant\n"); How about '"Variant %d not currently supported", rn5t618->variant' > + return -ENOENT; > + } > + > + ret = devm_regmap_add_irq_chip(rn5t618->dev, rn5t618->regmap, > + rn5t618->chip_irq, > + IRQF_TRIGGER_FALLING | IRQF_ONESHOT, > + 0, irq_chip, &rn5t618->irq_data); > + if (ret != 0) { if (ret) > + dev_err(rn5t618->dev, "Failed to register IRQ chip\n"); > + return ret; > + } > + > + return 0; > +} > diff --git a/include/linux/mfd/rn5t618.h b/include/linux/mfd/rn5t618.h > index d62ef48060b5..edd2b6485e3b 100644 > --- a/include/linux/mfd/rn5t618.h > +++ b/include/linux/mfd/rn5t618.h > @@ -242,9 +242,25 @@ enum { > RC5T619, > }; > > +/* RN5T618 IRQ definitions */ > +enum { > + RN5T618_IRQ_SYS, = 0? > + RN5T618_IRQ_DCDC, > + RN5T618_IRQ_RTC, > + RN5T618_IRQ_ADC, > + RN5T618_IRQ_GPIO, > + RN5T618_IRQ_CHG, > + RN5T618_NR_IRQS, > +}; > + > struct rn5t618 { > struct regmap *regmap; > + struct device *dev; > long variant; > + > + int chip_irq; Are there any other kinds of IRQ? If you don't have to differentiate between multiple, just 'irq' will do. This could also get confused with 'irq_chip'. > + struct regmap_irq_chip_data *irq_data; > }; > > +extern int rn5t618_irq_init(struct rn5t618 *rn5t618); > #endif /* __LINUX_MFD_RN5T618_H */ -- Lee Jones [李琼斯] Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog