U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek via U-Boot <u-boot@lists.u-boot-project.org>
To: "Maniyam, Dinesh" <dinesh.maniyam@altera.com>,
	Pranav Tilak <pranav.vinaytilak@amd.com>,
	u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Cc: git@amd.com, padmarao.begari@amd.com, u-boot@lists.u-boot-project.org
Subject: Re: [PATCH v2 0/4] i3c: dw: fix slave device setup and probe issues
Date: Wed, 22 Jul 2026 07:30:44 +0200	[thread overview]
Message-ID: <853abbc7-4f45-44f4-a935-64cebb4479e2@amd.com> (raw)
In-Reply-To: <d0788bac-8527-4236-91d0-476479a92fb3@altera.com>

Hi,

On 7/22/26 05:56, Maniyam, Dinesh wrote:
> Hi Michal Simek,
> 
> On 21/7/2026 4:07 pm, Michal Simek wrote:
>> [CAUTION: This email is from outside your organization. Unless you trust the sender, do not click on links or open attachments as it may be a fraudulent email attempting to steal your information and/or compromise your computer.]
>>
>> Hi Dinesh,
>>
>> On 7/9/26 11:12, Pranav Tilak wrote:
>>> This series fixes several issues in the DW I3C master driver and
>>> related infrastructure that prevented I3C read/write operations,
>>> and enables I3C support for Versal Gen 2.
>>>
>>> Changes in v2:
>>> - Use -ENOTSUPP instead of -EOPNOTSUPP as the reset stub in
>>>     include/reset.h returns -ENOTSUPP when CONFIG_DM_RESET=n
>>>
>>> Pranav Tilak (4):
>>>     i3c: dw: make resets optional in probe
>>>     cmd: i3c: fix list and current needing pre-selected controller
>>>     configs: versal2: enable I3C support
>>>     i3c: dw: fix slave device setup after DAA
>>>
>>>    cmd/i3c.c                          | 11 ++++++-----
>>>    configs/amd_versal2_virt_defconfig |  3 +++
>>>    drivers/i3c/master.c               |  1 -
>>>    drivers/i3c/master/dw-i3c-master.c |  7 ++++---
>>>    4 files changed, 13 insertions(+), 9 deletions(-)
>>>
>>
>> Dinesh: Can you please look at 1/4 and 4/4 patches?
>>
>> Thanks,
>> Michal
> 
> Reviewed. Thanks!

Thanks.

Tom: Are you going to take it directly? Or do you want me to collect it?
In patchwork it is assigned to you.

Thanks,
Michal

  reply	other threads:[~2026-07-22  5:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  9:12 [PATCH v2 0/4] i3c: dw: fix slave device setup and probe issues Pranav Tilak
2026-07-09  9:12 ` [PATCH v2 1/4] i3c: dw: make resets optional in probe Pranav Tilak
2026-07-22  2:51   ` Maniyam, Dinesh via U-Boot
2026-07-09  9:12 ` [PATCH v2 2/4] cmd: i3c: fix list and current needing pre-selected controller Pranav Tilak
2026-07-09  9:12 ` [PATCH v2 3/4] configs: versal2: enable I3C support Pranav Tilak
2026-07-09  9:12 ` [PATCH v2 4/4] i3c: dw: fix slave device setup after DAA Pranav Tilak
2026-07-22  3:54   ` Maniyam, Dinesh via U-Boot
2026-07-21  8:07 ` [PATCH v2 0/4] i3c: dw: fix slave device setup and probe issues Michal Simek via U-Boot
2026-07-22  3:56   ` Maniyam, Dinesh via U-Boot
2026-07-22  5:30     ` Michal Simek via U-Boot [this message]
2026-07-22 16:19       ` Tom Rini via U-Boot
2026-07-22 20:27 ` Tom Rini via U-Boot

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=853abbc7-4f45-44f4-a935-64cebb4479e2@amd.com \
    --to=u-boot@lists.u-boot-project.org \
    --cc=dinesh.maniyam@altera.com \
    --cc=git@amd.com \
    --cc=michal.simek@amd.com \
    --cc=padmarao.begari@amd.com \
    --cc=pranav.vinaytilak@amd.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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