All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Michael Williamson <michael.williamson@criticallink.com>,
	linux-serial@vger.kernel.org,
	"davinci-linux-open-source@linux.davincidsp.com"
	<davinci-linux-open-source@linux.davincidsp.com>
Subject: Re: Need to disable MSR interrupts in 8250 driver. Request for guidance...
Date: Mon, 3 Jan 2011 16:07:31 -0800	[thread overview]
Message-ID: <20110104000731.GA17841@suse.de> (raw)
In-Reply-To: <87pqsda6de.fsf@ti.com>

On Mon, Jan 03, 2011 at 03:56:45PM -0800, Kevin Hilman wrote:
> Michael Williamson <michael.williamson@criticallink.com> writes:
> 
> > I am working on platform from the davinci architecture that uses the 8520 UART
> > driver.  However, there are some configurations that do not have a valid
> > CTS input pin (it is a multi-purpose pin on a SoC part, and it may be configured
> > for other functions).  These configurations can cause a pile of "false" 
> > MSR interrupts.  If, in 8250.c, I set the UART_BUG_NOMSR flag as part of
> > the up->bugs information, the problem clears up.
> 
> [...]
> 
> > Should I create a new port type, add a new UPF_ flag in the flags field, figure 
> > out how to pass bugs information via platform data, or continue along the
> > work-around path?  
> 
> I added Greg KH to Cc as he's maintaining the 8250 core now.
> 
> IMO, adding UPF_ flag(s) to indicate this bug seems like the right way
> to go to me.

Yes, it sounds correct to me as well.

thanks,

greg k-h

      reply	other threads:[~2011-01-04  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 14:15 Need to disable MSR interrupts in 8250 driver. Request for guidance Michael Williamson
2011-01-03 23:56 ` Kevin Hilman
2011-01-04  0:07   ` Greg KH [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=20110104000731.GA17841@suse.de \
    --to=gregkh@suse.de \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=michael.williamson@criticallink.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.