On Mon, Jul 24, 2017 at 11:08 PM, Sudeep Holla <sudeep.holla@xxxxxxx> wrote: > On 24/07/17 18:20, Jassi Brar wrote: >> >>> I see that the SCPI firmware driver (as the user of the mailbox API) is >>> expecting the return value from a0 as returned above, translating the >>> firmware error codes into Linux' ones. >>> >> I am afraid, SCPI driver is not the golden example for client drivers >> to follow. It is supposed to work only with MHU, and then, it is >> likely to break if some other protocol is running parallel to it. >> > > Not sure why do you say it works only with ARM MHU ? AmLogic uses it > with their mailbox driver. However they followed an interim version of > the SCPI spec which is termed "legacy" in the driver. > Screw coding... Just tell me what stuff do you smoke? Must be really good! -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
