From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: peter.griffin@linaro.org, krzysztof.kozlowski+dt@linaro.org,
gregkh@linuxfoundation.org, mturquette@baylibre.com,
sboyd@kernel.org, robh+dt@kernel.org, conor+dt@kernel.org,
andi.shyti@kernel.org, alim.akhtar@samsung.com,
jirislaby@kernel.org, s.nawrocki@samsung.com,
tomasz.figa@gmail.com, cw00.choi@samsung.com,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-serial@vger.kernel.org,
andre.draszik@linaro.org, kernel-team@android.com,
willmcvicker@google.com
Subject: Re: [PATCH v3 08/12] arm64: dts: exynos: gs101: remove reg-io-width from serial
Date: Wed, 17 Jan 2024 14:59:24 +0000 [thread overview]
Message-ID: <59a2e142-e970-4792-9233-7c447ac391b2@linaro.org> (raw)
In-Reply-To: <CAPLW+4mUMx9RvFiS0L2U+_Fd_PzcHhmNbyR4cmUrYF3BVgb=Cw@mail.gmail.com>
On 1/16/24 17:57, Sam Protsenko wrote:
> On Tue, Jan 9, 2024 at 7:00 AM Tudor Ambarus <tudor.ambarus@linaro.org> wrote:
>> Remove the reg-io-width property in order to comply with the bindings.
>>
>> The entire bus (PERIC) on which the GS101 serial resides only allows
>> 32-bit register accesses. The reg-io-width dt property is disallowed
>> for the "google,gs101-uart" compatible and instead the iotype is
>> inferred from the compatible.
>>
>> Reviewed-by: Peter Griffin <peter.griffin@linaro.org>
>> Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
>> ---
> Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org>
>
> Just out of curiosity (I probably missed the relevant discussion
> earlier): what is the actual reason for moving 'reg-io-width' to the
> driver's code as 'iotype'? I mean, what is the actual problem that's
The majority (if not all?) of the hardware blocks in GS101 SoC require
32 bit register access widths. Instead of specifying reg-io-width = 4
everywhere in the device tree, we infer it from the compatibles.
The relevant discussion is here:
https://lore.kernel.org/linux-arm-kernel/db368449-f446-47e8-81b6-a11c2a872306@linaro.org/
Cheers,
ta
> being solved by this -- is it to make the earlycon functional for
> gs101? I'm asking because the bus width looks like a part of HW
> description, which usually belongs to dts, from the design point of
> view. Anyways, that's not a concern, just trying to understand the
> decision.
next prev parent reply other threads:[~2024-01-17 14:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 12:58 [PATCH v3 00/12] GS101 Oriole: CMU_PERIC0 support and USI updates Tudor Ambarus
2024-01-09 12:58 ` [PATCH v3 01/12] dt-bindings: clock: google,gs101-clock: add PERIC0 clock management unit Tudor Ambarus
2024-01-16 15:50 ` Rob Herring
2024-01-09 12:58 ` [PATCH v3 02/12] dt-bindings: i2c: exynos5: add google,gs101-hsi2c compatible Tudor Ambarus
2024-01-10 8:02 ` Krzysztof Kozlowski
2024-01-09 12:58 ` [PATCH v3 03/12] dt-bindings: serial: samsung: do not allow reg-io-width for gs101 Tudor Ambarus
2024-01-10 8:06 ` Krzysztof Kozlowski
2024-01-10 9:04 ` Tudor Ambarus
2024-01-16 18:11 ` Sam Protsenko
2024-01-09 12:58 ` [PATCH v3 04/12] tty: serial: samsung: prepare for different IO types Tudor Ambarus
2024-01-10 8:07 ` Krzysztof Kozlowski
2024-01-16 17:50 ` Sam Protsenko
2024-01-09 12:58 ` [PATCH v3 05/12] tty: serial: samsung: set UPIO_MEM32 iotype for gs101 Tudor Ambarus
2024-01-10 8:08 ` Krzysztof Kozlowski
2024-01-16 18:10 ` Sam Protsenko
2024-01-09 12:58 ` [PATCH v3 06/12] tty: serial: samsung: add gs101 earlycon support Tudor Ambarus
2024-01-10 8:08 ` Krzysztof Kozlowski
2024-01-16 17:51 ` Sam Protsenko
2024-01-09 12:58 ` [PATCH v3 07/12] clk: samsung: gs101: add support for cmu_peric0 Tudor Ambarus
2024-01-16 17:42 ` Sam Protsenko
2024-01-17 14:49 ` Tudor Ambarus
2024-01-17 16:11 ` Sam Protsenko
2024-01-09 12:58 ` [PATCH v3 08/12] arm64: dts: exynos: gs101: remove reg-io-width from serial Tudor Ambarus
2024-01-16 17:57 ` Sam Protsenko
2024-01-17 14:59 ` Tudor Ambarus [this message]
2024-01-09 12:58 ` [PATCH v3 09/12] arm64: dts: exynos: gs101: enable cmu-peric0 clock controller Tudor Ambarus
2024-01-09 12:58 ` [PATCH v3 10/12] arm64: dts: exynos: gs101: update USI UART to use peric0 clocks Tudor Ambarus
2024-01-16 17:58 ` Sam Protsenko
2024-01-09 12:58 ` [PATCH v3 11/12] arm64: dts: exynos: gs101: define USI8 with I2C configuration Tudor Ambarus
2024-01-16 18:03 ` Sam Protsenko
2024-01-17 15:08 ` Tudor Ambarus
2024-01-17 16:12 ` Sam Protsenko
2024-01-09 12:58 ` [PATCH v3 12/12] arm64: dts: exynos: gs101: enable eeprom on gs101-oriole Tudor Ambarus
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=59a2e142-e970-4792-9233-7c447ac391b2@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peter.griffin@linaro.org \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tomasz.figa@gmail.com \
--cc=willmcvicker@google.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