From: Vinod Koul <vinod.koul@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Dan Williams" <dan.j.williams@intel.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
dmaengine@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hiroyuki Yokoyama" <hiroyuki.yokoyama.vx@renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v3] dmaengine: rcar-dmac: use TCRB instead of TCR for residue
Date: Wed, 8 Nov 2017 14:07:10 +0530 [thread overview]
Message-ID: <20171108083710.GP3187@localhost> (raw)
In-Reply-To: <87a7zxe18o.wl%kuninori.morimoto.gx@renesas.com>
On Wed, Nov 08, 2017 at 06:33:33AM +0000, Kuninori Morimoto wrote:
>
> Hi Vinod
>
> > > > > This is now commit 847449f23dcbff68 ("dmaengine: rcar-dmac: use TCRB
> > > > > instead of TCR for residue") in slave-dma/next, and breaks serial console
> > > > > input on koelsch (shmobile_defconfig) and salvator-x (renesas_defconfig).
> > > > > Reverting that commit fixes the issue for me.
> > >
> > > Okay since we are close to merge window I can drop this patch for now,
> > > unless we identify the fix very quickly
> >
> > I have not seen a resolution to this, so reverted it.
>
> We are sorry, but we still don't have solution about this.
thats okay, reverted seemed best in this situation. Once we have a solution
we can apply and mark to stable.
--
~Vinod
prev parent reply other threads:[~2017-11-08 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 1:15 [PATCH v3] dmaengine: rcar-dmac: use TCRB instead of TCR for residue Kuninori Morimoto
2017-10-19 7:41 ` Geert Uytterhoeven
2017-10-19 11:56 ` Laurent Pinchart
2017-10-20 6:15 ` Vinod Koul
2017-10-31 10:45 ` Geert Uytterhoeven
2017-10-31 10:46 ` Geert Uytterhoeven
2017-10-31 11:41 ` Vinod Koul
2017-11-01 3:07 ` Kuninori Morimoto
2017-11-06 1:24 ` Kuninori Morimoto
2017-11-06 13:27 ` Geert Uytterhoeven
2017-11-08 5:35 ` Vinod Koul
2017-11-08 6:33 ` Kuninori Morimoto
2017-11-08 8:37 ` 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=20171108083710.GP3187@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=hiroyuki.yokoyama.vx@renesas.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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).