Re: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs

2019-10-14 Thread Shawn Guo
On Mon, Oct 07, 2019 at 09:15:59AM +0800, Anson Huang wrote: > The SCU firmware does NOT always have return value stored in message > header's function element even the API has response data, those special > APIs are defined as void function in SCU firmware, so they should be > treated as return su

Re: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs

2019-10-09 Thread Marco Felsch
Hi Anson, On 19-10-09 09:09, Anson Huang wrote: > Hi, Marco > > > On 19-10-07 09:15, Anson Huang wrote: > > > The SCU firmware does NOT always have return value stored in message > > > header's function element even the API has response data, those > > > special APIs are defined as void function

RE: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs

2019-10-09 Thread Anson Huang
Hi, Marco > On 19-10-07 09:15, Anson Huang wrote: > > The SCU firmware does NOT always have return value stored in message > > header's function element even the API has response data, those > > special APIs are defined as void function in SCU firmware, so they > > should be treated as return succ

Re: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs

2019-10-09 Thread Marco Felsch
Hi Anson, On 19-10-07 09:15, Anson Huang wrote: > The SCU firmware does NOT always have return value stored in message > header's function element even the API has response data, those special > APIs are defined as void function in SCU firmware, so they should be > treated as return success always

Re: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs

2019-10-09 Thread Marco Felsch
On 19-10-09 08:28, Anson Huang wrote: > Hi, Marco > > > On 19-10-08 00:48, Anson Huang wrote: > > > Hi, Marco > > > > > > > On 19-10-07 09:15, Anson Huang wrote: > > > > > The SCU firmware does NOT always have return value stored in > > > > > message header's function element even the API has resp

RE: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs

2019-10-09 Thread Anson Huang
Hi, Marco > On 19-10-08 00:48, Anson Huang wrote: > > Hi, Marco > > > > > On 19-10-07 09:15, Anson Huang wrote: > > > > The SCU firmware does NOT always have return value stored in > > > > message header's function element even the API has response data, > > > > those special APIs are defined as v

Re: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs

2019-10-09 Thread Marco Felsch
Hi Anson, On 19-10-08 00:48, Anson Huang wrote: > Hi, Marco > > > On 19-10-07 09:15, Anson Huang wrote: > > > The SCU firmware does NOT always have return value stored in message > > > header's function element even the API has response data, those > > > special APIs are defined as void function

RE: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs

2019-10-07 Thread Anson Huang
Hi, Marco > On 19-10-07 09:15, Anson Huang wrote: > > The SCU firmware does NOT always have return value stored in message > > header's function element even the API has response data, those > > special APIs are defined as void function in SCU firmware, so they > > should be treated as return succ

Re: [PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs

2019-10-07 Thread Marco Felsch
Hi Anson, On 19-10-07 09:15, Anson Huang wrote: > The SCU firmware does NOT always have return value stored in message > header's function element even the API has response data, those special > APIs are defined as void function in SCU firmware, so they should be > treated as return success always

[PATCH V2] firmware: imx: Skip return value check for some special SCU firmware APIs

2019-10-06 Thread Anson Huang
The SCU firmware does NOT always have return value stored in message header's function element even the API has response data, those special APIs are defined as void function in SCU firmware, so they should be treated as return success always. Signed-off-by: Anson Huang --- Changes since V1: