linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: chen.zhong@mediatek.com (Chen Zhong)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/6] mfd: mt6397: create irq mappings in mfd core driver
Date: Wed, 27 Sep 2017 18:44:03 +0800	[thread overview]
Message-ID: <1506509048-19032-2-git-send-email-chen.zhong@mediatek.com> (raw)
In-Reply-To: <1506509048-19032-1-git-send-email-chen.zhong@mediatek.com>

The core driver should create and manage irq mappings instead of
leaf drivers. This patch change to pass irq domain to
devm_mfd_add_devices() and it will create mapping for irq resources
automatically. And remove irq mapping in rtc driver since this has
been done in core driver.

Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
Acked-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Signed-off-by: Chen Zhong <chen.zhong@mediatek.com>
---
 drivers/mfd/mt6397-core.c |    4 ++--
 drivers/rtc/rtc-mt6397.c  |    7 +++----
 2 files changed, 5 insertions(+), 6 deletions(-)

diff --git a/drivers/mfd/mt6397-core.c b/drivers/mfd/mt6397-core.c
index 04a601f..6546d7f 100644
--- a/drivers/mfd/mt6397-core.c
+++ b/drivers/mfd/mt6397-core.c
@@ -289,7 +289,7 @@ static int mt6397_probe(struct platform_device *pdev)
 
 		ret = devm_mfd_add_devices(&pdev->dev, -1, mt6323_devs,
 					   ARRAY_SIZE(mt6323_devs), NULL,
-					   0, NULL);
+					   0, pmic->irq_domain);
 		break;
 
 	case MT6397_CID_CODE:
@@ -304,7 +304,7 @@ static int mt6397_probe(struct platform_device *pdev)
 
 		ret = devm_mfd_add_devices(&pdev->dev, -1, mt6397_devs,
 					   ARRAY_SIZE(mt6397_devs), NULL,
-					   0, NULL);
+					   0, pmic->irq_domain);
 		break;
 
 	default:
diff --git a/drivers/rtc/rtc-mt6397.c b/drivers/rtc/rtc-mt6397.c
index 1a61fa5..385f830 100644
--- a/drivers/rtc/rtc-mt6397.c
+++ b/drivers/rtc/rtc-mt6397.c
@@ -322,10 +322,9 @@ static int mtk_rtc_probe(struct platform_device *pdev)
 	res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
 	rtc->addr_base = res->start;
 
-	res = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
-	rtc->irq = irq_create_mapping(mt6397_chip->irq_domain, res->start);
-	if (rtc->irq <= 0)
-		return -EINVAL;
+	rtc->irq = platform_get_irq(pdev, 0);
+	if (rtc->irq < 0)
+		return rtc->irq;
 
 	rtc->regmap = mt6397_chip->regmap;
 	rtc->dev = &pdev->dev;
-- 
1.7.9.5

  reply	other threads:[~2017-09-27 10:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 10:44 [PATCH v5 0/6] Add MediaTek PMIC keys support Chen Zhong
2017-09-27 10:44 ` Chen Zhong [this message]
2017-09-27 10:44 ` [PATCH v5 2/6] dt-bindings: input: Add common keyboard document bindings Chen Zhong
2017-10-05 22:22   ` Rob Herring
2017-09-27 10:44 ` [PATCH v5 3/6] dt-bindings: input: Add document bindings for mtk-pmic-keys Chen Zhong
2017-10-05 22:23   ` Rob Herring
2017-09-27 10:44 ` [PATCH v5 4/6] dt-bindings: mfd: Add bindings for the keys as subnode of PMIC Chen Zhong
2017-09-27 10:44 ` [PATCH v5 5/6] input: Add MediaTek PMIC keys support Chen Zhong
2017-10-24  1:27   ` Chen Zhong
2017-10-24  5:44   ` Dmitry Torokhov
2017-10-24  9:37     ` Chen Zhong
2017-10-24 19:16       ` Dmitry Torokhov
2017-10-26  8:27   ` Andi Shyti
2017-09-27 10:44 ` [PATCH v5 6/6] mfd: mt6397: Add PMIC keys support to MT6397 driver Chen Zhong

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=1506509048-19032-2-git-send-email-chen.zhong@mediatek.com \
    --to=chen.zhong@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).