All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, shurd@broadcom.com, mchan@broadcom.com
Subject: Re: [PATCH] 8250/16?50: Add support for Broadcom TruManage redirected serial port
Date: Tue, 29 Jan 2013 07:18:18 -0800	[thread overview]
Message-ID: <20130129151818.GA2976@kroah.com> (raw)
In-Reply-To: <87ip6gm3kf.fsf@ashishki-desk.ger.corp.intel.com>

On Tue, Jan 29, 2013 at 05:06:24PM +0200, Alexander Shishkin wrote:
> Michael Chan <mchan@broadcom.com> writes:
> 
> > From: Stephen Hurd <shurd@broadcom.com>
> >
> > Add support for the UART device present in Broadcom TruManage capable
> > NetXtreme chips (ie: 5761m 5762, and 5725).
> >
> > This implementation has a hidden transmit FIFO, so running in single-byte
> > interrupt mode results in too many interrupts.  The UART_CAP_HFIFO
> > capability was added to track this.  It continues to reload the THR as long
> > as the THRE and TSRE bits are set in the LSR up to a specified limit (1024
> > is used here).
> >
> > Signed-off-by: Stephen Hurd <shurd@broadcom.com>
> > Signed-off-by: Michael Chan <mchan@broadcom.com>
> 
> Greg, this looks like a new feature, yet it was applied to -rc5 and
> stable. Any reason for that? I'm asking because this patch doesn't seem
> to have received enough reviewing/testing:
> 
> [skip platform bits]
> 
> > diff --git a/include/uapi/linux/serial_core.h b/include/uapi/linux/serial_core.h
> > index 78f99d9..2c6c85f 100644
> > --- a/include/uapi/linux/serial_core.h
> > +++ b/include/uapi/linux/serial_core.h
> > @@ -50,7 +50,8 @@
> >  #define PORT_LPC3220	22	/* NXP LPC32xx SoC "Standard" UART */
> >  #define PORT_8250_CIR	23	/* CIR infrared port, has its own driver */
> >  #define PORT_XR17V35X	24	/* Exar XR17V35x UARTs */
> > -#define PORT_MAX_8250	24	/* max port ID */
> > +#define PORT_BRCM_TRUMANAGE	24
> > +#define PORT_MAX_8250	25	/* max port ID */
> 
> This is a bug, TRUMANAGE should be 25 as well as PORT_MAX_8250.

Good catch, care to make up a patch to fix it?

thanks,

greg k-h

  reply	other threads:[~2013-01-29 15:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 22:14 [PATCH] 8250/16?50: Add support for Broadcom TruManage redirected serial port Michael Chan
2013-01-29 15:06 ` Alexander Shishkin
2013-01-29 15:18   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-12-12  1:11 Stephen Hurd
2012-12-12  4:45 ` gregkh
2012-12-12  5:28   ` Stephen Hurd
2013-01-16  6:59     ` gregkh
2013-01-16 21:49       ` Stephen Hurd
2012-12-12  0:32 Stephen Hurd

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=20130129151818.GA2976@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchan@broadcom.com \
    --cc=shurd@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.