[PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Laxman Dewangan]

In cyclic mode of DMA, the byte transferred can be more
than the requested size and in this case, calculating
residuals based on the current position of DMA transfer to
bytes requested i.e. bytes required to transfer to reach
bytes requested from current DMA position.

Signed-off-by: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
---
 drivers/dma/tegra20-apb-dma.c |   15 +++++++++------
 1 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/drivers/dma/tegra20-apb-dma.c b/drivers/dma/tegra20-apb-dma.c
index 340c617..d52dbc6 100644
--- a/drivers/dma/tegra20-apb-dma.c
+++ b/drivers/dma/tegra20-apb-dma.c
@@ -731,6 +731,7 @@ static enum dma_status tegra_dma_tx_status(struct dma_chan *dc,
 	struct tegra_dma_sg_req *sg_req;
 	enum dma_status ret;
 	unsigned long flags;
+	unsigned int residual;
 
 	spin_lock_irqsave(&tdc->lock, flags);
 
@@ -744,9 +745,10 @@ static enum dma_status tegra_dma_tx_status(struct dma_chan *dc,
 	/* Check on wait_ack desc status */
 	list_for_each_entry(dma_desc, &tdc->free_dma_desc, node) {
 		if (dma_desc->txd.cookie == cookie) {
-			dma_set_residue(txstate,
-				dma_desc->bytes_requested -
-				dma_desc->bytes_transferred);
+			residual =  dma_desc->bytes_requested -
+					(dma_desc->bytes_transferred %
+						dma_desc->bytes_requested);
+			dma_set_residue(txstate, residual);
 			ret = dma_desc->dma_status;
 			spin_unlock_irqrestore(&tdc->lock, flags);
 			return ret;
@@ -757,9 +759,10 @@ static enum dma_status tegra_dma_tx_status(struct dma_chan *dc,
 	list_for_each_entry(sg_req, &tdc->pending_sg_req, node) {
 		dma_desc = sg_req->dma_desc;
 		if (dma_desc->txd.cookie == cookie) {
-			dma_set_residue(txstate,
-				dma_desc->bytes_requested -
-				dma_desc->bytes_transferred);
+			residual =  dma_desc->bytes_requested -
+					(dma_desc->bytes_transferred %
+						dma_desc->bytes_requested);
+			dma_set_residue(txstate, residual);
 			ret = dma_desc->dma_status;
 			spin_unlock_irqrestore(&tdc->lock, flags);
 			return ret;
-- 
1.7.1.1

[PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Laxman Dewangan]

In cyclic mode of DMA, the byte transferred can be more
than the requested size and in this case, calculating
residuals based on the current position of DMA transfer to
bytes requested i.e. bytes required to transfer to reach
bytes requested from current DMA position.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
 drivers/dma/tegra20-apb-dma.c |   15 +++++++++------
 1 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/drivers/dma/tegra20-apb-dma.c b/drivers/dma/tegra20-apb-dma.c
index 340c617..d52dbc6 100644
--- a/drivers/dma/tegra20-apb-dma.c
+++ b/drivers/dma/tegra20-apb-dma.c
@@ -731,6 +731,7 @@ static enum dma_status tegra_dma_tx_status(struct dma_chan *dc,
 	struct tegra_dma_sg_req *sg_req;
 	enum dma_status ret;
 	unsigned long flags;
+	unsigned int residual;
 
 	spin_lock_irqsave(&tdc->lock, flags);
 
@@ -744,9 +745,10 @@ static enum dma_status tegra_dma_tx_status(struct dma_chan *dc,
 	/* Check on wait_ack desc status */
 	list_for_each_entry(dma_desc, &tdc->free_dma_desc, node) {
 		if (dma_desc->txd.cookie == cookie) {
-			dma_set_residue(txstate,
-				dma_desc->bytes_requested -
-				dma_desc->bytes_transferred);
+			residual =  dma_desc->bytes_requested -
+					(dma_desc->bytes_transferred %
+						dma_desc->bytes_requested);
+			dma_set_residue(txstate, residual);
 			ret = dma_desc->dma_status;
 			spin_unlock_irqrestore(&tdc->lock, flags);
 			return ret;
@@ -757,9 +759,10 @@ static enum dma_status tegra_dma_tx_status(struct dma_chan *dc,
 	list_for_each_entry(sg_req, &tdc->pending_sg_req, node) {
 		dma_desc = sg_req->dma_desc;
 		if (dma_desc->txd.cookie == cookie) {
-			dma_set_residue(txstate,
-				dma_desc->bytes_requested -
-				dma_desc->bytes_transferred);
+			residual =  dma_desc->bytes_requested -
+					(dma_desc->bytes_transferred %
+						dma_desc->bytes_requested);
+			dma_set_residue(txstate, residual);
 			ret = dma_desc->dma_status;
 			spin_unlock_irqrestore(&tdc->lock, flags);
 			return ret;
-- 
1.7.1.1

[PATCH 1/2] dma: tegra: rename driver and compatible to match with dts

[Laxman Dewangan]

Rename the compatible name and driver name to match with
tegra dts file and as per clock driver.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
 drivers/dma/tegra20-apb-dma.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/dma/tegra20-apb-dma.c b/drivers/dma/tegra20-apb-dma.c
index c0836a7..340c617 100644
--- a/drivers/dma/tegra20-apb-dma.c
+++ b/drivers/dma/tegra20-apb-dma.c
@@ -1177,10 +1177,10 @@ static struct tegra_dma_chip_data tegra30_dma_chip_data = {
 
 static const struct of_device_id tegra_dma_of_match[] __devinitconst = {
 	{
-		.compatible = "nvidia,tegra30-apbdma-new",
+		.compatible = "nvidia,tegra30-apbdma",
 		.data = &tegra30_dma_chip_data,
 	}, {
-		.compatible = "nvidia,tegra20-apbdma-new",
+		.compatible = "nvidia,tegra20-apbdma",
 		.data = &tegra20_dma_chip_data,
 	}, {
 	},
@@ -1395,7 +1395,7 @@ static const struct dev_pm_ops tegra_dma_dev_pm_ops __devinitconst = {
 
 static struct platform_driver tegra_dmac_driver = {
 	.driver = {
-		.name	= "tegra20-apbdma",
+		.name	= "tegra-apbdma",
 		.owner = THIS_MODULE,
 		.pm	= &tegra_dma_dev_pm_ops,
 		.of_match_table = of_match_ptr(tegra_dma_of_match),
-- 
1.7.1.1

[PATCH 1/2] dma: tegra: rename driver and compatible to match with dts

[Laxman Dewangan]

Rename the compatible name and driver name to match with
tegra dts file and as per clock driver.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
 drivers/dma/tegra20-apb-dma.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/dma/tegra20-apb-dma.c b/drivers/dma/tegra20-apb-dma.c
index c0836a7..340c617 100644
--- a/drivers/dma/tegra20-apb-dma.c
+++ b/drivers/dma/tegra20-apb-dma.c
@@ -1177,10 +1177,10 @@ static struct tegra_dma_chip_data tegra30_dma_chip_data = {
 
 static const struct of_device_id tegra_dma_of_match[] __devinitconst = {
 	{
-		.compatible = "nvidia,tegra30-apbdma-new",
+		.compatible = "nvidia,tegra30-apbdma",
 		.data = &tegra30_dma_chip_data,
 	}, {
-		.compatible = "nvidia,tegra20-apbdma-new",
+		.compatible = "nvidia,tegra20-apbdma",
 		.data = &tegra20_dma_chip_data,
 	}, {
 	},
@@ -1395,7 +1395,7 @@ static const struct dev_pm_ops tegra_dma_dev_pm_ops __devinitconst = {
 
 static struct platform_driver tegra_dmac_driver = {
 	.driver = {
-		.name	= "tegra20-apbdma",
+		.name	= "tegra-apbdma",
 		.owner = THIS_MODULE,
 		.pm	= &tegra_dma_dev_pm_ops,
 		.of_match_table = of_match_ptr(tegra_dma_of_match),
-- 
1.7.1.1

Re: [PATCH 1/2] dma: tegra: rename driver and compatible to match with dts

[Stephen Warren]

On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
> Rename the compatible name and driver name to match with
> tegra dts file and as per clock driver.
> 
> Signed-off-by: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

Acked-by: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

The separate config options for the old and new DMA drivers should
prevent them conflicting with each-other, even though they both support
the same compatible values and driver name. Hence, this patch should be
fine.

Re: [PATCH 1/2] dma: tegra: rename driver and compatible to match with dts

[Stephen Warren]

On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
> Rename the compatible name and driver name to match with
> tegra dts file and as per clock driver.
> 
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>

Acked-by: Stephen Warren <swarren@wwwdotorg.org>

The separate config options for the old and new DMA drivers should
prevent them conflicting with each-other, even though they both support
the same compatible values and driver name. Hence, this patch should be
fine.

Re: [PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Stephen Warren]

On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
> In cyclic mode of DMA, the byte transferred can be more
> than the requested size and in this case, calculating
> residuals based on the current position of DMA transfer to
> bytes requested i.e. bytes required to transfer to reach
> bytes requested from current DMA position.
> 
> Signed-off-by: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

This makes sense to me, although I wonder if details like this aren't
something that the dmaengine core should be handling.

Acked-by: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

Re: [PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Stephen Warren]

On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
> In cyclic mode of DMA, the byte transferred can be more
> than the requested size and in this case, calculating
> residuals based on the current position of DMA transfer to
> bytes requested i.e. bytes required to transfer to reach
> bytes requested from current DMA position.
> 
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>

This makes sense to me, although I wonder if details like this aren't
something that the dmaengine core should be handling.

Acked-by: Stephen Warren <swarren@wwwdotorg.org>

Re: [PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Vinod Koul]

On Mon, 2012-07-02 at 10:02 -0600, Stephen Warren wrote:
> On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
> > In cyclic mode of DMA, the byte transferred can be more
> > than the requested size and in this case, calculating
> > residuals based on the current position of DMA transfer to
> > bytes requested i.e. bytes required to transfer to reach
> > bytes requested from current DMA position.
> > 
> > Signed-off-by: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> 
> This makes sense to me, although I wonder if details like this aren't
> something that the dmaengine core should be handling.
No core doesn't know anything about the how much you are transferring
and where you are. That is the driver to calculate and provide.

-- 
~Vinod

Re: [PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Vinod Koul]

On Mon, 2012-07-02 at 10:02 -0600, Stephen Warren wrote:
> On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
> > In cyclic mode of DMA, the byte transferred can be more
> > than the requested size and in this case, calculating
> > residuals based on the current position of DMA transfer to
> > bytes requested i.e. bytes required to transfer to reach
> > bytes requested from current DMA position.
> > 
> > Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> 
> This makes sense to me, although I wonder if details like this aren't
> something that the dmaengine core should be handling.
No core doesn't know anything about the how much you are transferring
and where you are. That is the driver to calculate and provide.

-- 
~Vinod

Re: [PATCH 1/2] dma: tegra: rename driver and compatible to match with dts

[Vinod Koul]

On Mon, 2012-07-02 at 13:52 +0530, Laxman Dewangan wrote:
> Rename the compatible name and driver name to match with
> tegra dts file and as per clock driver.
> 
> Signed-off-by: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Applied both, Thanks

-- 
~Vinod

Re: [PATCH 1/2] dma: tegra: rename driver and compatible to match with dts

[Vinod Koul]

On Mon, 2012-07-02 at 13:52 +0530, Laxman Dewangan wrote:
> Rename the compatible name and driver name to match with
> tegra dts file and as per clock driver.
> 
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Applied both, Thanks

-- 
~Vinod

Re: [PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Laxman Dewangan]

On Friday 13 July 2012 08:45 AM, Vinod Koul wrote:
> On Mon, 2012-07-02 at 10:02 -0600, Stephen Warren wrote:
>> On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
>>> In cyclic mode of DMA, the byte transferred can be more
>>> than the requested size and in this case, calculating
>>> residuals based on the current position of DMA transfer to
>>> bytes requested i.e. bytes required to transfer to reach
>>> bytes requested from current DMA position.
>>>
>>> Signed-off-by: Laxman Dewangan<ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>> This makes sense to me, although I wonder if details like this aren't
>> something that the dmaengine core should be handling.
> No core doesn't know anything about the how much you are transferring
> and where you are. That is the driver to calculate and provide.

Just for confirmation, are you going to apply this patch or do I need to 
do anything here.

Thanks,
Laxman

Re: [PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Laxman Dewangan]

On Friday 13 July 2012 08:45 AM, Vinod Koul wrote:
> On Mon, 2012-07-02 at 10:02 -0600, Stephen Warren wrote:
>> On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
>>> In cyclic mode of DMA, the byte transferred can be more
>>> than the requested size and in this case, calculating
>>> residuals based on the current position of DMA transfer to
>>> bytes requested i.e. bytes required to transfer to reach
>>> bytes requested from current DMA position.
>>>
>>> Signed-off-by: Laxman Dewangan<ldewangan@nvidia.com>
>> This makes sense to me, although I wonder if details like this aren't
>> something that the dmaengine core should be handling.
> No core doesn't know anything about the how much you are transferring
> and where you are. That is the driver to calculate and provide.

Just for confirmation, are you going to apply this patch or do I need to 
do anything here.

Thanks,
Laxman

Re: [PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Vinod Koul]

On Fri, 2012-07-13 at 11:09 +0530, Laxman Dewangan wrote:
> On Friday 13 July 2012 08:45 AM, Vinod Koul wrote:
> > On Mon, 2012-07-02 at 10:02 -0600, Stephen Warren wrote:
> >> On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
> >>> In cyclic mode of DMA, the byte transferred can be more
> >>> than the requested size and in this case, calculating
> >>> residuals based on the current position of DMA transfer to
> >>> bytes requested i.e. bytes required to transfer to reach
> >>> bytes requested from current DMA position.
> >>>
> >>> Signed-off-by: Laxman Dewangan<ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> >> This makes sense to me, although I wonder if details like this aren't
> >> something that the dmaengine core should be handling.
> > No core doesn't know anything about the how much you are transferring
> > and where you are. That is the driver to calculate and provide.
> 
> Just for confirmation, are you going to apply this patch or do I need to 
> do anything here.
???

You didnt get my other mail about applying?

-- 
~Vinod

Re: [PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Vinod Koul]

On Fri, 2012-07-13 at 11:09 +0530, Laxman Dewangan wrote:
> On Friday 13 July 2012 08:45 AM, Vinod Koul wrote:
> > On Mon, 2012-07-02 at 10:02 -0600, Stephen Warren wrote:
> >> On 07/02/2012 02:22 AM, Laxman Dewangan wrote:
> >>> In cyclic mode of DMA, the byte transferred can be more
> >>> than the requested size and in this case, calculating
> >>> residuals based on the current position of DMA transfer to
> >>> bytes requested i.e. bytes required to transfer to reach
> >>> bytes requested from current DMA position.
> >>>
> >>> Signed-off-by: Laxman Dewangan<ldewangan@nvidia.com>
> >> This makes sense to me, although I wonder if details like this aren't
> >> something that the dmaengine core should be handling.
> > No core doesn't know anything about the how much you are transferring
> > and where you are. That is the driver to calculate and provide.
> 
> Just for confirmation, are you going to apply this patch or do I need to 
> do anything here.
???

You didnt get my other mail about applying?

-- 
~Vinod

Re: [PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Laxman Dewangan]

On Friday 13 July 2012 11:58 AM, Vinod Koul wrote:
> On Fri, 2012-07-13 at 11:09 +0530, Laxman Dewangan wrote:
> You didnt get my other mail about applying?
>

Read carefully now and saw both are applied.
Thanks for care.

Thanks,
Laxman

Re: [PATCH 2/2] dma: tegra: fix residual calculation for cyclic case

[Laxman Dewangan]

On Friday 13 July 2012 11:58 AM, Vinod Koul wrote:
> On Fri, 2012-07-13 at 11:09 +0530, Laxman Dewangan wrote:
> You didnt get my other mail about applying?
>

Read carefully now and saw both are applied.
Thanks for care.

Thanks,
Laxman