[PULL][Xenial] Update for third party Redpine Wifi-BT and Exar USB UART drivers

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[PULL][Xenial] Update for third party Redpine Wifi-BT and Exar USB UART drivers

Shrirang Bagul
BugLink: http://bugs.launchpad.net/bugs/1669672
BugLink: http://bugs.launchpad.net/bugs/1685133

This pull request to update two third party vendor drivers to be included
in A-rev delivary image for Dell IoT project. These drivers are:

1. Exar USB UART driver - fixes to Rx fail after resume from S3/S4
2. Redpine ver. 1.2.RC4 - multiple fixes and enables lot's of new features.

While the Exar driver is fileterd out of builds on s390 systems, Redpine
driver will compile only on amd64 systems. Also, the Redpine driver will
bind only to the RS9113 Wifi-BT combo chips probed on SDIO or USB buses.
Support for other Redpine chipsets will be supported by the driver carried
by the 4.4.X kernel from mainline.

Tested on Dell IoT gateway DVT-2 boards.

The following changes since commit 50aaaec159365f8f8788e054048545e7ec9734f1:

  UBUNTU: Ubuntu-4.4.0-72.93 (2017-03-31 15:54:28 +0200)

are available in the git repository at:

  git://kernel.ubuntu.com/snb/ubuntu-xenial.git caracalla-kt-for-arev

for you to fetch changes up to 2367e69e2056c5605867f2bd477fe59ff4c0284b:

  UBUNTU: [Config] Update CONFIG_VEN_RSI_* configs (2017-04-21 15:57:08 +0800)

----------------------------------------------------------------
Shrirang Bagul (4):
      UBUNTU: SAUCE: xr-usb-serial: Update driver for Exar USB serial ports
      UBUNTU: SAUCE: sdhci: use PCI ID to identify Dell IoT gateways
      UBUNTU: SAUCE: Redpine: Upgrade to ver. 1.2.RC4
      UBUNTU: [Config] Update CONFIG_VEN_RSI_* configs

 debian.master/config/config.common.ubuntu   |    7 +-
 drivers/mmc/host/sdhci.c                    |   19 +-
 ubuntu/rsi/Kconfig                          |   50 +-
 ubuntu/rsi/Makefile                         |   59 +-
 ubuntu/rsi/rsi_91x_coex.c                   |   53 +-
 ubuntu/rsi/rsi_91x_core.c                   |  152 ++--
 ubuntu/rsi/rsi_91x_debugfs.c                |   59 +-
 ubuntu/rsi/rsi_91x_hal.c                    |  444 ++++------
 ubuntu/rsi/rsi_91x_hci.c                    |   57 +-
 ubuntu/rsi/rsi_91x_mac80211.c               | 1222 ++++++++++++++++++++++-----
 ubuntu/rsi/rsi_91x_main.c                   |  205 ++---
 ubuntu/rsi/rsi_91x_mgmt.c                   |  687 +++++++++++----
 ubuntu/rsi/rsi_91x_ps.c                     |   44 +-
 ubuntu/rsi/rsi_91x_sdio.c                   |  269 +++++-
 ubuntu/rsi/rsi_91x_sdio_ops.c               |   75 +-
 ubuntu/rsi/rsi_91x_usb.c                    |   77 +-
 ubuntu/rsi/rsi_91x_usb_ops.c                |   37 +-
 ubuntu/rsi/rsi_boot_params.h                |   38 +-
 ubuntu/rsi/rsi_coex.h                       |   38 +-
 ubuntu/rsi/rsi_common.h                     |   44 +-
 ubuntu/rsi/rsi_debugfs.h                    |   42 +-
 ubuntu/rsi/rsi_hal.h                        |   63 +-
 ubuntu/rsi/rsi_hci.h                        |   38 +-
 ubuntu/rsi/rsi_main.h                       |  110 ++-
 ubuntu/rsi/rsi_mgmt.h                       |   94 ++-
 ubuntu/rsi/rsi_ps.h                         |   39 +-
 ubuntu/rsi/rsi_sdio.h                       |   38 +-
 ubuntu/rsi/rsi_usb.h                        |   41 +-
 ubuntu/xr-usb-serial/README.txt             |    3 +
 ubuntu/xr-usb-serial/xr_get_smbios.c        |  350 ++++++++
 ubuntu/xr-usb-serial/xr_get_smbios.h        |  237 ++++++
 ubuntu/xr-usb-serial/xr_usb_serial_common.c |  392 ++++++---
 ubuntu/xr-usb-serial/xr_usb_serial_common.h |   16 +-
 ubuntu/xr-usb-serial/xr_usb_serial_hal.c    |  244 +++++-
 ubuntu/xr-usb-serial/xr_usb_serial_ioctl.h  |    7 +
 35 files changed, 4065 insertions(+), 1285 deletions(-)
 create mode 100644 ubuntu/xr-usb-serial/xr_get_smbios.c
 create mode 100644 ubuntu/xr-usb-serial/xr_get_smbios.h

--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

Re: [PULL][Xenial] Update for third party Redpine Wifi-BT and Exar USB UART drivers

Stefan Bader-2
On 21.04.2017 11:12, Shrirang Bagul wrote:
> git://kernel.ubuntu.com/snb/ubuntu-xenial.git caracalla-kt-for-arev

I really don't understand what the changes to drivers/mmc/host/sdhci.c should
accomplish:

@@ -1745,9 +1746,18 @@ static void sdhci_enable_sdio_irq_nolock(struct
sdhci_host *host, int enable)
 static void sdhci_enable_sdio_irq(struct mmc_host *mmc, int enable)
 {
        struct sdhci_host *host = mmc_priv(mmc);
+       struct pci_dev *pci_host;
        unsigned long flags;

-       sdhci_runtime_pm_get(host);
+       pci_host = pci_get_subsys(PCI_ANY_ID, PCI_ANY_ID,
+                       0x1028, 0x07b9, NULL);
+
+       if (!pci_host)
+               sdhci_runtime_pm_get(host);
+       else {
+               if (enable)
+                       sdhci_runtime_pm_get(host);
+       }

        spin_lock_irqsave(&host->lock, flags);
        if (enable)

So pci_host set to a value means this is the gw and NULL for anything else. At
least for everything else the behaviour is not changed. Only for the IOT device
the reference (assuming that is what pm_get/put do) is kept between enabling the
IRQ until disabling it (while otherwise it is kept only while modifying the state).
On the positive side it should not cause regressions for everything else but
while not seeing any additional protection for that case, then why change it at all?

-Stefan


@@ -1758,7 +1768,12 @@ static void sdhci_enable_sdio_irq(struct mmc_host *mmc,
int enable)
        sdhci_enable_sdio_irq_nolock(host, enable);
        spin_unlock_irqrestore(&host->lock, flags);

-       sdhci_runtime_pm_put(host);
+       if (!pci_host)
+               sdhci_runtime_pm_put(host);
+       else {
+               if (!enable)
+                       sdhci_runtime_pm_put(host);
+       }
 }

 static int sdhci_do_start_signal_voltage_switch(struct sdhci_host *host,


--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [PULL][Xenial] Update for third party Redpine Wifi-BT and Exar USB UART drivers

Shrirang Bagul


On Fri, Apr 21, 2017 at 6:43 PM, Stefan Bader <[hidden email]> wrote:
On <a href="tel:21.04.2017%2011" value="+12104201711">21.04.2017 11:12, Shrirang Bagul wrote:
> git://kernel.ubuntu.com/snb/ubuntu-xenial.git caracalla-kt-for-arev

I really don't understand what the changes to drivers/mmc/host/sdhci.c should
accomplish:

@@ -1745,9 +1746,18 @@ static void sdhci_enable_sdio_irq_nolock(struct
sdhci_host *host, int enable)
 static void sdhci_enable_sdio_irq(struct mmc_host *mmc, int enable)
 {
        struct sdhci_host *host = mmc_priv(mmc);
+       struct pci_dev *pci_host;
        unsigned long flags;

-       sdhci_runtime_pm_get(host);
+       pci_host = pci_get_subsys(PCI_ANY_ID, PCI_ANY_ID,
+                       0x1028, 0x07b9, NULL);
+
+       if (!pci_host)
+               sdhci_runtime_pm_get(host);
+       else {
+               if (enable)
+                       sdhci_runtime_pm_get(host);
+       }

        spin_lock_irqsave(&host->lock, flags);
        if (enable)

So pci_host set to a value means this is the gw and NULL for anything else. At
least for everything else the behaviour is not changed. Only for the IOT device
the reference (assuming that is what pm_get/put do) is kept between enabling the
IRQ until disabling it (while otherwise it is kept only while modifying the state).
On the positive side it should not cause regressions for everything else but
while not seeing any additional protection for that case, then why change it at all?

-Stefan

The patch is targeted to be applied only for specific models of Dell IoT gateways which use
Intel Baytrail-I processors. This patch [1] is required to support SDIO IRQ's on Baytrail [2].
Because this project will eventually go through  a de-branding / re-branding process, quirks 
based on DMI strings cannot be used to uniquely identify the hardware. Hence, the use 
of PCI host sub-system ID [3] to get runtime pm when sdio IRQ is enabled.


-Shrirang


@@ -1758,7 +1768,12 @@ static void sdhci_enable_sdio_irq(struct mmc_host *mmc,
int enable)
        sdhci_enable_sdio_irq_nolock(host, enable);
        spin_unlock_irqrestore(&host->lock, flags);

-       sdhci_runtime_pm_put(host);
+       if (!pci_host)
+               sdhci_runtime_pm_put(host);
+       else {
+               if (!enable)
+                       sdhci_runtime_pm_put(host);
+       }
 }

 static int sdhci_do_start_signal_voltage_switch(struct sdhci_host *host,



--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

Re: [PULL][Xenial] Update for third party Redpine Wifi-BT and Exar USB UART drivers

Colin King
On 21/04/17 15:50, Shrirang Bagul wrote:

>
>
> On Fri, Apr 21, 2017 at 6:43 PM, Stefan Bader
> <[hidden email] <mailto:[hidden email]>> wrote:
>
>     On 21.04.2017 11 <tel:21.04.2017%2011>:12, Shrirang Bagul wrote:
>     > git://kernel.ubuntu.com/snb/ubuntu-xenial.git
>     <http://kernel.ubuntu.com/snb/ubuntu-xenial.git> caracalla-kt-for-arev
>
>     I really don't understand what the changes to
>     drivers/mmc/host/sdhci.c should
>     accomplish:
>
>     @@ -1745,9 +1746,18 @@ static void sdhci_enable_sdio_irq_nolock(struct
>     sdhci_host *host, int enable)
>      static void sdhci_enable_sdio_irq(struct mmc_host *mmc, int enable)
>      {
>             struct sdhci_host *host = mmc_priv(mmc);
>     +       struct pci_dev *pci_host;
>             unsigned long flags;
>
>     -       sdhci_runtime_pm_get(host);
>     +       pci_host = pci_get_subsys(PCI_ANY_ID, PCI_ANY_ID,
>     +                       0x1028, 0x07b9, NULL);
>     +
>     +       if (!pci_host)
>     +               sdhci_runtime_pm_get(host);
>     +       else {
>     +               if (enable)
>     +                       sdhci_runtime_pm_get(host);
>     +       }
>
>             spin_lock_irqsave(&host->lock, flags);
>             if (enable)
>
>     So pci_host set to a value means this is the gw and NULL for
>     anything else. At
>     least for everything else the behaviour is not changed. Only for the
>     IOT device
>     the reference (assuming that is what pm_get/put do) is kept between
>     enabling the
>     IRQ until disabling it (while otherwise it is kept only while
>     modifying the state).
>     On the positive side it should not cause regressions for everything
>     else but
>     while not seeing any additional protection for that case, then why
>     change it at all?
>
>     -Stefan
>
>
> The patch is targeted to be applied only for specific models of Dell IoT
> gateways which use
> Intel Baytrail-I processors. This patch [1] is required to support SDIO
> IRQ's on Baytrail [2].
> Because this project will eventually go through  a de-branding /
> re-branding process, quirks
> based on DMI strings cannot be used to uniquely identify the hardware.
> Hence, the use
> of PCI host sub-system ID [3] to get runtime pm when sdio IRQ is enabled.
>
> [1] https://git.congatec.com/arm/qmx6_kernel/commit/2ced65a11885ea84c6d3cd2ec8832d489bb0c3f7
> [2] http://www.spinics.net/lists/linux-mmc/msg41440.html
> [3] Inspired from :
> http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?id=38a6598a75d76b6625fca0972cd463fe56cab368
>
> -Shrirang


OK, thanks for the explanation. I can understand now why the keying on
the Dell IoT gateway is not based on a DMI check. Will the PCI IDs of
the system change in the future with different models?

As for the this patch, it does not appear to change the behaviour for
systems other than the one that has that specific PCI IDs.

Colin.

>
>
>
>     @@ -1758,7 +1768,12 @@ static void sdhci_enable_sdio_irq(struct
>     mmc_host *mmc,
>     int enable)
>             sdhci_enable_sdio_irq_nolock(host, enable);
>             spin_unlock_irqrestore(&host->lock, flags);
>
>     -       sdhci_runtime_pm_put(host);
>     +       if (!pci_host)
>     +               sdhci_runtime_pm_put(host);
>     +       else {
>     +               if (!enable)
>     +                       sdhci_runtime_pm_put(host);
>     +       }
>      }
>
>      static int sdhci_do_start_signal_voltage_switch(struct sdhci_host
>     *host,
>
>



--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

Re: [PULL][Xenial] Update for third party Redpine Wifi-BT and Exar USB UART drivers

Shrirang Bagul
On Fri, 2017-04-21 at 19:32 +0100, Colin Ian King wrote:

> On 21/04/17 15:50, Shrirang Bagul wrote:
> >
> >
> > On Fri, Apr 21, 2017 at 6:43 PM, Stefan Bader
> > <[hidden email] <mailto:[hidden email]>> wrote:
> >
> >     On 21.04.2017 11 <tel:21.04.2017%2011>:12, Shrirang Bagul wrote:
> >     > git://kernel.ubuntu.com/snb/ubuntu-xenial.git
> >     <http://kernel.ubuntu.com/snb/ubuntu-xenial.git> caracalla-kt-for-arev
> >
> >     I really don't understand what the changes to
> >     drivers/mmc/host/sdhci.c should
> >     accomplish:
> >
> >     @@ -1745,9 +1746,18 @@ static void sdhci_enable_sdio_irq_nolock(struct
> >     sdhci_host *host, int enable)
> >      static void sdhci_enable_sdio_irq(struct mmc_host *mmc, int enable)
> >      {
> >             struct sdhci_host *host = mmc_priv(mmc);
> >     +       struct pci_dev *pci_host;
> >             unsigned long flags;
> >
> >     -       sdhci_runtime_pm_get(host);
> >     +       pci_host = pci_get_subsys(PCI_ANY_ID, PCI_ANY_ID,
> >     +                       0x1028, 0x07b9, NULL);
> >     +
> >     +       if (!pci_host)
> >     +               sdhci_runtime_pm_get(host);
> >     +       else {
> >     +               if (enable)
> >     +                       sdhci_runtime_pm_get(host);
> >     +       }
> >
> >             spin_lock_irqsave(&host->lock, flags);
> >             if (enable)
> >
> >     So pci_host set to a value means this is the gw and NULL for
> >     anything else. At
> >     least for everything else the behaviour is not changed. Only for the
> >     IOT device
> >     the reference (assuming that is what pm_get/put do) is kept between
> >     enabling the
> >     IRQ until disabling it (while otherwise it is kept only while
> >     modifying the state).
> >     On the positive side it should not cause regressions for everything
> >     else but
> >     while not seeing any additional protection for that case, then why
> >     change it at all?
> >
> >     -Stefan
> >
> >
> > The patch is targeted to be applied only for specific models of Dell IoT
> > gateways which use
> > Intel Baytrail-I processors. This patch [1] is required to support SDIO
> > IRQ's on Baytrail [2].
> > Because this project will eventually go through  a de-branding /
> > re-branding process, quirks 
> > based on DMI strings cannot be used to uniquely identify the hardware.
> > Hence, the use 
> > of PCI host sub-system ID [3] to get runtime pm when sdio IRQ is enabled.
> >
> > [1] https://git.congatec.com/arm/qmx6_kernel/commit/2ced65a11885ea84c6d3cd2ec8832
> > d489bb0c3f7
> > [2] http://www.spinics.net/lists/linux-mmc/msg41440.html
> > [3] Inspired from :
> > http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?id=38a6598a75d76b66
> > 25fca0972cd463fe56cab368
> >
> > -Shrirang
>
>
> OK, thanks for the explanation. I can understand now why the keying on
> the Dell IoT gateway is not based on a DMI check. Will the PCI IDs of
> the system change in the future with different models?
No. The PCI IDs on all SKU's of this product will not change.

-Shrirang

>
> As for the this patch, it does not appear to change the behaviour for
> systems other than the one that has that specific PCI IDs.
>
> Colin.
>
> >
> >
> >
> >     @@ -1758,7 +1768,12 @@ static void sdhci_enable_sdio_irq(struct
> >     mmc_host *mmc,
> >     int enable)
> >             sdhci_enable_sdio_irq_nolock(host, enable);
> >             spin_unlock_irqrestore(&host->lock, flags);
> >
> >     -       sdhci_runtime_pm_put(host);
> >     +       if (!pci_host)
> >     +               sdhci_runtime_pm_put(host);
> >     +       else {
> >     +               if (!enable)
> >     +                       sdhci_runtime_pm_put(host);
> >     +       }
> >      }
> >
> >      static int sdhci_do_start_signal_voltage_switch(struct sdhci_host
> >     *host,
> >
> >
>
>

--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

ACK: [PULL][Xenial] Update for third party Redpine Wifi-BT and Exar USB UART drivers

Colin King
On 22/04/17 11:53, Shrirang Bagul wrote:

> On Fri, 2017-04-21 at 19:32 +0100, Colin Ian King wrote:
>> On 21/04/17 15:50, Shrirang Bagul wrote:
>>>
>>>
>>> On Fri, Apr 21, 2017 at 6:43 PM, Stefan Bader
>>> <[hidden email] <mailto:[hidden email]>> wrote:
>>>
>>>     On 21.04.2017 11 <tel:21.04.2017%2011>:12, Shrirang Bagul wrote:
>>>     > git://kernel.ubuntu.com/snb/ubuntu-xenial.git
>>>     <http://kernel.ubuntu.com/snb/ubuntu-xenial.git> caracalla-kt-for-arev
>>>
>>>     I really don't understand what the changes to
>>>     drivers/mmc/host/sdhci.c should
>>>     accomplish:
>>>
>>>     @@ -1745,9 +1746,18 @@ static void sdhci_enable_sdio_irq_nolock(struct
>>>     sdhci_host *host, int enable)
>>>      static void sdhci_enable_sdio_irq(struct mmc_host *mmc, int enable)
>>>      {
>>>             struct sdhci_host *host = mmc_priv(mmc);
>>>     +       struct pci_dev *pci_host;
>>>             unsigned long flags;
>>>
>>>     -       sdhci_runtime_pm_get(host);
>>>     +       pci_host = pci_get_subsys(PCI_ANY_ID, PCI_ANY_ID,
>>>     +                       0x1028, 0x07b9, NULL);
>>>     +
>>>     +       if (!pci_host)
>>>     +               sdhci_runtime_pm_get(host);
>>>     +       else {
>>>     +               if (enable)
>>>     +                       sdhci_runtime_pm_get(host);
>>>     +       }
>>>
>>>             spin_lock_irqsave(&host->lock, flags);
>>>             if (enable)
>>>
>>>     So pci_host set to a value means this is the gw and NULL for
>>>     anything else. At
>>>     least for everything else the behaviour is not changed. Only for the
>>>     IOT device
>>>     the reference (assuming that is what pm_get/put do) is kept between
>>>     enabling the
>>>     IRQ until disabling it (while otherwise it is kept only while
>>>     modifying the state).
>>>     On the positive side it should not cause regressions for everything
>>>     else but
>>>     while not seeing any additional protection for that case, then why
>>>     change it at all?
>>>
>>>     -Stefan
>>>
>>>
>>> The patch is targeted to be applied only for specific models of Dell IoT
>>> gateways which use
>>> Intel Baytrail-I processors. This patch [1] is required to support SDIO
>>> IRQ's on Baytrail [2].
>>> Because this project will eventually go through  a de-branding /
>>> re-branding process, quirks
>>> based on DMI strings cannot be used to uniquely identify the hardware.
>>> Hence, the use
>>> of PCI host sub-system ID [3] to get runtime pm when sdio IRQ is enabled.
>>>
>>> [1] https://git.congatec.com/arm/qmx6_kernel/commit/2ced65a11885ea84c6d3cd2ec8832
>>> d489bb0c3f7
>>> [2] http://www.spinics.net/lists/linux-mmc/msg41440.html
>>> [3] Inspired from :
>>> http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?id=38a6598a75d76b66
>>> 25fca0972cd463fe56cab368
>>>
>>> -Shrirang
>>
>>
>> OK, thanks for the explanation. I can understand now why the keying on
>> the Dell IoT gateway is not based on a DMI check. Will the PCI IDs of
>> the system change in the future with different models?
> No. The PCI IDs on all SKU's of this product will not change.

OK, thanks for that info.

Acked-by: Colin Ian King <[hidden email]>

>
> -Shrirang
>>
>> As for the this patch, it does not appear to change the behaviour for
>> systems other than the one that has that specific PCI IDs.
>>
>> Colin.
>>
>>>
>>>
>>>
>>>     @@ -1758,7 +1768,12 @@ static void sdhci_enable_sdio_irq(struct
>>>     mmc_host *mmc,
>>>     int enable)
>>>             sdhci_enable_sdio_irq_nolock(host, enable);
>>>             spin_unlock_irqrestore(&host->lock, flags);
>>>
>>>     -       sdhci_runtime_pm_put(host);
>>>     +       if (!pci_host)
>>>     +               sdhci_runtime_pm_put(host);
>>>     +       else {
>>>     +               if (!enable)
>>>     +                       sdhci_runtime_pm_put(host);
>>>     +       }
>>>      }
>>>
>>>      static int sdhci_do_start_signal_voltage_switch(struct sdhci_host
>>>     *host,
>>>
>>>
>>
>>
>


--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

ACK/cmnt: [PULL][Xenial] Update for third party Redpine Wifi-BT and Exar USB UART drivers

Stefan Bader-2
In reply to this post by Shrirang Bagul
On 21.04.2017 11:12, Shrirang Bagul wrote:
> BugLink: http://bugs.launchpad.net/bugs/1669672
> BugLink: http://bugs.launchpad.net/bugs/1685133
>
> This pull request to update two third party vendor drivers to be included
> in A-rev delivary image for Dell IoT project. These drivers are:
>

Ok, after discussing this with Colin I think the change to common code works by
keeping hold of whatever pm_get does, so the generic driver fails to meddle with
things. And for hw other than this board everything remains the same. So ok this
time but note that I see upstream code to remove the pm_get/put calls in newer
kernel versions. So it won't work then.

-Stefan

> 1. Exar USB UART driver - fixes to Rx fail after resume from S3/S4
> 2. Redpine ver. 1.2.RC4 - multiple fixes and enables lot's of new features.
>
> While the Exar driver is fileterd out of builds on s390 systems, Redpine
> driver will compile only on amd64 systems. Also, the Redpine driver will
> bind only to the RS9113 Wifi-BT combo chips probed on SDIO or USB buses.
> Support for other Redpine chipsets will be supported by the driver carried
> by the 4.4.X kernel from mainline.
>
> Tested on Dell IoT gateway DVT-2 boards.
>
> The following changes since commit 50aaaec159365f8f8788e054048545e7ec9734f1:
>
>   UBUNTU: Ubuntu-4.4.0-72.93 (2017-03-31 15:54:28 +0200)
>
> are available in the git repository at:
>
>   git://kernel.ubuntu.com/snb/ubuntu-xenial.git caracalla-kt-for-arev
>
> for you to fetch changes up to 2367e69e2056c5605867f2bd477fe59ff4c0284b:
>
>   UBUNTU: [Config] Update CONFIG_VEN_RSI_* configs (2017-04-21 15:57:08 +0800)
>
> ----------------------------------------------------------------
> Shrirang Bagul (4):
>       UBUNTU: SAUCE: xr-usb-serial: Update driver for Exar USB serial ports
>       UBUNTU: SAUCE: sdhci: use PCI ID to identify Dell IoT gateways
>       UBUNTU: SAUCE: Redpine: Upgrade to ver. 1.2.RC4
>       UBUNTU: [Config] Update CONFIG_VEN_RSI_* configs
>
>  debian.master/config/config.common.ubuntu   |    7 +-
>  drivers/mmc/host/sdhci.c                    |   19 +-
>  ubuntu/rsi/Kconfig                          |   50 +-
>  ubuntu/rsi/Makefile                         |   59 +-
>  ubuntu/rsi/rsi_91x_coex.c                   |   53 +-
>  ubuntu/rsi/rsi_91x_core.c                   |  152 ++--
>  ubuntu/rsi/rsi_91x_debugfs.c                |   59 +-
>  ubuntu/rsi/rsi_91x_hal.c                    |  444 ++++------
>  ubuntu/rsi/rsi_91x_hci.c                    |   57 +-
>  ubuntu/rsi/rsi_91x_mac80211.c               | 1222 ++++++++++++++++++++++-----
>  ubuntu/rsi/rsi_91x_main.c                   |  205 ++---
>  ubuntu/rsi/rsi_91x_mgmt.c                   |  687 +++++++++++----
>  ubuntu/rsi/rsi_91x_ps.c                     |   44 +-
>  ubuntu/rsi/rsi_91x_sdio.c                   |  269 +++++-
>  ubuntu/rsi/rsi_91x_sdio_ops.c               |   75 +-
>  ubuntu/rsi/rsi_91x_usb.c                    |   77 +-
>  ubuntu/rsi/rsi_91x_usb_ops.c                |   37 +-
>  ubuntu/rsi/rsi_boot_params.h                |   38 +-
>  ubuntu/rsi/rsi_coex.h                       |   38 +-
>  ubuntu/rsi/rsi_common.h                     |   44 +-
>  ubuntu/rsi/rsi_debugfs.h                    |   42 +-
>  ubuntu/rsi/rsi_hal.h                        |   63 +-
>  ubuntu/rsi/rsi_hci.h                        |   38 +-
>  ubuntu/rsi/rsi_main.h                       |  110 ++-
>  ubuntu/rsi/rsi_mgmt.h                       |   94 ++-
>  ubuntu/rsi/rsi_ps.h                         |   39 +-
>  ubuntu/rsi/rsi_sdio.h                       |   38 +-
>  ubuntu/rsi/rsi_usb.h                        |   41 +-
>  ubuntu/xr-usb-serial/README.txt             |    3 +
>  ubuntu/xr-usb-serial/xr_get_smbios.c        |  350 ++++++++
>  ubuntu/xr-usb-serial/xr_get_smbios.h        |  237 ++++++
>  ubuntu/xr-usb-serial/xr_usb_serial_common.c |  392 ++++++---
>  ubuntu/xr-usb-serial/xr_usb_serial_common.h |   16 +-
>  ubuntu/xr-usb-serial/xr_usb_serial_hal.c    |  244 +++++-
>  ubuntu/xr-usb-serial/xr_usb_serial_ioctl.h  |    7 +
>  35 files changed, 4065 insertions(+), 1285 deletions(-)
>  create mode 100644 ubuntu/xr-usb-serial/xr_get_smbios.c
>  create mode 100644 ubuntu/xr-usb-serial/xr_get_smbios.h
>


--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

APPLIED[Xenial]: [PULL][Xenial] Update for third party Redpine Wifi-BT and Exar USB UART drivers

Stefan Bader-2
In reply to this post by Shrirang Bagul



--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team

signature.asc (836 bytes) Download Attachment