From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Youngmin Nam'" <youngmin.nam@samsung.com>, <krzk@kernel.org>,
<s.nawrocki@samsung.com>, <linus.walleij@linaro.org>,
<peter.griffin@linaro.org>, <semen.protsenko@linaro.org>,
<ivo.ivanov.ivanov1@gmail.com>
Cc: <ryu.real@samsung.com>, <d7271.choe@samsung.com>,
<shin.son@samsung.com>, <jaewon02.kim@samsung.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3 1/5] pinctrl: samsung: Consolidate pin-bank macros under EXYNOS9_* and pass bank_type explicitly
Date: Wed, 17 Dec 2025 09:58:08 +0530 [thread overview]
Message-ID: <12a301dc6f0d$8fea7ec0$afbf7c40$@samsung.com> (raw)
In-Reply-To: <20251202093613.852109-2-youngmin.nam@samsung.com>
Hello Youngmin,
> -----Original Message-----
> From: Youngmin Nam <youngmin.nam@samsung.com>
> Sent: Tuesday, December 2, 2025 3:06 PM
> To: krzk@kernel.org; s.nawrocki@samsung.com; alim.akhtar@samsung.com;
> linus.walleij@linaro.org; peter.griffin@linaro.org;
> semen.protsenko@linaro.org; ivo.ivanov.ivanov1@gmail.com
> Cc: ryu.real@samsung.com; d7271.choe@samsung.com;
> shin.son@samsung.com; jaewon02.kim@samsung.com; linux-arm-
> kernel@lists.infradead.org; linux-samsung-soc@vger.kernel.org; linux-
> gpio@vger.kernel.org; linux-kernel@vger.kernel.org; Youngmin Nam
> <youngmin.nam@samsung.com>
> Subject: [PATCH v3 1/5] pinctrl: samsung: Consolidate pin-bank macros under
> EXYNOS9_* and pass bank_type explicitly
>
> Modern Exynos platforms have several near-duplicate pin-bank macro
> families (EXYNOS850_*, EXYNOS8895_*, EXYNOS7870_*), which makes
> tables verbose and harder to share across SoCs that differ only by
> bank_type (alive/off) layout.
>
> This patch unifies them into one EXYNOS9_* macro family and makes the
> bank_type an explicit argument. The common 850-era bank types are also
> renamed to 'exynos9_bank_type_{alive,off}' to reflect their reuse on
> later Exynos 9xxx-generation parts.
>
> Naming rationale:
> - Use of the EXYNOS9_* prefix indicates that these macros target
> current Exynos generations sharing the same register layout and
> EINT wiring model. Compared to SoC-specific prefixes
> (EXYNOS850_*, EXYNOS8895_*),
> EXYNOS9_* is clearer and more future-proof for modern parts.
>
> Key changes:
> - Introduce:
> - 'EXYNOS9_PIN_BANK_EINTN(bank_type, pins, reg, id)'
> - 'EXYNOS9_PIN_BANK_EINTG(bank_type, pins, reg, id, offs)'
> - 'EXYNOS9_PIN_BANK_EINTW(bank_type, pins, reg, id, offs)'
> - Rename:
> - 'exynos850_bank_type_alive'-> 'exynos9_bank_type_alive'
> - 'exynos850_bank_type_off' -> 'exynos9_bank_type_off'
> - Convert pin-bank tables for:
> - Exynos2200, 7870, 7885, 850, 990, 9810, 8890, 8895,
> AutoV9, AutoV920, FSD
> - Update GS101/EXYNOSV920 helpers to reference 'exynos9_bank_type_*'
> instead of the old exynos850 names.
> - Standardize on EXYNOS9_* macros while keeping SoC-specific
> '*_bank_type_*' when layouts differ (e.g., 7870/8895).
>
> No functional change intended.
>
> Signed-off-by: Youngmin Nam <youngmin.nam@samsung.com>
> Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org>
> Tested-by: Sam Protsenko <semen.protsenko@linaro.org>
> ---
Thanks for consolidating this.
Feel free to add
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
Also tested on SADK based on Exynosautov920, GPIO EINT works fine.
Tested-by: Alim Akhtar <alim.akhtar@samsung.com>
next prev parent reply other threads:[~2025-12-17 4:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251202093024epcas2p1567dddf09e3599867e9dc14a9a234d38@epcas2p1.samsung.com>
2025-12-02 9:36 ` [PATCH v3 0/5] pinctrl: samsung: exynos9 cleanups and fixes Youngmin Nam
[not found] ` <CGME20251202093026epcas2p28ddfd32305695df996841fd73b231b6b@epcas2p2.samsung.com>
2025-12-02 9:36 ` [PATCH v3 1/5] pinctrl: samsung: Consolidate pin-bank macros under EXYNOS9_* and pass bank_type explicitly Youngmin Nam
2025-12-17 4:28 ` Alim Akhtar [this message]
[not found] ` <CGME20251202093027epcas2p24adbd3226dd50b2780baceee6588f3ba@epcas2p2.samsung.com>
2025-12-02 9:36 ` [PATCH v3 2/5] pinctrl: samsung: fix incorrect pin-bank entries on Exynos2200/7885/8890/8895 Youngmin Nam
2025-12-17 4:33 ` Alim Akhtar
[not found] ` <CGME20251202093028epcas2p456b6a2bfebfc76384f706a9962266fcf@epcas2p4.samsung.com>
2025-12-02 9:36 ` [PATCH v3 3/5] pinctrl: samsung: add per-bank FLTCON offset to EXYNOS9_PIN_BANK_* and fix tables Youngmin Nam
2025-12-17 4:46 ` Alim Akhtar
[not found] ` <CGME20251202093028epcas2p1955176332d21ce4cadf7ed8894c5c1fa@epcas2p1.samsung.com>
2025-12-02 9:36 ` [PATCH v3 4/5] pinctrl: samsung: fold GS101 pin-bank macros into EXYNOS9_* Youngmin Nam
2025-12-17 4:43 ` Alim Akhtar
[not found] ` <CGME20251202093029epcas2p19224bab81f8ed2b9f63613fdd010ab57@epcas2p1.samsung.com>
2025-12-02 9:36 ` [PATCH v3 5/5] pinctrl: samsung: rename gs101_pinctrl_* to exynos9_pinctrl_* Youngmin Nam
2025-12-17 4:53 ` Alim Akhtar
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='12a301dc6f0d$8fea7ec0$afbf7c40$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=d7271.choe@samsung.com \
--cc=ivo.ivanov.ivanov1@gmail.com \
--cc=jaewon02.kim@samsung.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=ryu.real@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=semen.protsenko@linaro.org \
--cc=shin.son@samsung.com \
--cc=youngmin.nam@samsung.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).