mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] arm64: dts: exynos2200: introduce serial busses, except spi
Date: Fri, 29 Aug 2025 12:55:35 +0200	[thread overview]
Message-ID: <51240b84-b063-4b99-b755-cc958192fef2@kernel.org> (raw)
In-Reply-To: <31435f98-5701-4ae0-b822-11a99d1b2eef@gmail.com>

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...

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.


> I wanted to upstream before merge cycle.

You should have posted them already. b4 handles dependencies, this
maintainer can read cover letters.

I plan to clear my todo queue this weekend and close my merge window
within two weeks due to travel.

Best regards,
Krzysztof

  reply	other threads:[~2025-08-29 10:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15  7:04 Ivaylo Ivanov
2025-08-15  7:04 ` [PATCH v3 1/4] arm64: dts: exynos2200: fix typo in hsi2c23 bus pins label Ivaylo Ivanov
2025-08-15  7:04 ` [PATCH v3 2/4] arm64: dts: exynos2200: use 32-bit address space for /soc Ivaylo Ivanov
2025-08-15  7:04 ` [PATCH v3 3/4] arm64: dts: exynos2200: increase the size of all syscons Ivaylo Ivanov
2025-08-16 17:26   ` Sam Protsenko
2025-08-15  7:05 ` [PATCH v3 4/4] arm64: dts: exynos2200: define all usi nodes Ivaylo Ivanov
2025-08-16 18:00   ` Sam Protsenko
2025-08-16 20:25     ` Ivaylo Ivanov
2025-08-16 17:29 ` [PATCH v3 0/4] arm64: dts: exynos2200: introduce serial busses, except spi Sam Protsenko
2025-08-16 17:35   ` Ivaylo Ivanov
2025-08-29 10:40 ` Ivaylo Ivanov
2025-08-29 10:55   ` Krzysztof Kozlowski [this message]
2025-08-29 11:04     ` Ivaylo Ivanov
2025-08-30  9:19 ` 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=51240b84-b063-4b99-b755-cc958192fef2@kernel.org \
    --to=krzk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ivo.ivanov.ivanov1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=robh@kernel.org \
    /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

all inboxes | Powered by JetHome®