mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: quic_sibis@quicinc.com, Krzysztof Kozlowski <krzk+dt@kernel.org>,
	peng.fan@oss.nxp.com, devicetree@vger.kernel.org,
	Conor Dooley <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org, vincent.guittot@linaro.org,
	arm-scmi@vger.kernel.org, etienne.carriere@st.com,
	dan.carpenter@linaro.org, michal.simek@amd.com,
	sudeep.holla@arm.com, f.fainelli@gmail.com,
	james.quinlan@broadcom.com, quic_nkela@quicinc.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/5] dt-bindings: firmware: arm,scmi: Introduce more transport properties
Date: Thu, 24 Oct 2024 10:07:57 -0500	[thread overview]
Message-ID: <172978247557.479027.5212897770192282629.robh@kernel.org> (raw)
In-Reply-To: <20241021170726.2564329-4-cristian.marussi@arm.com>


On Mon, 21 Oct 2024 18:07:24 +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.
> 
> Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> ---
> Cc: Rob Herring <robh@kernel.org>
> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: devicetree@vger.kernel.org
> ---
> v1 --> v2
> - added vendor prefix
> - dropped warnings about resonable minimum max-msg-size
> - clarified the intended usage of max-msg
> - fixed Cc to include all maintainers and using correct e-mails
> ---
>  .../devicetree/bindings/firmware/arm,scmi.yaml    | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>


  reply	other threads:[~2024-10-24 15:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 17:07 [PATCH v2 0/5] Expose SCMI Transport properties Cristian Marussi
2024-10-21 17:07 ` [PATCH v2 1/5] firmware: arm_scmi: Account for SHMEM memory overhead Cristian Marussi
2024-10-21 17:11   ` Florian Fainelli
2024-10-22  9:18     ` Cristian Marussi
2024-10-21 17:07 ` [PATCH v2 2/5] firmware: arm_scmi: Calculate virtio PDU max size dynamically Cristian Marussi
2024-10-21 17:19   ` Florian Fainelli
2024-10-21 17:07 ` [PATCH v2 3/5] dt-bindings: firmware: arm,scmi: Introduce more transport properties Cristian Marussi
2024-10-24 15:07   ` Rob Herring (Arm) [this message]
2024-10-21 17:07 ` [PATCH v2 4/5] firmware: arm_scmi: Use max_msg and max_msg_size devicetree properties Cristian Marussi
2024-10-21 17:07 ` [PATCH v2 5/5] firmware: arm_scmi: Relocate atomic_threshold to scmi_desc Cristian Marussi

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=172978247557.479027.5212897770192282629.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=arm-scmi@vger.kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cristian.marussi@arm.com \
    --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=krzk+dt@kernel.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=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

all inboxes | Powered by JetHome®