Linux wireless drivers development
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Carlo Caione <carlo@endlessm.com>
Cc: Carlo Caione <carlo@caione.org>,
	johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
	frederic.danis.oss@gmail.com, sebastian.reichel@collabora.co.uk,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Linux Upstreaming Team <linux@endlessm.com>,
	Jeremy Cline <jcline@redhat.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [RFC PATCH 0/2] net: rfkill: gpio: Fix and support SerDev
Date: Tue, 20 Feb 2018 17:15:39 +0100	[thread overview]
Message-ID: <c1f7d6a5-7b31-e3e2-870c-ccc0dd2fca20@redhat.com> (raw)
In-Reply-To: <CAL9uMOEFm4apUrDxs6GkZqV2S=mepd2Ytcna+SCaLnCcwtcfeg@mail.gmail.com>

Hi,

On 02/20/2018 03:36 PM, Carlo Caione wrote:
> On Tue, Feb 20, 2018 at 2:01 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> Hi Carlo,
> 
> Hi Hans,
> 
>> Is this for devices with a RTL8723BS chip? If so then they
>> still will not work after this since there also no longer is
>> a /dev/ttyS4 created for the UART for the bluetooth, instead
>> you probably want:
>>
>> https://github.com/jwrdegoede/linux-sunxi/commit/c383dac5ea00738ac01d704d820aa548494fcd41
>>
>> Which also puts the /dev/ttyS4 back in place.
> 
> Yeah, this problem came up while working on the RTL8723BS chip but the
> driver is also broken for the other two GPS devices supported by this
> driver.
> Thank you for the patch BTW.
> 
>> Regards,
>>
>> Hans
>>
>> p.s.
>>
>> My college Jeremy Cline in the Cc is looking into getting proper
>> bluetooth support in place for the rtl8723bs using serdev binding
>> and having everything in the kernel, as we now already do for bcm
>> uart bluetooth modules.
> 
> Wasn't also Martin (+CC) working on this? See
> https://www.spinics.net/lists/linux-bluetooth/msg73594.html

Ah I did not know that, cool.  Jeremy, this is probably a good starting
point :)   And you should probably coordinate with Martin on this.

Regards,

Hans

  parent reply	other threads:[~2018-02-20 16:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 13:46 [RFC PATCH 0/2] net: rfkill: gpio: Fix and support SerDev Carlo Caione
2018-02-20 13:46 ` [RFC PATCH 1/2] net: rfkill: gpio: Fix NULL pointer deference Carlo Caione
2018-02-20 13:46 ` [RFC PATCH 2/2] net: rfkill: gpio: Convert driver to SerDev Carlo Caione
2018-02-20 14:04   ` Marcel Holtmann
2018-02-20 14:40     ` Carlo Caione
2018-02-20 14:01 ` [RFC PATCH 0/2] net: rfkill: gpio: Fix and support SerDev Hans de Goede
2018-02-20 14:10   ` Marcel Holtmann
2018-02-20 14:36   ` Carlo Caione
2018-02-20 15:55     ` Marcel Holtmann
2018-02-20 16:15     ` Hans de Goede [this message]
2018-02-20 20:26       ` Martin Blumenstingl
2018-02-20 21:18         ` Jeremy Cline
2018-02-20 21:34           ` Carlo Caione
2018-02-21  8:27             ` Marcel Holtmann
2018-02-21 15:35             ` Jeremy Cline
2018-02-21  8:26         ` Marcel Holtmann

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=c1f7d6a5-7b31-e3e2-870c-ccc0dd2fca20@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=carlo@caione.org \
    --cc=carlo@endlessm.com \
    --cc=frederic.danis.oss@gmail.com \
    --cc=jcline@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sebastian.reichel@collabora.co.uk \
    /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