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: Tue, 21 Nov 2023 14:51:21 +0100 [thread overview]
Message-ID: <8d4e3fcb-2e4a-4580-9aa2-5acbed961c3f@linaro.org> (raw)
In-Reply-To: <ab17d61e-f645-9b76-962c-4ba2849c5f42@samsung.com>
On 18/11/2023 08:43, Jaewon Kim wrote:
>
> On 23. 11. 17. 19:48, Krzysztof Kozlowski wrote:
>> On 17/11/2023 08:36, Jaewon Kim wrote:
>>>>> The reason why I chose variable name 'combine' is that EINT registers was
>>>>> separated from gpio control address. However, in exynosautov920 EINT
>>>>> registers combined with GPx group. So I chose "combine" word.
>>>> What does it mean "the GPx group"? Combined means the same place, the
>>>> same register. I could imagine offset is 0x4, what I wrote last time.
>>>>
>>>> Is the offset 0x4?
>
> If you are asking about the offset of GPIO control register and EINT
> control register, 0x4 is correct.
>
> There is no empty space between the two register.
>
>
> 0x0 CON
>
> 0x4 DAT
>
> 0x8 PUD
>
> 0xc DRV
>
> 0x10 CONPDN
>
> 0x14 PUDPDN
>
> 0x18 EINT_CON
>
> 0x1c EINT_FLTCON
>
> 0x20 or 0x24 EINT_MASK (The size of FLTCON register depending on the
> number of gpio)
>
> 0x24 or 0x28 EINT_PEND
>
>
>>>>
>>>>
>>>>> Is another reasonable word, I will change it.
>>>> Why you cannot store the offset?
>>>>
>>>>> EINT registers related to the entire group(e.g SVC) were at the end of
>>>>> the GPIO block and are now moved to 0xf000.
>>>> So not in the same register, not combined?
>>>>
>>> Okay,
>>>
>>> Instead of the word combine, I will think of a better word in next version.
>> I want to know answer to:
>>
>> "Why you cannot store the offset?"
>>
> I did not understand exactly what you said, but if i guess,,
>
> you want to get rid of the offs because the value of the offs is always
> the same?
>
> #define EXYNOSV920_PIN_BANK_EINTG(pins, reg, id, offs, mask_offs, pend_offs)
I meant that it looks possible to store the offset and use it directly,
instead of storing bool telling that offset is different.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-21 13:51 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
2023-11-15 9:55 ` [PATCH v2 01/12] dt-bindings: soc: samsung: exynos-sysreg: add exynosautov920 sysreg Jaewon Kim
2023-11-15 9:55 ` [PATCH v2 02/12] dt-bindings: soc: samsung: exynos-pmu: add exynosautov920 compatible Jaewon Kim
2023-11-15 9:55 ` [PATCH v2 03/12] dt-bindings: soc: samsung: usi: add exynosautov920-usi compatible Jaewon Kim
2023-11-15 9:56 ` [PATCH v2 04/12] dt-bindings: serial: samsung: add exynosautov920-uart compatible Jaewon Kim
2023-11-15 9:56 ` [PATCH v2 05/12] dt-bindings: pwm: samsung: add exynosautov920 compatible Jaewon Kim
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
2023-11-15 9:56 ` [PATCH v2 07/12] dt-bindings: arm: samsung: Document exynosautov920 SADK board binding Jaewon Kim
2023-11-15 9:56 ` [PATCH v2 08/12] dt-bindings: hwinfo: samsung,exynos-chipid: add exynosautov920 compatible Jaewon Kim
2023-11-15 9:56 ` [PATCH v2 09/12] soc: samsung: exynos-chipid: add exynosautov920 SoC support Jaewon Kim
2023-11-15 9:56 ` [PATCH v2 10/12] pinctrl: samsung: add exynosautov920 pinctrl Jaewon Kim
2023-11-15 12:28 ` Krzysztof Kozlowski
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 [this message]
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
2023-11-15 9:56 ` [PATCH v2 11/12] arm64: dts: exynos: add initial support for exynosautov920 SoC Jaewon Kim
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=8d4e3fcb-2e4a-4580-9aa2-5acbed961c3f@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