linux-kernel - Re: [PATCH v3 0/4] arm64: dts: exynos2200: introduce serial busses, except spi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <7e14b195-f383-45ee-a6b1-6e71fc8fea86@gmail.com>
Date: Fri, 29 Aug 2025 14:04:12 +0300
From: Ivaylo Ivanov <ivo.ivanov.ivanov1@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Alim Akhtar <alim.akhtar@...sung.com>
Cc: linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/4] arm64: dts: exynos2200: introduce serial busses,
 except spi

On 8/29/25 13:55, Krzysztof Kozlowski wrote:
> On 29/08/2025 12:40, Ivaylo Ivanov wrote:
>> On 8/15/25 10:04, Ivaylo Ivanov wrote:
>>> Hey, folks!
>>>
>>> This patchset adds serial busses, implemented in usi, for exynos2200.
>>> It's missing spi, due to me having troubles with reads when testing.
>>> Serial_0/1 have not been included in the patchset, as it seems like
>>> they're encapsulated in usi blocks, but are the only implemented
>>> protocol and/or do not have a dedicated register for setting other
>>> protocols in a sysreg. That'd at least require patches in the usi
>>> driver and bindings to add support for.
>>>
>>> About the naming convention for usi nodes, I've chosen to keep the
>>> downstream one instead of relabelling all to avoid confusion when
>>> cross-referencing the vendor DT and to keep consistency with clock
>>> names. They're labelled the same in the bootloader too.
>> BUMP - when is this going to get merged? I had a few other things
> OSSE25...

Ah right, my bad.

>
> You can help out by reviewing other patches on the mailing lists in
> order to relieve the burden of maintainers and move your patches higher
> up the list.

Yeah, sure. I never really did reviews before because I felt like mine wouldn't
hold much weight. But sure, I certainly can (and will). Thanks for your work :D

>
>
>> I wanted to upstream before merge cycle.
> You should have posted them already. b4 handles dependencies, this
> maintainer can read cover letters.

Yeah. I do things via send-email still, so rebasing is a bit of a pain when I need to
change stuff in previous patches. And I don't do new branches per patchset,
my hardware isn't.. the best.

Best regards,
Ivaylo

>
> I plan to clear my todo queue this weekend and close my merge window
> within two weeks due to travel.
>
> Best regards,
> Krzysztof