Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755567AbcJFNKQ (ORCPT ); Thu, 6 Oct 2016 09:10:16 -0400 Received: from mail-qk0-f169.google.com ([209.85.220.169]:36096 "EHLO mail-qk0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755170AbcJFNKG (ORCPT ); Thu, 6 Oct 2016 09:10:06 -0400 MIME-Version: 1.0 In-Reply-To: <1475758897.4102.31.camel@mtksdaap41> References: <1473039885-24009-1-git-send-email-hs.liao@mediatek.com> <1473039885-24009-3-git-send-email-hs.liao@mediatek.com> <1475204778.13398.28.camel@mtksdaap41> <1475225778.25044.35.camel@mtksdaap41> <1475226691.13398.35.camel@mtksdaap41> <1475228829.3658.1.camel@mtksdaap41> <1475636064.21937.25.camel@mtksdaap41> <1475670705.335.27.camel@mtksdaap41> <1475758897.4102.31.camel@mtksdaap41> From: Jassi Brar Date: Thu, 6 Oct 2016 18:40:04 +0530 Message-ID: Subject: Re: [PATCH v14 2/4] CMDQ: Mediatek CMDQ driver To: Horng-Shyang Liao Cc: CK Hu , Daniel Kurtz , Monica Wang , Jiaguang Zhang , Nicolas Boichat , Jassi Brar , cawa cheng , Bibby Hsieh , YT Shen , Damon Chu , Devicetree List , Sascha Hauer , Daoyuan Huang , Sascha Hauer , Glory Hung , Rob Herring , linux-mediatek@lists.infradead.org, Matthias Brugger , "linux-arm-kernel@lists.infradead.org" , srv_heupstream@mediatek.com, Josh-YC Liu , lkml , Dennis-YC Hsieh , Philipp Zabel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 709 Lines: 13 On 6 October 2016 at 18:31, Horng-Shyang Liao wrote: > Back to our original statement, we need to flush all tasks to queue > in GCE HW; i.e. we need to use mbox_client_txdone after > mbox_send_message, or send tx_done once mailbox controller receive > message (task). However, we still need a way to notice done tasks to > clients. Currently, we don't have a good way to call callback in mailbox > framework. Therefore, CMDQ driver has its owner callback functions. > mbox_client_txdone() is called by the client driver when only it knows the messages has been transmitted (i.e your submitted tasks are done). Obviously the client driver should do any callbacks to its users upstream.