Introduce drivers/soc and add QCOM GSBI driver
Subsystems (4)
v2 cover Introduce drivers/soc and add QCOM GSBI driver
The first patch in this set adds the drivers/soc directory and all the necessary plumbing. These changes were discussed at the kernel summit and also were introduced in an earlier patch set from Santosh Shilimkar.
Reference the following set of patches:
https://lkml.org/lkml/2014/2/28/567
The remaining patches add the QCOM GSBI (General Serial Bus Interface) driver, device tree binding information for both the GSBI and child node interaction, and lastly a patch to fix the current MSM serial driver to work correctly with the GSBI changes.
Before this patch series, serial drivers (UART, I2C, and SPI) were all directly accessing the overarching mux control settings for the parent GSBI device. This leads to unfortunate interactions when you want a UART and I2C device which share the same GSBI interface. By moving the serial devices to child nodes of the GSBI, we can get the right mode setting for the ports and keep the children from accessing the GSBI directly.
Changes from v1:
- Add dt-bindings file containing definitions for MUX values
- Fix code comments
- Removed unnecessary code
Andy Gross (4):
soc: Placeholder files for drivers/soc
soc: qcom: Add device tree binding for GSBI
soc: qcom: Add GSBI driver
tty: serial: msm: Remove direct access to GSBI
.../devicetree/bindings/soc/qcom/qcom,gsbi.txt | 78 ++++++++++++++++++ drivers/Kconfig | 2 + drivers/Makefile | 4 + drivers/soc/Kconfig | 5 ++ drivers/soc/Makefile | 5 ++ drivers/soc/qcom/Kconfig | 11 +++ drivers/soc/qcom/Makefile | 1 + drivers/soc/qcom/qcom_gsbi.c | 84 ++++++++++++++++++++ drivers/tty/serial/msm_serial.c | 48 +---------- drivers/tty/serial/msm_serial.h | 5 -- include/dt-bindings/soc/qcom,gsbi.h | 26 ++++++ 11 files changed, 218 insertions(+), 51 deletions(-) create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,gsbi.txt create mode 100644 drivers/soc/Kconfig create mode 100644 drivers/soc/Makefile create mode 100644 drivers/soc/qcom/Kconfig create mode 100644 drivers/soc/qcom/Makefile create mode 100644 drivers/soc/qcom/qcom_gsbi.c create mode 100644 include/dt-bindings/soc/qcom,gsbi.h
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH v2 1/4 soc: Placeholder files for drivers/soc
Add placeholder Kconfig and linkage for driver/soc.
The first patch set that implemented this was authored by Santosh Shilimkar:
https://lkml.org/lkml/2014/2/28/567
--- drivers/Kconfig | 2 ++ drivers/Makefile | 4 ++++ drivers/soc/Kconfig | 4 ++++ 3 files changed, 10 insertions(+) create mode 100644 drivers/soc/Kconfig
drivers/Kconfig +2 -0
@@ -130,6 +130,8 @@ source "drivers/staging/Kconfig" source "drivers/platform/Kconfig" +source "drivers/soc/Kconfig" + source "drivers/clk/Kconfig" source "drivers/hwspinlock/Kconfig"
drivers/Makefile +4 -0
@@ -132,6 +132,10 @@ obj-$(CONFIG_VHOST_RING) += vhost/ obj-$(CONFIG_VLYNQ) += vlynq/ obj-$(CONFIG_STAGING) += staging/ obj-y += platform/ + +# soc specific drivers +obj-y += soc/ + #common clk code obj-y += clk/
drivers/soc/Kconfig new file +4 -0
@@ -0,0 +1,4 @@ +menu "SOC specific Drivers" + +endmenu +`
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
Re: [Patch v2 1/4] soc: Placeholder files for drivers/soc
Quoted 7 lines · Andy Gross
Add placeholder
Kconfigand linkage for driver/soc.The first patch set that implemented this was authored by Santosh Shilimkar:
https://lkml.org/lkml/2014/2/28/567Signed-off-by Andy Gross <[email protected]>---
Good to see these patches on the list. Me and Kumar spoke about it many times before.
BTW, I just posted updated version. Feel free to use the from it instead of 4subject one.
Regards,
Santosh
Re: [Patch v2 1/4] soc: Placeholder files for drivers/soc
Quoted 14 lines · Santosh Shilimkar
Quoted 7 lines · Andy Gross
Add placeholder
Kconfigand linkage for driver/soc.The first patch set that implemented this was authored by Santosh Shilimkar:
https://lkml.org/lkml/2014/2/28/567Signed-off-by Andy Gross <[email protected]>---
Good to see these patches on the list. Me and Kumar spoke about it many times before.
BTW, I just posted updated version. Feel free to use the from it instead of 4subject one.
Quoted 6 lines
Regards,
Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Paul,
Did you have any other thoughts on this, do we want to add more to Santosh?s patch w/regards to comments or MAINTAINERs?
- k
Signature · 2 lines
Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v2 2/4 soc: qcom: Add device tree binding for GSBI
In reply to Andy GrossAdd device tree binding support for the QCOM GSBI driver.
--- .../devicetree/bindings/soc/qcom/qcom,gsbi.txt | 78 ++++++++++++++++++++ include/dt-bindings/soc/qcom,gsbi.h | 26 +++++++ 2 files changed, 104 insertions(+) create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,gsbi.txt create mode 100644 include/dt-bindings/soc/qcom,gsbi.h
Documentation/devicetree/bindings/soc/qcom/qcom,gsbi.txt new file +78 -0
@@ -0,0 +1,78 @@ +QCOM GSBI (General Serial Bus Interface) Driver + +The GSBI controller is modeled as a node with zero or more child nodes, each +representing a serial sub-node device that is mux'd as part of the GSBI +configuration settings. The mode setting will govern the input/output mode of +the 4 GSBI IOs. + +Required properties: +- compatible: must contain "qcom,gsbi-v1.0.0" for APQ8064/IPQ8064 +- reg: Address range for GSBI registers +- clocks: required clock +- clock-names: must contain "iface" entry +- qcom,mode : indicates MUX value for configuration of the serial interface. + Please reference dt-bindings/soc/qcom,gsbi.h for valid mux values. + +Optional properties: +- qcom,crci : indicates CRCI MUX value for QUP CRCI ports. Please reference + dt-bindings/soc/qcom,gsbi.h for valid CRCI mux values. + +Required properties if child node exists: +- #address-cells: Must be 1 +- #size-cells: Must be 1 +- ranges: Must be present + +Properties for children: + +A GSBI controller node can contain 0 or more child nodes representing serial +devices. These serial devices can be a QCOM UART, I2C controller, spi +controller, or some combination of aforementioned devices. + +See the following for child node definitions: +Documentation/devicetree/bindings/i2c/qcom,i2c-qup.txt +Documentation/devicetree/bindings/spi/qcom,spi-qup.txt +Documentation/devicetree/bindings/serial/qcom,msm-uartdm.txt + +Example for APQ8064: + +#include <dt-bindings/soc/qcom,gsbi.h> + + gsbi4 at 16300000 { + compatible = "qcom,gsbi-v1.0.0"; + reg = <0x16300000 0x100>; + clocks = <&gcc GSBI4_H_CLK>; + clock-names = "iface"; + #address-cells = <1>; + #size-cells = <1>; + ranges; + qcom,mode = <GSBI_PROT_I2C_UART>; + qcom,crci = <GSBI_CRCI_QUP>; + + /* child nodes go under here */ + + i2c_qup4: i2c at 16380000 { + compatible = "qcom,i2c-qup-v1.1.1"; + reg = <0x16380000 0x1000>; + interrupts = <0 153 0>; + + clocks = <&gcc GSBI4_QUP_CLK>, <&gcc GSBI4_H_CLK>; + clock-names = "core", "iface"; + + clock-frequency = <200000>; + + #address-cells = <1>; + #size-cells = <0>; + + }; + + uart4: serial at 16340000 { + compatible = "qcom,msm-uartdm-v1.3", "qcom,msm-uartdm"; + reg = <0x16340000 0x1000>, + <0x16300000 0x1000>; + interrupts = <0 152 0x0>; + clocks = <&gcc GSBI4_UART_CLK>, <&gcc GSBI4_H_CLK>; + clock-names = "core", "iface"; + status = "ok"; + }; + }; +
include/dt-bindings/soc/qcom,gsbi.h new file +26 -0
@@ -0,0 +1,26 @@ +/* Copyright (c) 2013, The Linux Foundation. All rights reserved. +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License version 2 and +* only version 2 as published by the Free Software Foundation. +* +* This program is distributed in the hope that it will be useful, +* but WITHOUT ANY WARRANTY; without even the implied warranty of +* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +* GNU General Public License for more details. +*/ +#ifndef __DT_BINDINGS_QCOM_GSBI_H +#define __DT_BINDINGS_QCOM_GSBI_H + +#define GSBI_PROT_IDLE 0 +#define GSBI_PROT_I2C_UIM 1 +#define GSBI_PROT_I2C 2 +#define GSBI_PROT_SPI 3 +#define GSBI_PROT_UART_W_FC 4 +#define GSBI_PROT_UIM 5 +#define GSBI_PROT_I2C_UART 6 + +#define GSBI_CRCI_QUP 0 +#define GSBI_CRCI_UART 1 + +#endif
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
PATCH v2 3/4 soc: qcom: Add GSBI driver
In reply to Andy GrossThe GSBI (General Serial Bus Interface) driver controls the overarching configuration of the shared serial bus infrastructure on APQ8064, IPQ8064, and earlier QCOM processors. The GSBI supports UART, I2C, SPI, and UIM functionality in various combinations.
--- drivers/soc/Kconfig | 3 +- drivers/soc/Makefile | 5 +++ drivers/soc/qcom/Kconfig | 11 ++++++ drivers/soc/qcom/Makefile | 1 + drivers/soc/qcom/qcom_gsbi.c | 84 ++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 103 insertions(+), 1 deletion(-) create mode 100644 drivers/soc/Makefile create mode 100644 drivers/soc/qcom/Kconfig create mode 100644 drivers/soc/qcom/Makefile create mode 100644 drivers/soc/qcom/qcom_gsbi.c
drivers/soc/Kconfig +2 -1
@@ -1,4 +1,5 @@ menu "SOC specific Drivers" +source "drivers/soc/qcom/Kconfig" + endmenu -`
drivers/soc/Makefile new file +5 -0
@@ -0,0 +1,5 @@ +# +# Makefile for the Linux Kernel SOC specific device drivers. +# + +obj-$(CONFIG_ARCH_QCOM) += qcom/
drivers/soc/qcom/Kconfig new file +11 -0
@@ -0,0 +1,11 @@ +# +# QCOM Soc drivers +# +config QCOM_GSBI + tristate "QCOM General Serial Bus Interface" + depends on ARCH_QCOM + help + Say y here to enable GSBI support. The GSBI provides control + functions for connecting the underlying serial UART, SPI, and I2C + devices to the output pins. +
drivers/soc/qcom/Makefile new file +1 -0
@@ -0,0 +1 @@ +obj-$(CONFIG_QCOM_GSBI) += qcom_gsbi.o
drivers/soc/qcom/qcom_gsbi.c new file +84 -0
84 lines not on this page · raw message
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
Re: [Patch v2 3/4] soc: qcom: Add GSBI driver
Review
Quoted 4 lines · Andy Gross
(quoted diff) +4
-0+ +static const struct of_device_id gsbi_dt_match[] = { + { .compatible = "qcom,gsbi-v1.0.0", }, +};
Eek. This isn't NULL terminated.
-----8<---
From: Stephen Boyd <[email protected]>
Subject: [PATCH] soc: qcom: Terminate gsbi of match table
Failure to terminate this match table can lead to boot failures depending on where the compiler places the match table.
--- drivers/soc/qcom/qcom_gsbi.c | 1 + 1 file changed, 1 insertion(+)
drivers/soc/qcom/qcom_gsbi.c +1 -0
@@ -64,6 +64,7 @@ static int gsbi_probe(struct platform_device *pdev)static const struct of_device_id gsbi_dt_match[] = { { .compatible ="qcom,gsbi-v1.0.0" , }, + { } };MODULE_DEVICE_TABLE (of, gsbi_dt_match);
Signature · 2 lines
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
PATCH v2 4/4 tty: serial: msm: Remove direct access to GSBI
In reply to Andy GrossThis patch removes direct access of the GSBI registers. GSBI configuration should be done through the GSBI driver directly.
--- drivers/tty/serial/msm_serial.c | 48 ++------------------------------------- drivers/tty/serial/msm_serial.h | 5 ---- 2 files changed, 2 insertions(+), 51 deletions(-)
drivers/tty/serial/msm_serial.c +2 -46
@@ -45,7 +45,6 @@ struct msm_port {struct clk *clk;struct clk *pclk;unsigned int imr; -void __iomem *gsbi_base;int is_uartdm;unsigned int old_snap_state; };
@@ -586,9 +585,7 @@ static const char *msm_type(struct uart_port *port)static void msm_release_port (struct uart_port *port) {struct platform_device *pdev =to_platform_device (port->dev); -struct msm_port *msm_port =UART_TO_MSM (port);struct resource *uart_resource; -struct resource *gsbi_resource;resource_size_t size; uart_resource =platform_get_resource (pdev,IORESOURCE_MEM ,0 );
@@ -599,28 +596,12 @@ static void msm_release_port(struct uart_port *port)release_mem_region (port->mapbase, size);iounmap (port->membase); port->membase =NULL ; - -if (msm_port->gsbi_base) { -writel_relaxed (GSBI_PROTOCOL_IDLE , - msm_port->gsbi_base +GSBI_CONTROL ); - - gsbi_resource =platform_get_resource (pdev,IORESOURCE_MEM ,1 ); -if (unlikely (!gsbi_resource)) -return ; - - size =resource_size (gsbi_resource); -release_mem_region (gsbi_resource->start, size); -iounmap (msm_port->gsbi_base); - msm_port->gsbi_base =NULL ; - } }static int msm_request_port (struct uart_port *port) { -struct msm_port *msm_port =UART_TO_MSM (port);struct platform_device *pdev =to_platform_device (port->dev);struct resource *uart_resource; -struct resource *gsbi_resource;resource_size_t size;int ret;
@@ -639,30 +620,8 @@ static int msm_request_port(struct uart_port *port) goto fail_release_port; } - gsbi_resource =platform_get_resource (pdev,IORESOURCE_MEM ,1 ); -/* Is this a GSBI-based port? */ -if (gsbi_resource) { - size =resource_size (gsbi_resource); - -if (!request_mem_region (gsbi_resource->start, size, -"msm_serial" )) { - ret = -EBUSY ; - goto fail_release_port_membase; - } - - msm_port->gsbi_base =ioremap (gsbi_resource->start, size); -if (!msm_port->gsbi_base) { - ret = -EBUSY ; - goto fail_release_gsbi; - } - } -return 0 ; -fail_release_gsbi: -release_mem_region (gsbi_resource->start, size); -fail_release_port_membase: -iounmap (port->membase); fail_release_port:release_mem_region (port->mapbase, size);return ret;
@@ -670,7 +629,6 @@ fail_release_port:static void msm_config_port (struct uart_port *port,int flags) { -struct msm_port *msm_port =UART_TO_MSM (port);int ret;if (flags &UART_CONFIG_TYPE ) { port->type =PORT_MSM ;
@@ -678,9 +636,6 @@ static void msm_config_port(struct uart_port *port, int flags)if (ret)return ; } -if (msm_port->gsbi_base) -writel_relaxed (GSBI_PROTOCOL_UART , - msm_port->gsbi_base +GSBI_CONTROL ); }static int msm_verify_port (struct uart_port *port,struct serial_struct *ser)
@@ -976,6 +931,7 @@ static struct of_device_id msm_match_table[] = {static struct platform_driver msm_platform_driver = { .remove = msm_serial_remove, + .probe = msm_serial_probe, .driver = { .name ="msm_serial" , .owner =THIS_MODULE ,
@@ -991,7 +947,7 @@ static int __init msm_serial_init(void)if (unlikely (ret))return ret; - ret =platform_driver_probe (&msm_platform_driver, msm_serial_probe); + ret =platform_driver_register (&msm_platform_driver);if (unlikely (ret))uart_unregister_driver (&msm_uart_driver);
drivers/tty/serial/msm_serial.h +0 -5
@@ -108,11 +108,6 @@#define UART_ISR 0x0014#define UART_ISR_TX_READY (1 << 7) -#define GSBI_CONTROL 0x0 -#define GSBI_PROTOCOL_CODE 0x30 -#define GSBI_PROTOCOL_UART 0x40 -#define GSBI_PROTOCOL_IDLE 0x0 -#define UARTDM_DMRX 0x34#define UARTDM_NCF_TX 0x40#define UARTDM_RX_TOTAL_SNAP 0x38
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
Re: [Patch v2 4/4] tty: serial: msm: Remove direct access to GSBI
Quoted 8 lines · Andy Gross
This patch removes direct access of the GSBI registers. GSBI configuration should be done through the GSBI driver directly.
Signed-off-by Andy Gross <[email protected]>---
drivers/tty/serial/msm_serial.c| 48 ++-------------------------------------drivers/tty/serial/msm_serial.h| 5 ----2 files changed, 2 insertions(+), 51 deletions(-)
Greg,
Any update on pulling this is for next?
- k
Quoted 142 lines
drivers/tty/serial/msm_serial.c +0
-41@@ -45,7 +45,6 @@ struct msm_port {struct clk *clk;struct clk *pclk;unsigned int imr; -void __iomem *gsbi_base;int is_uartdm;unsigned int old_snap_state; };@@ -586,9 +585,7 @@ static const char *msm_type(struct uart_port *port)static void msm_release_port (struct uart_port *port) {struct platform_device *pdev =to_platform_device (port->dev); -struct msm_port *msm_port =UART_TO_MSM (port);struct resource *uart_resource; -struct resource *gsbi_resource;resource_size_t size; uart_resource =platform_get_resource (pdev,IORESOURCE_MEM ,0 );@@ -599,28 +596,12 @@ static void msm_release_port(struct uart_port *port)release_mem_region (port->mapbase, size);iounmap (port->membase); port->membase =NULL ; - -if (msm_port->gsbi_base) { -writel_relaxed (GSBI_PROTOCOL_IDLE , - msm_port->gsbi_base +GSBI_CONTROL ); - - gsbi_resource =platform_get_resource (pdev,IORESOURCE_MEM ,1 ); -if (unlikely (!gsbi_resource)) -return ; - - size =resource_size (gsbi_resource); -release_mem_region (gsbi_resource->start, size); -iounmap (msm_port->gsbi_base); - msm_port->gsbi_base =NULL ; - } }static int msm_request_port (struct uart_port *port) { -struct msm_port *msm_port =UART_TO_MSM (port);struct platform_device *pdev =to_platform_device (port->dev);struct resource *uart_resource; -struct resource *gsbi_resource;resource_size_t size;int ret;@@ -639,30 +620,8 @@ static int msm_request_port(struct uart_port *port) goto fail_release_port; } - gsbi_resource =platform_get_resource (pdev,IORESOURCE_MEM ,1 ); -/* Is this a GSBI-based port? */ -if (gsbi_resource) { - size =resource_size (gsbi_resource); - -if (!request_mem_region (gsbi_resource->start, size, -"msm_serial" )) { - ret = -EBUSY ; - goto fail_release_port_membase; - } - - msm_port->gsbi_base =ioremap (gsbi_resource->start, size); -if (!msm_port->gsbi_base) { - ret = -EBUSY ; - goto fail_release_gsbi; - } - } -return 0 ; -fail_release_gsbi: -release_mem_region (gsbi_resource->start, size); -fail_release_port_membase: -iounmap (port->membase);
fail_release_port:release_mem_region(port->mapbase, size); return ret;drivers/tty/serial/msm_serial.c +2
-5@@ -670,7 +629,6 @@ fail_release_port:static void msm_config_port (struct uart_port *port,int flags) { -struct msm_port *msm_port =UART_TO_MSM (port);int ret;if (flags &UART_CONFIG_TYPE ) { port->type =PORT_MSM ;@@ -678,9 +636,6 @@ static void msm_config_port(struct uart_port *port, int flags)if (ret)return ; } -if (msm_port->gsbi_base) -writel_relaxed (GSBI_PROTOCOL_UART , - msm_port->gsbi_base +GSBI_CONTROL ); }static int msm_verify_port (struct uart_port *port,struct serial_struct *ser)@@ -976,6 +931,7 @@ static struct of_device_id msm_match_table[] = {static struct platform_driver msm_platform_driver = { .remove = msm_serial_remove, + .probe = msm_serial_probe, .driver = { .name ="msm_serial" , .owner =THIS_MODULE ,@@ -991,7 +947,7 @@ static int __init msm_serial_init(void)if (unlikely (ret))return ret; - ret =platform_driver_probe (&msm_platform_driver, msm_serial_probe); + ret =platform_driver_register (&msm_platform_driver);if (unlikely (ret))uart_unregister_driver (&msm_uart_driver);drivers/tty/serial/msm_serial.h +0
-5@@ -108,11 +108,6 @@#define UART_ISR 0x0014#define UART_ISR_TX_READY (1 << 7) -#define GSBI_CONTROL 0x0 -#define GSBI_PROTOCOL_CODE 0x30 -#define GSBI_PROTOCOL_UART 0x40 -#define GSBI_PROTOCOL_IDLE 0x0 -#define UARTDM_DMRX 0x34#define UARTDM_NCF_TX 0x40#define UARTDM_RX_TOTAL_SNAP 0x38Signature · 7 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 2 lines
Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
Greg Kroah-Hartman
maintainerRe: [Patch v2 4/4] tty: serial: msm: Remove direct access to GSBI
Quoted 12 lines · Kumar Gala
Quoted 8 lines · Andy Gross
This patch removes direct access of the GSBI registers. GSBI configuration should be done through the GSBI driver directly.
Signed-off-by Andy Gross <[email protected]>---
drivers/tty/serial/msm_serial.c| 48 ++-------------------------------------drivers/tty/serial/msm_serial.h| 5 ----2 files changed, 2 insertions(+), 51 deletions(-)
Quoted 3 lines
Greg,
Any update on pulling this is for next?
I thought this was going through someone else's tree, sorry. And, there seemd to be a second set of patches for this, which I don't have anywhere :(
If you want me to take all of these, or just this one, Andy, can you please resend?
thanks,
greg k-h
Re: [Patch v2 4/4] tty: serial: msm: Remove direct access to GSBI
In reply to Kumar GalaQuoted 12 lines · Kumar Gala
Quoted 8 lines · Andy Gross
This patch removes direct access of the GSBI registers. GSBI configuration should be done through the GSBI driver directly.
Signed-off-by Andy Gross <[email protected]>---
drivers/tty/serial/msm_serial.c| 48 ++-------------------------------------drivers/tty/serial/msm_serial.h| 5 ----2 files changed, 2 insertions(+), 51 deletions(-)
Quoted 5 lines
Greg,
Any update on pulling this is for next?
- k
I?ll send it via arm-soc as the related patches are going via that path.
- k
Signature · 2 lines
Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation