From: Cristian Marussi <cristian.marussi@arm.com>
To: Nikunj Kela <quic_nkela@quicinc.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org,
devicetree@vger.kernel.org, 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,
dan.carpenter@linaro.org, souvik.chakravarty@arm.com,
robh@kernel.org, krzk+dt@kernel.org
Subject: Re: [PATCH v1 5/6] firmware: arm_scmi: Use max_msg and max_msg_size from devicetree
Date: Mon, 16 Sep 2024 15:14:08 +0100 [thread overview]
Message-ID: <Zug9MJj_3q0kSgAM@pluto> (raw)
In-Reply-To: <34d1783c-8b0d-4337-8169-1c41cd02a6e3@quicinc.com>
On Thu, Sep 12, 2024 at 12:22:48PM -0700, Nikunj Kela wrote:
>
> On 8/20/2024 7:48 AM, Sudeep Holla wrote:
> > On Tue, Jul 30, 2024 at 03:47:06PM +0100, Cristian Marussi wrote:
> >> Override max_msg and max_msg_size transport properties when corresponding
> >> devicetree properties are available.
> >>
> > I am holding off on these changes to think how these max_msg and max_msg_size
> > can be used without breaking any platforms allowing space for the header
> > and the message itself which is around 28 bytes. The binding itself looks
> > good. We may have to adjust the value passed to the core driver taking
> > the above into consideration.
> >
> > --
> > Regards,
> > Sudeep
>
Hi Nikunj,
these additional patches of initial series was still not reviewed by DT
maintainers really and it needed some rework for the reason Sudeep
mmentioned above. This is in my soon-ish todo list :P
Thanks,
Cristian
next prev parent reply other threads:[~2024-09-16 14:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 14:47 [PATCH v1 0/6] Add SCMI transport descriptors Cristian Marussi
2024-07-30 14:47 ` [PATCH v1 1/6] firmware: arm_scmi: Remove const from " Cristian Marussi
2024-07-30 14:47 ` [PATCH v1 2/6] dt-bindings: firmware: arm,scmi: Introduce property max-rx-timeout-ms Cristian Marussi
2024-07-30 14:47 ` [PATCH v1 3/6] firmware: arm_scmi: Use max-rx-timeout-ms from devicetree Cristian Marussi
2024-09-12 21:05 ` Florian Fainelli
2024-09-16 9:54 ` Cristian Marussi
2024-07-30 14:47 ` [PATCH v1 4/6] dt-bindings: firmware: arm,scmi: Introduce more transport properties Cristian Marussi
2024-07-30 14:47 ` [PATCH v1 5/6] firmware: arm_scmi: Use max_msg and max_msg_size from devicetree Cristian Marussi
2024-08-20 14:48 ` Sudeep Holla
2024-09-12 19:22 ` Nikunj Kela
2024-09-16 14:14 ` Cristian Marussi [this message]
2024-07-30 14:47 ` [PATCH v1 6/6] firmware: arm_scmi: Relocate atomic_threshold to scmi_desc Cristian Marussi
2024-07-31 13:13 ` [PATCH v1 0/6] Add SCMI transport descriptors Peng Fan
2024-07-31 13:58 ` Cristian Marussi
2024-08-01 19:17 ` Nikunj Kela
2024-08-01 19:23 ` Cristian Marussi
2024-08-01 19:44 ` Nikunj Kela
2024-08-20 14:39 ` Sudeep Holla
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=Zug9MJj_3q0kSgAM@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=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=robh@kernel.org \
--cc=souvik.chakravarty@arm.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