From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.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, Frank.Li@nxp.com,
wsa+renesas@sang-engineering.com, alok.a.tiwari@oracle.com
Cc: andersson@kernel.org, konradybcio@kernel.org
Subject: Re: [PATCH v6 1/3] dt-bindings: i3c: Add support for Qualcomm I3C controller
Date: Tue, 1 Jul 2025 10:58:02 +0200 [thread overview]
Message-ID: <ef9a18f8-4e71-4ed4-87d5-d5f175b60a25@kernel.org> (raw)
In-Reply-To: <20250701071852.2107800-2-mukesh.savaliya@oss.qualcomm.com>
On 01/07/2025 09:18, Mukesh Kumar Savaliya wrote:
> Add device tree bindings for the Qualcomm I3C controller. This includes
> the necessary documentation and properties required to describe the
> hardware in the device tree.
Last sentence is completely redundant. How would you add bindings
without necessary documentation? Does it make any sense to add bindings
without neccesary documentation and properties? No, it does not. Say
something useful or keep it simple. And I reject patches created to meet
KPIs/goals like amount of lines of patches (second pattern: other patch
was for IPQ5424 where I asked to shorten and qualcomm kept it two lines...).
> +maintainers:
> + - Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>
> +
> +description:
> + I3C in master mode supports up to 12.5MHz, SDR mode data transfer in mixed
> + bus mode (I2C and I3C target devices on same i3c bus). It also supports
> + hotjoin, IBI mechanism.
> +
> + I3C Controller nodes must be child of GENI based Qualcomm Universal
> + Peripharal. Please refer GENI based QUP wrapper controller node bindings
> + described in Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml.
Your cover letter - or this changelog - should explain what is your plan
in updating that one.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-01 8:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 7:18 [PATCH v6 0/3] Add Qualcomm i3c controller driver support Mukesh Kumar Savaliya
2025-07-01 7:18 ` [PATCH v6 1/3] dt-bindings: i3c: Add support for Qualcomm I3C controller Mukesh Kumar Savaliya
2025-07-01 8:30 ` Rob Herring (Arm)
2025-07-01 8:33 ` Krzysztof Kozlowski
2025-07-01 8:53 ` ALOK TIWARI
2025-07-01 8:58 ` Krzysztof Kozlowski [this message]
2025-07-17 20:51 ` Konrad Dybcio
2025-07-01 7:18 ` [PATCH v6 2/3] i3c: master: Add Qualcomm I3C controller driver Mukesh Kumar Savaliya
2025-07-01 8:43 ` Krzysztof Kozlowski
2025-07-01 8:48 ` ALOK TIWARI
2025-07-01 16:40 ` Frank Li
2025-07-01 20:56 ` Bjorn Andersson
2025-07-01 7:18 ` [PATCH v6 3/3] MAINTAINERS: Add maintainer for Qualcomm's " 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=ef9a18f8-4e71-4ed4-87d5-d5f175b60a25@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alok.a.tiwari@oracle.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=mukesh.savaliya@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.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).