From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bjorn Andersson Subject: Re: [PATCH v4 3/5] soc: qcom: Introduce APCS IPC driver Date: Fri, 12 May 2017 15:48:40 -0700 Message-ID: <20170512224840.GW15143@minitux> References: <20170506011920.GH15143@minitux> <20170508055439.GJ15143@minitux> <20170508191154.GM15143@minitux> <20170509191106.GQ15143@minitux> <20170510190046.GT15143@minitux> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-arm-msm-owner@vger.kernel.org To: Jassi Brar Cc: Jeffrey Hugo , Andy Gross , Rob Herring , Mark Rutland , Ohad Ben-Cohen , linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, Devicetree List , Linux Kernel Mailing List , linux-remoteproc@vger.kernel.org List-Id: devicetree@vger.kernel.org On Wed 10 May 19:07 PDT 2017, Jassi Brar wrote: > On Thu, May 11, 2017 at 12:30 AM, Bjorn Andersson > wrote: > > On Tue 09 May 19:33 PDT 2017, Jassi Brar wrote: [..] > > So please let me know what you think about [1], if you don't like it > > I'll fix the things pointed to by Stephen and we'll have to live with > > the two calls. > > > My last reply was about [1]. Other platforms call > mbox_send_data()+mbox_client_txdone() see > drivers/firmware/tegra/bpmp.c, but you want to introduce another API > in the innards of the framework. Okay, lets go with that then. I will incorporate the changes requested by Stephen and post a final version and then add the mbox_client_txdone() in the clients. > If we must do it, it should be done > above the framework by introducing > > void mbox_send_message_and_tick(struct mbox_chan *chan, void *mssg) > OR > void mbox_ring_doorbell(struct mbox_chan *chan, void *mssg) > { > (void)mbox_send_message(chan, mssg); > mbox_client_txdone(chan, 0); > } This sounds reasonable, but I would prefer that we get the two drivers merged - so I suggest that we deal with that later, when we see if its worth the effort. Regards, Bjorn