From: Vinod Koul <vkoul@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: dmaengine@vger.kernel.org, Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH v1] dmaengine: hsu: Revert "set HSU_CH_MTSR to memory width"
Date: Mon, 24 Jun 2019 17:30:02 +0530 [thread overview]
Message-ID: <20190624120002.GA2962@vkoul-mobl> (raw)
In-Reply-To: <20190613133232.49971-1-andriy.shevchenko@linux.intel.com>
On 13-06-19, 16:32, Andy Shevchenko wrote:
> The commit
>
> 080edf75d337 ("dmaengine: hsu: set HSU_CH_MTSR to memory width")
>
> has been mistakenly submitted. The further investigations show that
> the original code does better job since the memory side transfer size
> has never been configured by DMA users.
>
> As per latest revision of documentation: "Channel minimum transfer size
> (CHnMTSR)... For IOSF UART, maximum value that can be programmed is 64 and
> minimum value that can be programmed is 1."
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2019-06-24 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 13:32 [PATCH v1] dmaengine: hsu: Revert "set HSU_CH_MTSR to memory width" Andy Shevchenko
2019-06-24 12:00 ` Vinod Koul [this message]
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=20190624120002.GA2962@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.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).