linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mars Cheng <mars.cheng@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: CC Hwang <cc.hwang@mediatek.com>,
	Loda Chou <loda.chou@mediatek.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <wsd_upstream@mediatek.com>,
	Wendell Lin <wendell.lin@mediatek.com>,
	Ivan Tseng <ivan.tseng@mediatek.com>,
	Mars Cheng <mars.cheng@mediatek.com>
Subject: [PATCH 07/11] pinctrl: mediatek: add mt6779 eint support
Date: Mon, 5 Aug 2019 17:11:56 +0800	[thread overview]
Message-ID: <1564996320-10897-8-git-send-email-mars.cheng@mediatek.com> (raw)
In-Reply-To: <1564996320-10897-1-git-send-email-mars.cheng@mediatek.com>

add driver setting to support mt6779 eint

Signed-off-by: Mars Cheng <mars.cheng@mediatek.com>
---
 drivers/pinctrl/mediatek/pinctrl-mt6779.c |    8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/pinctrl/mediatek/pinctrl-mt6779.c b/drivers/pinctrl/mediatek/pinctrl-mt6779.c
index 145bf22..49ff3cc 100644
--- a/drivers/pinctrl/mediatek/pinctrl-mt6779.c
+++ b/drivers/pinctrl/mediatek/pinctrl-mt6779.c
@@ -731,11 +731,19 @@
 	"iocfg_rt", "iocfg_lt", "iocfg_tl",
 };
 
+static const struct mtk_eint_hw mt6779_eint_hw = {
+	.port_mask = 7,
+	.ports     = 6,
+	.ap_num    = 209,
+	.db_cnt    = 16,
+};
+
 static const struct mtk_pin_soc mt6779_data = {
 	.reg_cal = mt6779_reg_cals,
 	.pins = mtk_pins_mt6779,
 	.npins = ARRAY_SIZE(mtk_pins_mt6779),
 	.ngrps = ARRAY_SIZE(mtk_pins_mt6779),
+	.eint_hw = &mt6779_eint_hw,
 	.gpio_m = 0,
 	.ies_present = true,
 	.base_names = mt6779_pinctrl_register_base_names,
-- 
1.7.9.5


  parent reply	other threads:[~2019-08-05  9:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05  9:11 [PATCH 00/11] Add basic SoC Support for Mediatek MT6779 SoC Mars Cheng
2019-08-05  9:11 ` [PATCH 01/11] dt-bindings: mediatek: add support for mt6779 reference board Mars Cheng
2019-08-05 15:28   ` Rob Herring
2019-08-05  9:11 ` [PATCH 02/11] dt-bindings: mtk-uart: add mt6779 uart bindings Mars Cheng
2019-08-05  9:11 ` [PATCH 03/11] dt-bindings: irq: mtk,sysirq: add support for mt6779 Mars Cheng
2019-08-05  9:11 ` [PATCH 04/11] pinctrl: mediatek: update pinmux defintions " Mars Cheng
2019-08-21 18:50   ` Rob Herring
2019-08-22  0:43     ` Mars Cheng
2019-08-05  9:11 ` [PATCH 05/11] pinctrl: mediatek: avoid virtual gpio trying to set reg Mars Cheng
2019-08-05  9:11 ` [PATCH 06/11] pinctrl: mediatek: add pinctrl support for MT6779 SoC Mars Cheng
2019-08-05  9:11 ` Mars Cheng [this message]
2019-08-05  9:11 ` [PATCH 08/11] dt-bindings: mediatek: bindings for MT6779 clk Mars Cheng
2019-08-05  9:11 ` [PATCH 09/11] clk: mediatek: Add dt-bindings for MT6779 clocks Mars Cheng
2019-08-05  9:11 ` [PATCH 10/11] clk: mediatek: Add MT6779 clock support Mars Cheng
2019-08-05  9:12 ` [PATCH 11/11] arm64: dts: add dts nodes for MT6779 Mars Cheng

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=1564996320-10897-8-git-send-email-mars.cheng@mediatek.com \
    --to=mars.cheng@mediatek.com \
    --cc=cc.hwang@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ivan.tseng@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=loda.chou@mediatek.com \
    --cc=matthias.bgg@gmail.com \
    --cc=wendell.lin@mediatek.com \
    --cc=wsd_upstream@mediatek.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: 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).