linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling]
Date: Wed, 14 Dec 2016 08:02:47 -0800	[thread overview]
Message-ID: <20161214160246.GA4920@atomide.com> (raw)
In-Reply-To: <20161214155208.ocs4vw77expduefr@earth>

* Sebastian Reichel <sre@kernel.org> [161214 07:52]:
> On Wed, Dec 14, 2016 at 07:10:56AM -0800, Tony Lindgren wrote:
> > Maybe send it so we can merge it as a fix during the early -rc
> > cycle?
> 
> Sorry if I was not clear enough: mainline does *not* contain
> incorrect DT information. My bluetooth RFC patches did. So
> this can go into the kernel once the driver is there and
> the binding got accepted.

Oh OK good to hear.

> Alternatively I can prepare a patch, which just adds the
> cts/rts pinmux for the bluetooth UART, but it's not very
> useful on its own.

OK sounds like no rush until other pieces are ready.

Regards,

Tony

      reply	other threads:[~2016-12-14 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161016002454.ul5rdqwubvkct4pf@earth>
     [not found] ` <20161016090959.GA377@amd>
     [not found]   ` <20161016173911.arxynrja6vely3d5@earth>
     [not found]     ` <20161017085137.GA6628@amd>
     [not found]       ` <20161018224259.jrwbaal27irzjqyo@earth>
2016-10-19  9:25         ` partial bluetooth success on n900 [was Re: bluetooth/uart timeout handling] Pavel Machek
2016-12-14 12:21           ` Pali Rohár
2016-12-14 12:53             ` Pavel Machek
2016-12-14 13:31               ` Sebastian Reichel
2016-12-14 15:10                 ` Tony Lindgren
2016-12-14 15:52                   ` Sebastian Reichel
2016-12-14 16:02                     ` Tony Lindgren [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=20161214160246.GA4920@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).