Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1587933 > unrolled thread

Re: [PATCH] NFC: remove TI nfcwilink driver

Started byRob Herring <robh@kernel.org>
First post2017-02-24 22:00 +0100
Last post2017-02-27 11:40 +0100
Articles 4 — 3 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] NFC: remove TI nfcwilink driver Rob Herring <robh@kernel.org> - 2017-02-24 22:00 +0100
    Re: [PATCH] NFC: remove TI nfcwilink driver Marcel Holtmann <marcel@holtmann.org> - 2017-02-24 23:00 +0100
      Re: [PATCH] NFC: remove TI nfcwilink driver Rob Herring <robh@kernel.org> - 2017-02-24 23:00 +0100
    Re: [PATCH] NFC: remove TI nfcwilink driver Samuel Ortiz <sameo@linux.intel.com> - 2017-02-27 11:40 +0100

#1587933 — Re: [PATCH] NFC: remove TI nfcwilink driver

FromRob Herring <robh@kernel.org>
Date2017-02-24 22:00 +0100
SubjectRe: [PATCH] NFC: remove TI nfcwilink driver
Message-ID<tev85-5AX-1@gated-at.bofh.it>
On Wed, Jan 25, 2017 at 11:54 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Rob,
>
>> It appears that TI WiLink devices including NFC (WL185x/WL189x) never
>> shipped. The only information I found were announcements in Feb
>> 2012 about the parts. There's been no activity on this driver besided
>> common changes since initially added in Jan 2012. There's also no in
>> users that instantiate the platform device (nor DT bindings).
>>
>> This is a first step in removing TI ST (shared transport) driver in
>> favor of extending the BT hci_ll driver to support WL183x chips.
>
> since the firmware files TINfcInit_* also never made it into the linux-firmware tree, I have no idea who is using this driver. I am actually fine with removing it since it would be easy enough to bring back based on hci_ll driver once there is hardware to test this on.

Ping. Someone going to pick up this patch?

Rob

[toc] | [next] | [standalone]


#1587965

FromMarcel Holtmann <marcel@holtmann.org>
Date2017-02-24 23:00 +0100
Message-ID<tew49-6gV-9@gated-at.bofh.it>
In reply to#1587933
Hi Rob,

>>> It appears that TI WiLink devices including NFC (WL185x/WL189x) never
>>> shipped. The only information I found were announcements in Feb
>>> 2012 about the parts. There's been no activity on this driver besided
>>> common changes since initially added in Jan 2012. There's also no in
>>> users that instantiate the platform device (nor DT bindings).
>>> 
>>> This is a first step in removing TI ST (shared transport) driver in
>>> favor of extending the BT hci_ll driver to support WL183x chips.
>> 
>> since the firmware files TINfcInit_* also never made it into the linux-firmware tree, I have no idea who is using this driver. I am actually fine with removing it since it would be easy enough to bring back based on hci_ll driver once there is hardware to test this on.
> 
> Ping. Someone going to pick up this patch?

if Samuel does not have anything pending for his tree, I can take it through bluetooth-next tree.

Regards

Marcel

[toc] | [prev] | [next] | [standalone]


#1587968

FromRob Herring <robh@kernel.org>
Date2017-02-24 23:00 +0100
Message-ID<tew4a-6gV-13@gated-at.bofh.it>
In reply to#1587965
On Fri, Feb 24, 2017 at 3:43 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Rob,
>
>>>> It appears that TI WiLink devices including NFC (WL185x/WL189x) never
>>>> shipped. The only information I found were announcements in Feb
>>>> 2012 about the parts. There's been no activity on this driver besided
>>>> common changes since initially added in Jan 2012. There's also no in
>>>> users that instantiate the platform device (nor DT bindings).
>>>>
>>>> This is a first step in removing TI ST (shared transport) driver in
>>>> favor of extending the BT hci_ll driver to support WL183x chips.
>>>
>>> since the firmware files TINfcInit_* also never made it into the linux-firmware tree, I have no idea who is using this driver. I am actually fine with removing it since it would be easy enough to bring back based on hci_ll driver once there is hardware to test this on.
>>
>> Ping. Someone going to pick up this patch?
>
> if Samuel does not have anything pending for his tree, I can take it through bluetooth-next tree.

From the looks of -next, it doesn't appear so.

Rob

[toc] | [prev] | [next] | [standalone]


#1588593

FromSamuel Ortiz <sameo@linux.intel.com>
Date2017-02-27 11:40 +0100
Message-ID<tfqSK-4fZ-17@gated-at.bofh.it>
In reply to#1587933
Hi Rob,

On Fri, Feb 24, 2017 at 02:56:48PM -0600, Rob Herring wrote:
> On Wed, Jan 25, 2017 at 11:54 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> > Hi Rob,
> >
> >> It appears that TI WiLink devices including NFC (WL185x/WL189x) never
> >> shipped. The only information I found were announcements in Feb
> >> 2012 about the parts. There's been no activity on this driver besided
> >> common changes since initially added in Jan 2012. There's also no in
> >> users that instantiate the platform device (nor DT bindings).
> >>
> >> This is a first step in removing TI ST (shared transport) driver in
> >> favor of extending the BT hci_ll driver to support WL183x chips.
> >
> > since the firmware files TINfcInit_* also never made it into the linux-firmware tree, I have no idea who is using this driver. I am actually fine with removing it since it would be easy enough to bring back based on hci_ll driver once there is hardware to test this on.
> 
> Ping. Someone going to pick up this patch?
I'll take it, I need to catch up with pending NFC patches this week.

Cheers,
Samuel.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web