[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <39eeddc1-99fb-092a-a833-cf4024695d87@arm.com>
Date: Mon, 24 Jul 2017 18:30:41 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Jassi Brar <jassisinghbrar@...il.com>
Cc: Sudeep Holla <sudeep.holla@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Rob Herring <robh@...nel.org>,
Alexey Klimov <alexey.klimov@....com>, Loc Ho <lho@....com>,
Mark Rutland <mark.rutland@....com>,
"arnd@...db.de" <arnd@...db.de>,
Jassi Brar <jaswinder.singh@...aro.org>,
Roy Franz <roy.franz@...ium.com>,
Harb Abdulhamid <harba@...eaurora.org>,
Matt Sealey <neko@...uhatsu.net>,
ALKML <linux-arm-kernel@...ts.infradead.org>,
DTML <devicetree@...r.kernel.org>, Nishanth Menon <nm@...com>
Subject: Re: [PATCH 3/9] firmware: arm_scmi: add basic driver infrastructure
for SCMI
On 24/07/17 18:21, Jassi Brar wrote:
> On Mon, Jul 24, 2017 at 9:51 PM, Sudeep Holla <sudeep.holla@....com> wrote:
>> On 24/07/17 16:41, Jassi Brar wrote:
>
>>> SCMI calls
>>> mbox_send_message(struct mbox_chan *chan, struct scmi_xfer *xfer);
>>>
>>> whereas the API expects
>>> mbox_send_message(struct mbox_chan *chan, struct controller_specific *xfer);
>>>
>>
>> That's not hard to change ...
>
> Cool, please change it and lets move on.
>
But tell me why first ? You said it needs to work with any controller.
And now you say I need to change it to some controller_specific ptr,
won't that make it controller specific protocol ?
You responded on something you wanted ignoring all the other parts,
still waiting for those response.
1. Tell me how my changes to MHU and SCMI are related ?
2. How my MHU changes and PCC are different ? Why do you think
this SCMI is FUBAR design which the clients using PCC are not ?
--
Regards,
Sudeep
Powered by blists - more mailing lists