From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
alexandre.belloni@bootlin.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
jarkko.nikula@linux.intel.com, linux-i3c@lists.infradead.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: andersson@kernel.org, konradybcio@kernel.org
Subject: Re: [PATCH v4 0/3] Add Qualcomm i3c controller driver support
Date: Sat, 12 Apr 2025 01:20:39 +0200 [thread overview]
Message-ID: <eb6e8452-db37-47f7-9265-fd47d4cb69b8@oss.qualcomm.com> (raw)
In-Reply-To: <20250411113516.87958-1-quic_msavaliy@quicinc.com>
On 4/11/25 1:35 PM, Mukesh Kumar Savaliya wrote:
> This patchset adds i3c controller support for the qualcomm's QUPV3 based
> Serial engine (SE) hardware controller.
>
> The I3C SE(Serial Engine) controller implements I3C master functionality
> as defined in the MIPI Specifications for I3C, Version 1.0.
>
> This patchset was tested on Kailua SM8550 MTP device and data transfer
> has been tested in I3C SDR mode.
>
> Features tested and supported :
> Standard CCC commands.
> I3C SDR mode private transfers in PIO mode.
> I2C transfers in PIO mode.
>
> Signed-off-by: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
> ----
> Link to V3: https://lore.kernel.org/lkml/20250403134644.3935983-1-quic_msavaliy@quicinc.com/T/
> v3->v4:
> - Dropped "clock-names" property from dt-bindings as suggested by krzysztof.
> - Makefile: Correct order sequence for i3c-qcom-geni.c.
> - Indentation corrected around print statement.
> - geni_i3c_probe() : Exit with return 0 instead of ret for success.
> - Added sparse annotations around i3c_geni_runtime_get_mutex_lock()/_unlock().
So this is the third time I got this revision in my inbox, previous were
<20250410084813.3594436-1-quic_msavaliy@quicinc.com> 10.04
<20250331164648.2321899-1-quic_msavaliy@quicinc.com> 31.03
b4 should be automatically upticking the revision counter, please don't mess
with it manually
Konrad
next prev parent reply other threads:[~2025-04-11 23:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 11:35 [PATCH v4 0/3] Add Qualcomm i3c controller driver support Mukesh Kumar Savaliya
2025-04-11 11:35 ` [PATCH v4 1/3] dt-bindings: i3c: Add support for Qualcomm I3C controller Mukesh Kumar Savaliya
2025-04-11 20:30 ` Rob Herring (Arm)
2025-04-20 8:16 ` Mukesh Kumar Savaliya
2025-04-11 11:35 ` [PATCH v4 2/3] i3c: master: Add Qualcomm I3C controller driver Mukesh Kumar Savaliya
2025-04-11 23:15 ` Konrad Dybcio
2025-04-14 5:51 ` Mukesh Kumar Savaliya
2025-04-14 9:35 ` Konrad Dybcio
2025-04-14 8:53 ` Mukesh Kumar Savaliya
2025-04-14 10:08 ` Konrad Dybcio
2025-04-14 10:21 ` Mukesh Kumar Savaliya
2025-04-11 11:35 ` [PATCH v4 3/3] MAINTAINERS: Add maintainer for Qualcomm's " Mukesh Kumar Savaliya
2025-04-11 23:20 ` Konrad Dybcio [this message]
2025-04-13 7:28 ` [PATCH v4 0/3] Add Qualcomm i3c controller driver support Mukesh Kumar Savaliya
2025-04-14 9:18 ` Konrad Dybcio
2025-04-14 10:09 ` Mukesh Kumar Savaliya
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=eb6e8452-db37-47f7-9265-fd47d4cb69b8@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_msavaliy@quicinc.com \
--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