From: "André Draszik" <andre.draszik@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
peter.griffin@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
tudor.ambarus@linaro.org, willmcvicker@google.com,
semen.protsenko@linaro.org, alim.akhtar@samsung.com,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: exynos: gs101: add stable i2c aliases for gs101-oriole
Date: Mon, 12 Feb 2024 12:38:14 +0000 [thread overview]
Message-ID: <fbd335e81928c1c3cd63ee44514cf95a23dafb6f.camel@linaro.org> (raw)
In-Reply-To: <b6ec1d0e-e35c-4917-871b-049efcb2ea22@linaro.org>
On Mon, 2024-02-12 at 13:07 +0100, Krzysztof Kozlowski wrote:
> On 12/02/2024 12:52, André Draszik wrote:
> > As I said above, we won't care if downstream changes again at that stage, so
> > no, I wouldn't plan on changing again.
>
> Then I am lost. What stage are you thinking? What differs between now
> and let's say 1 month for the GS101 which was released more than three
> years ago?
The idea was to make the initial transition to using upstream easier,
hence we added the same aliases as downstream (at the time).
Given the transition is not happening right now, we might as well hold
off with the aliases and add them later, with whatever downstream will
be using at that time.
If in the future somebody downstream decides 'I want this' (changed again),
why should upstream care at that stage?
Again, this patch was just trying to make initial transition easier, do you
have a better recommendation?
> BTW, the aliases I see in downstream DTS (gs101-usi.dtsi) - since
> beginning up to Android 14 are:
>
> hsi2c8 = &hsi2c_8;
> hsi2c9 = &hsi2c_9;
> hsi2c10 = &hsi2c_10;
> hsi2c11 = &hsi2c_11;
> hsi2c12 = &hsi2c_12;
>
> They were set like this in 2020 and never changed afterwards.
Those were incorrect and didn't actually work as intended, here's a
better place to look:
https://android.googlesource.com/kernel/google-modules/raviole-device/+log/refs/heads/android-gs-raviole-mainline
and
https://android.googlesource.com/kernel/google-modules/raviole-device/+/9864593c894da90cd8b631ab57f15c25f4e11465%5E%21/
Cheers,
Andre'
next prev parent reply other threads:[~2024-02-12 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 23:37 [PATCH] arm64: dts: exynos: gs101: add stable i2c aliases for gs101-oriole André Draszik
2024-01-31 20:40 ` William McVicker
2024-02-08 8:08 ` Krzysztof Kozlowski
2024-02-12 10:17 ` André Draszik
2024-02-12 11:18 ` Krzysztof Kozlowski
2024-02-12 11:30 ` André Draszik
2024-02-12 11:40 ` Krzysztof Kozlowski
2024-02-12 11:52 ` André Draszik
2024-02-12 12:07 ` Krzysztof Kozlowski
2024-02-12 12:38 ` André Draszik [this message]
2024-02-12 13:20 ` Krzysztof Kozlowski
2024-02-12 13:22 ` 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=fbd335e81928c1c3cd63ee44514cf95a23dafb6f.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh+dt@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tudor.ambarus@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).