From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jaewon Kim <jaewon02.kim@samsung.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Tomasz Figa <tomasz.figa@gmail.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Linus Walleij <linus.walleij@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-pwm@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v2 10/12] pinctrl: samsung: add exynosautov920 pinctrl
Date: Wed, 15 Nov 2023 13:28:45 +0100 [thread overview]
Message-ID: <62b7176d-f99c-49f6-a287-17a6b3604c1c@linaro.org> (raw)
In-Reply-To: <20231115095609.39883-11-jaewon02.kim@samsung.com>
On 15/11/2023 10:56, Jaewon Kim wrote:
> ExynosAutov920 GPIO has a different register structure.
> In the existing Exynos series, EINT control register enumerated after
> a specific offset (e.g EXYNOS_GPIO_ECON_OFFSET).
> However, in ExynosAutov920 SoC, the register that controls EINT belongs
> to each GPIO group, and each GPIO group has 0x1000 align.
>
> This is a structure to protect the GPIO group with S2MPU in VM environment,
> and will only be applied in ExynosAuto series SoCs.
>
> Example)
> -------------------------------------------------
> | original | ExynosAutov920 |
> |-----------------------------------------------|
> | 0x0 GPIO_CON | 0x0 GPIO_CON |
> | 0x4 GPIO_DAT | 0x4 GPIO_DAT |
> | 0x8 GPIO_PUD | 0x8 GPIO_PUD |
> | 0xc GPIO_DRV | 0xc GPIO_DRV |
> | 0x700 EINT_CON | 0x18 EINT_CON |
> | 0x800 EINT_FLTCON | 0x1c EINT_FLTCON0 |
> | 0x900 EINT_MASK | 0x20 EINT_FLTCON1 |
> | 0xa00 EINT_PEND | 0x24 EINT_MASK |
> | | 0x28 EINT_PEND |
> -------------------------------------------------
>
> Pinctrl data for ExynosAutoV920 SoC.
> - GPA0,GPA1 (10): External wake up interrupt
> - GPQ0 (2): SPMI (PMIC I/F)
> - GPB0,GPB1,GPB2,GPB3,GPB4,GPB5,GPB6 (47): I2S Audio
> - GPH0,GPH1,GPH2,GPH3,GPH4,GPH5,GPH6,GPH8 (49): PCIE, UFS, Ethernet
> - GPG0,GPG1,GPG2,GPG3,GPG4,GPG5 (29): General purpose
> - GPP0,GPP1,GPP2,GPP3,GPP4,GPP5,GPP6,GPP7,GPP8,GPP9,GPP10 (77): USI
>
> Signed-off-by: Jaewon Kim <jaewon02.kim@samsung.com>
> ---
> .../pinctrl/samsung/pinctrl-exynos-arm64.c | 140 ++++++++++++++++++
> drivers/pinctrl/samsung/pinctrl-exynos.c | 102 ++++++++++++-
> drivers/pinctrl/samsung/pinctrl-exynos.h | 27 ++++
> drivers/pinctrl/samsung/pinctrl-samsung.c | 5 +
> drivers/pinctrl/samsung/pinctrl-samsung.h | 13 ++
> 5 files changed, 280 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/pinctrl/samsung/pinctrl-exynos-arm64.c b/drivers/pinctrl/samsung/pinctrl-exynos-arm64.c
> index cb965cf93705..cf86722a70a3 100644
> --- a/drivers/pinctrl/samsung/pinctrl-exynos-arm64.c
> +++ b/drivers/pinctrl/samsung/pinctrl-exynos-arm64.c
> @@ -796,3 +796,143 @@ const struct samsung_pinctrl_of_match_data fsd_of_data __initconst = {
> .ctrl = fsd_pin_ctrl,
> .num_ctrl = ARRAY_SIZE(fsd_pin_ctrl),
> };
> +
> +/* pin banks of exynosautov920 pin-controller 0 (ALIVE) */
> +static struct samsung_pin_bank_data exynosautov920_pin_banks0[] = {
So you created patch from some downstream code? No, please work on
upstream. Take upstream code and customize it to your needs. That way
you won't introduce same mistakes fixes years ago.
Missing const.
...
> @@ -31,6 +31,7 @@
> #define EXYNOS7_WKUP_EMASK_OFFSET 0x900
> #define EXYNOS7_WKUP_EPEND_OFFSET 0xA00
> #define EXYNOS_SVC_OFFSET 0xB08
> +#define EXYNOSAUTOV920_SVC_OFFSET 0xF008
>
...
> #ifdef CONFIG_PINCTRL_S3C64XX
> { .compatible = "samsung,s3c64xx-pinctrl",
> diff --git a/drivers/pinctrl/samsung/pinctrl-samsung.h b/drivers/pinctrl/samsung/pinctrl-samsung.h
> index 9b3db50adef3..cbb78178651b 100644
> --- a/drivers/pinctrl/samsung/pinctrl-samsung.h
> +++ b/drivers/pinctrl/samsung/pinctrl-samsung.h
> @@ -122,6 +122,9 @@ struct samsung_pin_bank_type {
> * @eint_type: type of the external interrupt supported by the bank.
> * @eint_mask: bit mask of pins which support EINT function.
> * @eint_offset: SoC-specific EINT register or interrupt offset of bank.
> + * @mask_offset: SoC-specific EINT mask register offset of bank.
> + * @pend_offset: SoC-specific EINT pend register offset of bank.
> + * @combine: EINT register is adjacent to the GPIO control register.
I don't understand it. Adjacent? Are you sure? GPIO control register has
0xF004 (EXYNOSAUTOV920_SVC_OFFSET + 0x4)? Anyway, this does not scale.
What if next revision comes with not-adjacent. There will be
"combine_plus"? Also name confuses me - combine means together.
Also your first map of registers does not have it adjacent...
Anyway first patch is to rework driver to support new register layout.
Second patch is to add new variant.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-15 12:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231115095852epcas2p21e067efe75275c6abd2aebf04c5c6166@epcas2p2.samsung.com>
2023-11-15 9:55 ` [PATCH v2 00/12] Introduce ExynosAutov920 SoC and SADK board Jaewon Kim
[not found] ` <CGME20231115095853epcas2p3e808e27c4a5c611e7e1965f4c968cbcc@epcas2p3.samsung.com>
2023-11-15 9:55 ` [PATCH v2 01/12] dt-bindings: soc: samsung: exynos-sysreg: add exynosautov920 sysreg Jaewon Kim
[not found] ` <CGME20231115095853epcas2p45e2c5fe8ac771555a25b434cf86895fd@epcas2p4.samsung.com>
2023-11-15 9:55 ` [PATCH v2 02/12] dt-bindings: soc: samsung: exynos-pmu: add exynosautov920 compatible Jaewon Kim
[not found] ` <CGME20231115095853epcas2p38f9fbdd7bbbb940afa2042cd5ee9d237@epcas2p3.samsung.com>
2023-11-15 9:55 ` [PATCH v2 03/12] dt-bindings: soc: samsung: usi: add exynosautov920-usi compatible Jaewon Kim
[not found] ` <CGME20231115095854epcas2p2e48229f664c1de554f3ecf7075171b93@epcas2p2.samsung.com>
2023-11-15 9:56 ` [PATCH v2 04/12] dt-bindings: serial: samsung: add exynosautov920-uart compatible Jaewon Kim
[not found] ` <CGME20231115095854epcas2p42af0a20bcc4fb98aee818c7b44d77c31@epcas2p4.samsung.com>
2023-11-15 9:56 ` [PATCH v2 05/12] dt-bindings: pwm: samsung: add exynosautov920 compatible Jaewon Kim
[not found] ` <CGME20231115095854epcas2p457e0eedcd0b4a001eba8fba012f73920@epcas2p4.samsung.com>
2023-11-15 9:56 ` [PATCH v2 06/12] dt-bindings: pinctrl: samsung: add exynosautov920 binding Jaewon Kim
2023-11-15 12:44 ` (subset) " Krzysztof Kozlowski
[not found] ` <CGME20231115095855epcas2p41cfb2254bb7f5908612267ab254bb985@epcas2p4.samsung.com>
2023-11-15 9:56 ` [PATCH v2 07/12] dt-bindings: arm: samsung: Document exynosautov920 SADK board binding Jaewon Kim
[not found] ` <CGME20231115095855epcas2p3fb87cfdf820587174cc6b4d97e7f1b45@epcas2p3.samsung.com>
2023-11-15 9:56 ` [PATCH v2 08/12] dt-bindings: hwinfo: samsung,exynos-chipid: add exynosautov920 compatible Jaewon Kim
[not found] ` <CGME20231115095855epcas2p3fe5776db0e15e0427cbe2bd2382644c2@epcas2p3.samsung.com>
2023-11-15 9:56 ` [PATCH v2 09/12] soc: samsung: exynos-chipid: add exynosautov920 SoC support Jaewon Kim
[not found] ` <CGME20231115095856epcas2p1c3ee85750828bec2ee4ab0adeaeaff28@epcas2p1.samsung.com>
2023-11-15 9:56 ` [PATCH v2 10/12] pinctrl: samsung: add exynosautov920 pinctrl Jaewon Kim
2023-11-15 12:28 ` Krzysztof Kozlowski [this message]
2023-11-16 7:18 ` Jaewon Kim
[not found] ` <f0f6a7af-2170-89a2-1eea-dfb9d8440321@samsung.com>
2023-11-16 11:21 ` Krzysztof Kozlowski
2023-11-17 7:36 ` Jaewon Kim
2023-11-17 10:48 ` Krzysztof Kozlowski
2023-11-18 7:43 ` Jaewon Kim
2023-11-21 13:51 ` Krzysztof Kozlowski
2023-11-23 6:22 ` Jaewon Kim
2023-11-15 12:42 ` Krzysztof Kozlowski
2023-11-16 3:50 ` Jaewon Kim
2023-11-16 11:17 ` Krzysztof Kozlowski
2023-11-17 8:07 ` Jaewon Kim
[not found] ` <CGME20231115095856epcas2p473602f53ec35b5f3c57503b21b7ef406@epcas2p4.samsung.com>
2023-11-15 9:56 ` [PATCH v2 11/12] arm64: dts: exynos: add initial support for exynosautov920 SoC Jaewon Kim
[not found] ` <CGME20231115095856epcas2p189ef50d3e97656a92df6fef64414690c@epcas2p1.samsung.com>
2023-11-15 9:56 ` [PATCH v2 12/12] arm64: dts: exynos: add minimal support for exynosautov920 sadk board Jaewon Kim
2023-11-15 13:08 ` [PATCH v2 00/12] Introduce ExynosAutov920 SoC and SADK board Krzysztof Kozlowski
2023-11-15 21:11 ` Krzysztof Kozlowski
2023-11-15 21:17 ` Krzysztof Kozlowski
2023-11-16 3:32 ` Jaewon Kim
2023-11-16 7:56 ` Uwe Kleine-König
2023-11-16 7:59 ` Jaewon Kim
2023-11-16 11:17 ` Krzysztof Kozlowski
2023-11-17 7:19 ` Jaewon Kim
2023-11-17 10:57 ` Krzysztof Kozlowski
2023-11-17 11:00 ` Krzysztof Kozlowski
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=62b7176d-f99c-49f6-a287-17a6b3604c1c@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jaewon02.kim@samsung.com \
--cc=jirislaby@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-pwm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=thierry.reding@gmail.com \
--cc=tomasz.figa@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).