public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Welling <mwelling@ieee.org>
To: gnomes@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org, jslaby@suse.cz
Subject: Re: [PATCH 1/2] tty serial: xr17c15x driver
Date: Fri, 25 Apr 2014 01:22:13 -0500	[thread overview]
Message-ID: <20140425062213.GA2371@deathray> (raw)

I believe I found a related unresolved kernel bug:
"Bug 61961 – My Exar Corp. XR17C/D152 Dual PCI UART modem does not
work with 3.8.0"

The issue appears to be the same and gave me a clue as to where to
look.

Comparing the code from 3.5 to 3.8, I noticed that the UART_CAP_SLEEP
flag was added to the XR17D15X Exar chip.

Then I noticed what appears to be a bug in the serial8250_set_sleep
function:
.
.
        if ((p->port.type == PORT_XR17V35X) ||
           (p->port.type == PORT_XR17D15X)) {
                serial_out(p, UART_EXAR_SLEEP, 0xff);
                return;
        }
.
.

The if statement disregards the sleep parameter and always puts all of
the ports to sleep.

Something like this would be more appropriate:
.
.
        if ((p->port.type == PORT_XR17V35X) ||
           (p->port.type == PORT_XR17D15X)) {
                serial_out(p, UART_EXAR_SLEEP, sleep ? 0xff : 0);
                return;
        }
.
.

Now I don't know that this is the problem yet and I would like someone
to confirm that I am not crazy.

I can try the patch at work tomorrow and see if it fixes the issue.
Then maybe we can close Bug 61961.

             reply	other threads:[~2014-04-25  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  6:22 Michael Welling [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-10  4:04 [PATCH 1/2] tty serial: xr17c15x driver Michael Welling
2014-04-10  4:10 ` Michael Welling
2014-04-10 10:46   ` One Thousand Gnomes

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=20140425062213.GA2371@deathray \
    --to=mwelling@ieee.org \
    --cc=20140410114648.68bfbf61@alan.etchedpixels.co.uk \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@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