From: Sudeep Holla <sudeep.holla@arm.com>
To: Roy Franz <rfranz@cavium.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Roy Franz <roy.franz@cavium.com>,
Harb Abdulhamid <harba@codeaurora.org>,
Nishanth Menon <nm@ti.com>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [RFC PATCH 2/8] firmware: arm_scmi: add basic driver infrastructure for SCMI
Date: Thu, 8 Jun 2017 10:28:17 +0100 [thread overview]
Message-ID: <5310ae30-72b8-1dee-2b20-4759fad8b636@arm.com> (raw)
In-Reply-To: <CAKWsp+xR_1u2zrG=-dSzSktRvrr2Nfp50Hxur_YEFgr6oQ7KZQ@mail.gmail.com>
Hi Roy,
On 07/06/17 20:18, Roy Franz wrote:
> On Wed, Jun 7, 2017 at 9:10 AM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>> The SCMI is intended to allow OSPM to manage various functions that are
>> provided by the hardware platform it is running on, including power and
>> performance functions. SCMI provides two levels of abstraction, protocols
>> and transports. Protocols define individual groups of system control and
>> management messages. A protocol specification describes the messages
>> that it supports. Transports describe the method by which protocol
>> messages are communicated between agents and the platform.
>>
>> This patch adds basic infrastructure to manage the message allocation,
>> initialisation, packing/unpacking and shared memory management.
>>
>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>> ---
>> drivers/firmware/Kconfig | 21 ++
>> drivers/firmware/Makefile | 1 +
>> drivers/firmware/arm_scmi/Makefile | 2 +
>> drivers/firmware/arm_scmi/common.h | 74 ++++
>> drivers/firmware/arm_scmi/driver.c | 737 +++++++++++++++++++++++++++++++++++++
>> include/linux/scmi_protocol.h | 48 +++
>> 6 files changed, 883 insertions(+)
>> create mode 100644 drivers/firmware/arm_scmi/Makefile
>> create mode 100644 drivers/firmware/arm_scmi/common.h
>> create mode 100644 drivers/firmware/arm_scmi/driver.c
>> create mode 100644 include/linux/scmi_protocol.h
>>
[...]
>> +
>> +#define client_to_scmi_info(c) container_of(c, struct scmi_info, cl)
>> +#define handle_to_scmi_info(h) container_of(h, struct scmi_info, handle)
>> +
>> +/*
>> + * The SCP firmware only executes in little-endian mode, so any buffers
>> + * shared through SCMI should have their contents converted to little-endian
>> + */
>
> nit:
> This really has more to do with the SCMI protocol defining everything
> as little endian, rather the endian-ness of the SCP, right? There could be SCP
> implementations that are not Cortex M3s or little endian.
>
Thanks for taking time to review this RFC, much appreciated. All valid
points(on this and other patches) and fixed locally now. Also thanks for
saving time in debugging these issues. I should be able to do some
testing next week.
--
Regards,
Sudeep
next prev parent reply other threads:[~2017-06-08 9:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 16:10 [RFC PATCH 0/8] firmware: ARM System Control and Management Interface(SCMI) support Sudeep Holla
2017-06-07 16:10 ` [RFC PATCH 1/8] Documentation: add DT binding for ARM System Control and Management Interface(SCMI) protocol Sudeep Holla
2017-06-09 14:16 ` Rob Herring
2017-06-09 14:47 ` Sudeep Holla
2017-06-09 15:39 ` Rob Herring
2017-06-09 15:50 ` Sudeep Holla
[not found] ` <CAHCPf3s3MsiQyWFOgNJdD9F2JAwi_BVxVZG69zj+bJLzEw9AiA@mail.gmail.com>
2017-06-12 17:39 ` Sudeep Holla
2017-06-07 16:10 ` [RFC PATCH 2/8] firmware: arm_scmi: add basic driver infrastructure for SCMI Sudeep Holla
2017-06-07 19:18 ` Roy Franz
2017-06-08 9:28 ` Sudeep Holla [this message]
2017-06-07 16:10 ` [RFC PATCH 3/8] firmware: arm_scmi: add common infrastructure and support for base protocol Sudeep Holla
2017-06-07 19:19 ` Roy Franz
2017-06-07 16:10 ` [RFC PATCH 4/8] firmware: arm_scmi: add initial support for performance protocol Sudeep Holla
2017-06-07 16:10 ` [RFC PATCH 5/8] firmware: arm_scmi: add initial support for clock protocol Sudeep Holla
2017-06-07 19:19 ` Roy Franz
2017-06-07 16:10 ` [RFC PATCH 6/8] firmware: arm_scmi: add initial support for power protocol Sudeep Holla
2017-06-07 20:38 ` Arnd Bergmann
2017-06-08 9:39 ` Sudeep Holla
2017-06-08 11:06 ` Arnd Bergmann
2017-06-08 11:14 ` Sudeep Holla
2017-06-07 16:10 ` [RFC PATCH 7/8] firmware: arm_scmi: add initial support for sensor protocol Sudeep Holla
2017-06-07 19:19 ` Roy Franz
2017-06-07 16:10 ` [RFC PATCH 8/8] firmware: arm_scmi: probe and initialise all the supported protocols 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=5310ae30-72b8-1dee-2b20-4759fad8b636@arm.com \
--to=sudeep.holla@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=harba@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=rfranz@cavium.com \
--cc=roy.franz@cavium.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
all inboxes | Powered by JetHome®