linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: anup.patel@broadcom.com (Anup Patel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 16/17] dmaengine: bcm-sba-raid: Explicitly ACK mailbox message after sending
Date: Tue, 22 Aug 2017 15:27:05 +0530	[thread overview]
Message-ID: <1503395827-19428-17-git-send-email-anup.patel@broadcom.com> (raw)
In-Reply-To: <1503395827-19428-1-git-send-email-anup.patel@broadcom.com>

We should explicitly ACK mailbox message because after
sending message we can know the send status via error
attribute of brcm_message.

This will also help SBA-RAID to use "txdone_ack" method
whenever mailbox controller supports it.

Signed-off-by: Anup Patel <anup.patel@broadcom.com>
Reviewed-by: Ray Jui <ray.jui@broadcom.com>
---
 drivers/dma/bcm-sba-raid.c | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/drivers/dma/bcm-sba-raid.c b/drivers/dma/bcm-sba-raid.c
index 12310aa..0c41136 100644
--- a/drivers/dma/bcm-sba-raid.c
+++ b/drivers/dma/bcm-sba-raid.c
@@ -396,13 +396,17 @@ static int sba_send_mbox_request(struct sba_device *sba,
 		dev_err(sba->dev, "send message failed with error %d", ret);
 		return ret;
 	}
+
+	/* Check error returned by mailbox controller */
 	ret = req->msg.error;
 	if (ret < 0) {
 		dev_err(sba->dev, "message error %d", ret);
-		return ret;
 	}
 
-	return 0;
+	/* Signal txdone for mailbox channel */
+	mbox_client_txdone(sba->mchans[mchans_idx], ret);
+
+	return ret;
 }
 
 /* Note: Must be called with sba->reqs_lock held */
@@ -1724,7 +1728,7 @@ static int sba_probe(struct platform_device *pdev)
 	sba->client.dev			= &pdev->dev;
 	sba->client.rx_callback		= sba_receive_message;
 	sba->client.tx_block		= false;
-	sba->client.knows_txdone	= false;
+	sba->client.knows_txdone	= true;
 	sba->client.tx_tout		= 0;
 
 	/* Allocate mailbox channel array */
-- 
2.7.4

  parent reply	other threads:[~2017-08-22  9:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22  9:56 [PATCH v3 00/17] Broadcom SBA-RAID driver improvements Anup Patel
2017-08-22  9:56 ` [PATCH v3 01/17] dmaengine: bcm-sba-raid: Minor improvments in comments Anup Patel
2017-08-22  9:56 ` [PATCH v3 02/17] dmaengine: bcm-sba-raid: Reduce locking context in sba_alloc_request() Anup Patel
2017-08-22  9:56 ` [PATCH v3 03/17] dmaengine: bcm-sba-raid: Common flags for sba_request state and fence Anup Patel
2017-08-22  9:56 ` [PATCH v3 04/17] dmaengine: bcm-sba-raid: Remove redundant next_count from sba_request Anup Patel
2017-08-22  9:56 ` [PATCH v3 05/17] dmaengine: bcm-sba-raid: Remove redundant resp_dma " Anup Patel
2017-08-22  9:56 ` [PATCH v3 06/17] dmaengine: bcm-sba-raid: Remove reqs_free_count from sba_device Anup Patel
2017-08-22  9:56 ` [PATCH v3 07/17] dmaengine: bcm-sba-raid: Allow arbitrary number free sba_request Anup Patel
2017-08-22  9:56 ` [PATCH v3 08/17] dmaengine: bcm-sba-raid: Increase number of " Anup Patel
2017-08-22  9:56 ` [PATCH v3 09/17] dmaengine: bcm-sba-raid: Improve sba_issue_pending() run duration Anup Patel
2017-08-22  9:56 ` [PATCH v3 10/17] dmaengine: bcm-sba-raid: Alloc resources before registering DMA device Anup Patel
2017-08-22  9:57 ` [PATCH v3 11/17] dmaengine: bcm-sba-raid: Peek mbox when we have no free requests Anup Patel
2017-08-22  9:57 ` [PATCH v3 12/17] dmaengine: bcm-sba-raid: Pre-ack async tx descriptor Anup Patel
2017-08-22  9:57 ` [PATCH v3 13/17] dmaengine: bcm-sba-raid: Re-factor sba_process_deferred_requests() Anup Patel
2017-08-22  9:57 ` [PATCH v3 14/17] dmaengine: bcm-sba-raid: Remove redundant SBA_REQUEST_STATE_RECEIVED Anup Patel
2017-08-22  9:57 ` [PATCH v3 15/17] dmaengine: bcm-sba-raid: Add debugfs support Anup Patel
2017-08-22  9:57 ` Anup Patel [this message]
2017-08-22  9:57 ` [PATCH v3 17/17] dmaengine: bcm-sba-raid: Remove redundant SBA_REQUEST_STATE_COMPLETED Anup Patel
2017-08-28 11:14 ` [PATCH v3 00/17] Broadcom SBA-RAID driver improvements Vinod Koul

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1503395827-19428-17-git-send-email-anup.patel@broadcom.com \
    --to=anup.patel@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).