From: Cristian Marussi <cristian.marussi@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org,
sudeep.holla@arm.com, james.quinlan@broadcom.com,
f.fainelli@gmail.com, vincent.guittot@linaro.org,
etienne.carriere@st.com, peng.fan@oss.nxp.com,
michal.simek@amd.com, quic_sibis@quicinc.com,
quic_nkela@quicinc.com, dan.carpenter@linaro.org,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH 3/5] dt-bindings: firmware: arm,scmi: Introduce more transport properties
Date: Fri, 18 Oct 2024 15:11:42 +0100 [thread overview]
Message-ID: <ZxJsnswE6bg6PsPu@pluto> (raw)
In-Reply-To: <20241018133725.GA77066-robh@kernel.org>
On Fri, Oct 18, 2024 at 08:37:25AM -0500, Rob Herring wrote:
> On Fri, Oct 18, 2024 at 09:06:00AM +0100, Cristian Marussi wrote:
> > Depending on specific hardware and firmware design choices, it may be
> > possible for different platforms to end up having different requirements
> > regarding the same transport characteristics.
> >
> > Introduce max-msg-size and max-msg properties to describe such platform
> > specific transport constraints, since they cannot be discovered otherwise.
> >
> > Cc: devicetree@vger.kernel.org
> > Cc: Rob Herring (Arm) <robh@kernel.org>
> > Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Also, you missed Conor and that not the right address for Krzysztof. Use
> get_maintainers.pl or a tool that uses it (b4).
>
> Also, no need to store maintainer addresses in the commit msg.
Ok, my bad I ahev not checked with the tool this time but just grabbed
from a recent commit log. I will fix in V2
Thanks,
Cristian
next prev parent reply other threads:[~2024-10-18 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 8:05 [PATCH 0/5] Expose SCMI Transport properties Cristian Marussi
2024-10-18 8:05 ` [PATCH 1/5] firmware: arm_scmi: Account for SHMEM memory overhead Cristian Marussi
2024-10-18 8:05 ` [PATCH 2/5] firmware: arm_scmi: Calculate virtio PDU max size dynamically Cristian Marussi
2024-10-18 8:06 ` [PATCH 3/5] dt-bindings: firmware: arm,scmi: Introduce more transport properties Cristian Marussi
2024-10-18 13:33 ` Rob Herring
2024-10-18 14:10 ` Cristian Marussi
2024-10-18 13:37 ` Rob Herring
2024-10-18 14:11 ` Cristian Marussi [this message]
2024-10-18 8:06 ` [PATCH 4/5] firmware: arm_scmi: Use max_msg and max_msg_size devicetree properties Cristian Marussi
2024-10-18 8:06 ` [PATCH 5/5] firmware: arm_scmi: Relocate atomic_threshold to scmi_desc Cristian Marussi
2024-10-23 13:20 ` Dan Carpenter
2024-10-25 14:35 ` Cristian Marussi
2024-10-25 14:53 ` Dan Carpenter
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=ZxJsnswE6bg6PsPu@pluto \
--to=cristian.marussi@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@st.com \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=peng.fan@oss.nxp.com \
--cc=quic_nkela@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).