From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tomoya MORINAGA <tomoya.rohm@gmail.com>
Cc: Alan Cox <alan@linux.intel.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
qi.wang@intel.com, yong.y.wang@intel.com, joel.clark@intel.com,
kok.howg.ewe@intel.com
Subject: Re: [PATCH] pch_uart: Fix dma channel unallocated issue
Date: Tue, 10 Apr 2012 07:41:10 -0700 [thread overview]
Message-ID: <20120410144110.GE14703@kroah.com> (raw)
In-Reply-To: <CANKRQniAUT232kGLY0PmHi_kmXdFWKeX6289qCXkSw6N179yTg@mail.gmail.com>
On Tue, Apr 10, 2012 at 10:26:25AM +0900, Tomoya MORINAGA wrote:
> On Tue, Apr 10, 2012 at 2:44 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >> This driver anticipates pch_uart_verify_port() is not called
> >> during installation.
> >> However, actually pch_uart_verify_port() is called during
> >> installation.
> >> As a result, memory access violation occurs like below.
> >>
> >> 0. initial value: use_dma=0
> >> 1. starup()
> >> - dma channel is not allocated because use_dma=0
> >> 2. pch_uart_verify_port()
> >> - Set use_dma=1
> >> 3. UART processing acts DMA mode because use_dma=1
> >> - memory access violation occurs!
> >>
> >> This patch fixes the issue.
> >>
> >> Solution:
> >> Whenever pch_uart_verify_port() is called and then
> >> dma channel is not allocated, the channel should be allocated.
> >>
> >> Signed-off-by: Tomoya MORINAGA <tomoya.rohm@gmail.com>
> >> ---
> >> drivers/tty/serial/pch_uart.c | 4 +++-
> >> 1 files changed, 3 insertions(+), 1 deletions(-)
> >
> > This patch does not apply to 3.4-rc2, so I can not apply it, sorry.
> >
> > Care to redo it?
>
> This patch depends on the following patch you've already accepted.
>
> >From 44db113212d86a5870c2bfe8fb767fa842d68805 Mon Sep 17 00:00:00 2001
> From: Tomoya MORINAGA <tomoya.rohm@gmail.com>
> Date: Mon, 26 Mar 2012 14:43:00 +0900
> Subject: pch_uart: Delete unused structure member
>
> Signed-off-by: Tomoya MORINAGA <tomoya.rohm@gmail.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> drivers/tty/serial/pch_uart.c | 2 --
> 1 file changed, 2 deletions(-)
>
>
> So now, this patch can be applied.
> In fact, I've confirmed this patch can be applied to 3.4-rc2 with the
> following order.
> 1st: pch_uart: Delete unused structure member
That patch is not applicable for the 3.4-release.
> 2nd: pch_uart: Fix dma channel unallocated issue
But I thought this one would be, which is why I did not try to apply
anything else before it.
> I should have written the dependency.
Yes, you always should.
> Could you try to apply this patch again ?
Don't you want this patch in the 3.4-final release? If so, I need it
without the dependancy.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-04-10 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 9:56 [PATCH] pch_uart: Fix dma channel unallocated issue Tomoya MORINAGA
2012-04-09 17:44 ` Greg Kroah-Hartman
2012-04-10 1:26 ` Tomoya MORINAGA
2012-04-10 14:41 ` Greg Kroah-Hartman [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=20120410144110.GE14703@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=tomoya.rohm@gmail.com \
--cc=yong.y.wang@intel.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;
as well as URLs for NNTP newsgroup(s).