On Tue, May 9, 2017 at 3:28 PM, Sudeep Holla <sudeep.holla@xxxxxxx> wrote: >> >> If it is still not clear, please share your client driver. I will >> adapt that to work with existing MHU driver & bindings. >> > > Just take example of SCPI in the mainline. Assume there's another > protocol SCMI which uses few more bits in the same channel and the > remote firmware implements both but both are totally independent and not > related/linked. Also be keep in mind that SCPI is used by other > platforms and so will be the new protocol. We simply make SCPI or SCMI > bindings aligned to ARM MHU. That's ruled out. > Not sure what you mean by "that's ruled out". Anyways, to be clear, the bindings must remain same as long as the h/w doesn't change. It is the client driver (DT node) that should be versioned for SCPI or SCMI based on what the platform supports. I have tried many ways to explain how to implement it and apparently failed. So lets talk code. You have already shared this "v2" MHU driver, now please also share your client driver. I'll make it work with original MHU driver and that should settle your confusion. Thanks. -- 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
