From: Vinod Koul <vkoul@kernel.org>
To: Frank Mori Hess <fmh6jj@gmail.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
r.baldyga@hackerion.com, Krzysztof Kozlowski <krzk@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Linux Samsung SOC <linux-samsung-soc@vger.kernel.org>
Subject: Revert "dmaengine: pl330: add DMA_PAUSE feature"
Date: Wed, 23 May 2018 11:09:43 +0530 [thread overview]
Message-ID: <20180523053943.GB20991@vkoul-mobl> (raw)
On 22-05-18, 10:27, Frank Mori Hess wrote:
> On Mon, May 21, 2018 at 11:37 PM, Vinod Koul <vinod.koul@linaro.org> wrote:
> >
> > Well looks like even adding support for sync_pause doesn't solve your issue on
> > pl330. Do you want to move this to PIO mode then..?
The issue for which you requested the revert of pl330 pause
> I'm not sure what you think my issue is with the pl330, are you
> confusing me with Marek? My position is that pause is unsupported by
> the pl330 at the hardware level. Nothing the pl330.c driver or
> dmaengine api or 8250 serial driver does will change that. That is
> why I sent a patch to remove pause support from pl330.c. The rest is
> just trying to fix some bugs in mainline Linux I hit when I was a
> naive youngster who thought Linux support for the computer world's
> canonical serial uart could be counted on to move data from point A to
> point B. In truth though, I've already concluded it's not worth it to
> slog though the linux kernel development process just to clean up
> other people's messes. I've already fixed my issues out-of-tree. I
> don't mind answering questions if anyone else cares about the issue
> though. Other than that, I think I'll just be ghosting out now.
~Vinod
---
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-05-23 5:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 5:39 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-29 7:09 Revert "dmaengine: pl330: add DMA_PAUSE feature" Vinod Koul
2018-05-29 5:17 Marek Szyprowski
2018-05-22 14:27 Frank Mori Hess
2018-05-22 3:37 Vinod Koul
2018-05-22 0:56 Frank Mori Hess
2018-05-21 9:16 Vinod Koul
2018-05-18 19:01 Frank Mori Hess
2018-05-18 18:56 Frank Mori Hess
2018-05-18 7:21 Vinod Koul
2018-05-18 6:28 Marek Szyprowski
2018-05-18 4:03 Vinod Koul
2018-05-17 17:22 Lars-Peter Clausen
2018-05-17 16:20 Frank Mori Hess
2018-05-17 4:19 Vinod Koul
2018-05-15 15:50 Frank Mori Hess
2018-05-15 13:45 Vinod Koul
2018-05-15 12:24 Marek Szyprowski
2018-05-15 6:21 Vinod Koul
2018-05-11 15:57 Frank Mori Hess
2018-05-11 12:57 Marek Szyprowski
2018-05-10 16:04 Frank Mori Hess
2018-05-10 8:31 Marek Szyprowski
2018-05-09 17:48 Frank Mori Hess
2018-05-09 13:19 Marek Szyprowski
2018-05-09 6:59 Vinod Koul
2018-05-08 14:36 Frank Mori Hess
2018-05-08 9:04 Marek Szyprowski
2018-05-03 16:35 Vinod Koul
2018-05-03 9:01 Vinod Koul
2018-05-02 14:37 Frank Mori Hess
2018-05-02 4:32 Vinod Koul
2018-04-28 21:50 Frank Mori Hess
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=20180523053943.GB20991@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fmh6jj@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=r.baldyga@hackerion.com \
/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