Changes from v8:
Resending this patch series after rebasing to the latest usb-next branch.
Rewording inline comments for better readability.
Removed IS_ENABLED(CONFIG_OF) as pdev-dev.of_node is enough to check for dt
support.
Using of_match_ptr to add of_match_table to platform_driver structure.
This driver uses usb_phy interface to interact with s3c-hsotg. Supports
phy_init and phy_shutdown functions to enable/disable usb phy. Support
will be extended to host controllers and more Samsung SoCs.
Signed-off-by: Praveen Paneri p.pan...@samsung.com
Acked-by: Heiko Stuebner he...@sntech.de
Adding the transceiver to hsotg driver. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Praveen Paneri p.pan...@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/usb/gadget/s3c-hsotg.c | 37
On Thu, Jan 17, 2013 at 08:30:10PM +, Thierry Reding wrote:
On Thu, Jan 17, 2013 at 04:22:18PM +, Andrew Murray wrote:
On Thu, Jan 17, 2013 at 04:05:02PM +, Thierry Reding wrote:
On Thu, Jan 17, 2013 at 03:42:36PM +, Andrew Murray wrote:
On Wed, Jan 16, 2013 at 06:31:01PM
A seperate driver has been added to handle the usb part of control
module. A device for the above driver is created here, using the register
address information to be used by the driver for powering on the PHY and
for writing to the mailbox.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Added has_mailbox to the musb platform data to specify that omap uses
an external mailbox (in control module) to communicate with the musb
core during device connect and disconnect.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/mach-omap2/usb-musb.c |3 +++
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/omap-usb.txt |4 ++
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to control module registers for doing the above task which was
previously done in omap
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp.
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |4
1 file changed,
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/omap4.dtsi |8
1 file changed, 8 insertions(+)
diff --git
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-board.dts file.
The dt data specifies among others the interface type (ULPI or UTMI), mode
which is mostly OTG, power that specifies the amount of power this can supply
when in host
This patch series adds dt data to get MUSB working in omap4 and omap3.
Long time back a patch series with the same title was sent but only
a part of it got merged. The rest of it wasn't merged because of
adding omap control usb data to glue and usb phy.
Now there exists a separate driver for
On Wed, Jan 09, 2013 at 08:43:10PM +, Thierry Reding wrote:
Move the PCIe driver from arch/arm/mach-tegra into the drivers/pci/host
directory. The motivation is to collect various host controller drivers
in the same location in order to facilitate refactoring.
The Tegra PCIe driver has
On Fri, Jan 18, 2013 at 09:56:20AM +, Andrew Murray wrote:
On Wed, Jan 09, 2013 at 08:43:10PM +, Thierry Reding wrote:
Move the PCIe driver from arch/arm/mach-tegra into the drivers/pci/host
directory. The motivation is to collect various host controller drivers
in the same location
From: Patil, Rachna rac...@ti.com
This patch set is a cumulative set of [1] and [2] sent earlier.
Note that there are no code changes in either of the patch set,
only rebased on top of Linus's v3.8-rc3 tag to make sure that
all the patches apply without any conflicts.
This patch set has been
From: Patil, Rachna rac...@ti.com
Current code has hard coded value written to
step enable bits. Now the bits are updated based
on how many steps are needed to be configured got
from platform data.
The user needs to take care not to exceed
the count more than 16. While using ADC and TSC
one
From: Patil, Rachna rac...@ti.com
The current driver expected touchscreen input
wires(XP,XN,YP,YN) to be connected in a particular order.
Making changes to accept this as platform data.
Signed-off-by: Patil, Rachna rac...@ti.com
---
drivers/input/touchscreen/ti_am335x_tsc.c | 156
From: Patil, Rachna rac...@ti.com
When touchscreen and ADC are used together, this
unwanted fifo flush leads to loss of ADC data.
Signed-off-by: Patil, Rachna rac...@ti.com
---
drivers/input/touchscreen/ti_am335x_tsc.c | 10 --
1 file changed, 10 deletions(-)
diff --git
From: Patil, Rachna rac...@ti.com
Signed-off-by: Patil, Rachna rac...@ti.com
---
.../devicetree/bindings/mfd/ti_am335x_tscadc.txt | 35
1 file changed, 35 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/ti_am335x_tscadc.txt
diff --git
From: Patil, Rachna rac...@ti.com
Make changes to add DT support in the MFD core driver.
Signed-off-by: Patil, Rachna rac...@ti.com
---
drivers/mfd/ti_am335x_tscadc.c | 28 +++-
1 file changed, 23 insertions(+), 5 deletions(-)
diff --git
From: Patil, Rachna rac...@ti.com
Add DT support for client touchscreen driver
Signed-off-by: Patil, Rachna rac...@ti.com
---
drivers/input/touchscreen/ti_am335x_tsc.c | 94 +
1 file changed, 81 insertions(+), 13 deletions(-)
diff --git
From: Patil, Rachna rac...@ti.com
Add DT support for client ADC driver.
Signed-off-by: Patil, Rachna rac...@ti.com
---
drivers/iio/adc/ti_am335x_adc.c | 26 ++
1 file changed, 22 insertions(+), 4 deletions(-)
diff --git a/drivers/iio/adc/ti_am335x_adc.c
From: Patil, Rachna rac...@ti.com
Add support for core multifunctional device along
with its clients touchscreen and ADC.
Signed-off-by: Patil, Rachna rac...@ti.com
---
arch/arm/boot/dts/am335x-evm.dts | 13 +
arch/arm/boot/dts/am33xx.dtsi|8
2 files changed, 21
This patch set adds support for generic dma device tree bindings for
Samsung platforms and is dependent on the following patches from
Vinod Koul next branch
1)of: Add generic device tree DMA helpers
2)dmaengine: add helper function to request a slave DMA channel
This patch set is made based
Add xlate to translate the device-tree binding information into
the appropriate format. The filter function requires the dma
controller device node and dma channel number as filter_params.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
drivers/dma/pl330.c | 17 +
1
This patch registers the pl330 dma controller driver with the generic
device tree dma helper functions.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
drivers/dma/pl330.c | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/drivers/dma/pl330.c
This patch adds #dma-cells property to PL330 DMA controller
nodes for supporting generic dma dt bindings on samsung
exynos5250 platform.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
.../devicetree/bindings/dma/arm-pl330.txt |9 ++---
arch/arm/boot/dts/exynos5250.dtsi
This patch modify the filter function to filter the required channel
based on new filter params.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
drivers/dma/pl330.c | 11 ++-
1 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/drivers/dma/pl330.c
Continuing from discussion with Thierry (lkml.org/lkml/2013/1/18/107) perhaps
this will be useful to fold into your patchset - you may wish to remove the
overlap.
---
This patch attempts to overcome two difficulities when providing DT PCI host
bridge controllers:
At present PCI controllers are
On Fri, Jan 18, 2013 at 11:40:19AM +, Andrew Murray wrote:
static void __init pcibios_init_hw(struct hw_pci *hw, struct list_head *head)
{
struct pci_sys_data *sys = NULL;
+ static int busnr;
int ret;
- int nr, busnr;
-
- for (nr = busnr = 0; nr
Hi,
On Tue, Jan 15, 2013 at 02:12:51PM +0530, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to
This patch set is dependent on the following patches from
Vinod Koul next branch
1)of: Add generic device tree DMA helpers
2)dmaengine: add helper function to request a slave DMA channel
and also dependent on
1)DMA: PL330: Add xlate function
2)DMA: PL330: Register the DMA controller with the
On Thu, Jan 17, 2013 at 04:44:52PM +0530, kishon wrote:
@@ -171,6 +188,11 @@ static inline void devm_usb_put_phy(struct device
*dev, struct usb_phy *x)
{
}
+static inline struct usb_phy_bind *usb_bind_phy(const char *dev_name, u8
index,
+ const char
On Wed, Jan 16, 2013 at 08:30:56PM +0530, Kishon Vijay Abraham I wrote:
New platforms are being added which has multiple PHY's (of same type) and
which has multiple USB controllers. The binding information has to be
present in the PHY library (otg.c) in order for it to return the
appropriate
All Samsung SoCs has max 3 i2s controllers. So the i2s secondary fifo
interface device id was named as samsung-i2s.4. Renaming this to
samsung-i2s-sec to support device tree in i2s driver.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
sound/soc/samsung/i2s.c | 31
Add support for device based discovery.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
.../devicetree/bindings/sound/samsung-i2s.txt | 63 ++
sound/soc/samsung/dma.c|3 +-
sound/soc/samsung/dma.h|1 +
This patch make the dma dev request operation compatible for both
DT and non-DT cases. It takes the all the arguments required for
dma_request_slave_channel and dma_request_channel. If the driver
is initiated via DT or non-DT the corresponding call will be made.
Signed-off-by: Padmavathi Venna
This patch modifies the SPI driver to use generic dma dt bindings
support. This passes all the required arguments to dma dev request
functon which in turn calls the dma_request_slave_channel or dma__
request_channel based on DT or non-DT respectively.
Signed-off-by: Padmavathi Venna
On Friday 18 January 2013 05:18 PM, Felipe Balbi wrote:
On Wed, Jan 16, 2013 at 08:30:56PM +0530, Kishon Vijay Abraham I wrote:
New platforms are being added which has multiple PHY's (of same type) and
which has multiple USB controllers. The binding information has to be
present in the PHY
Add device nodes for the three instances of i2s controllers in Exynos5
platforms. Enable instance i2s 0 for exynos5250 board and disable all
other i2s instances.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
arch/arm/boot/dts/exynos5250-smdk5250.dts | 14 ++
Add AUXDATA entries for i2s controller driver so as to set the device
name for clock lookups
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
arch/arm/mach-exynos/mach-exynos5-dt.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git
Add the basic device tree based lookup.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
.../bindings/sound/samsung,smdk-wm8994.txt | 14 ++
arch/arm/boot/dts/exynos5250-smdk5250.dts | 18 +++--
arch/arm/boot/dts/exynos5250.dtsi |6
This patch removes custom way of adding spi dma channels and
adds according to new generic DMA DT bindings.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi | 15 +--
1 files changed, 9 insertions(+), 6 deletions(-)
diff --git
Update Kconfig file to enable I2S,PCM audio for wm8994 and spdif on all
samsung platforms.
Signed-off-by: Sangsu Park sangsu4u.p...@samsung.com
Signed-off-by: Sangbeom Kim sbki...@samsung.com
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
sound/soc/samsung/Kconfig |6 +++---
1 files
Hi,
On Fri, Jan 18, 2013 at 03:10:42PM +0530, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB has to act in host mode or in device mode.
Writing to
On 01/17/2013 06:50 PM, David Gibson wrote:
On Thu, Jan 17, 2013 at 01:32:45PM -0500, Jerry Van Baren wrote:
Hi Scott, Kim, David,
[snip]
libfdt_env.h is where Kim typedef'ed fdt16_t, fdt32_t, fdt64_t
I suspect the original intent was to have libfdt.h be the file
that people #included.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
include/linux/dmaengine.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
index 8cd0e25..c88f302 100644
--- a/include/linux/dmaengine.h
+++
On Fri, Jan 18, 2013 at 03:10:43PM +0530, Kishon Vijay Abraham I wrote:
A seperate driver has been added to handle the usb part of control
module. A device for the above driver is created here, using the register
address information to be used by the driver for powering on the PHY and
for
Hi,
On Fri, Jan 18, 2013 at 03:10:45PM +0530, Kishon Vijay Abraham I wrote:
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Hi,
On Friday 18 January 2013 05:29 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 18, 2013 at 03:10:42PM +0530, Kishon Vijay Abraham I wrote:
Added a new driver for the usb part of control module. This has an API
to power on the USB2 phy and an API to write to the mailbox depending on
whether MUSB
On Friday 18 January 2013 05:32 PM, Felipe Balbi wrote:
Hi,
On Fri, Jan 18, 2013 at 03:10:45PM +0530, Kishon Vijay Abraham I wrote:
Start using the control module driver for powering on the PHY and for
writing to the mailbox instead of writing to the control module
registers on their own.
Hi,
On Fri, Jan 18, 2013 at 05:40:04PM +0530, kishon wrote:
+void omap_control_usb_host_mode(struct device *dev)
+{
+ u32 val;
+ struct omap_control_usb *control_usb = dev_get_drvdata(dev);
+
+ val = AVALID | VBUSVALID;
+
+ writel(val, control_usb-otghs_control);
I would like
Currently cfi_cmdset_0002.c does not support PPB locking of sectors. This
patch adds support for this locking/unlocking mechanism. It is needed on
some platforms, since newer U-Boot versions do support this PPB locking
and protect for example their environment sector(s) this way.
This PPB
This is minimal infrastructure needed for devicetree work.
It uses an a sample skeleton devicetree - embedded in kernel image -
to print the board, manufacturer by parsing the top-level compatible
string.
As of now we don't need any additional board specific machine_desc.
TODO: support
Hi,
On Tue, Dec 18, 2012 at 09:09:40PM +0530, Vivek Gautam wrote:
This patch-set enables the samsung-usbphy driver on exynos5250,
which enables the support for USB2 type and USB3 type phys.
The corresponding phy driver patches are available at:
1) https://lkml.org/lkml/2012/12/18/201
2)
On Fri, Jan 18, 2013 at 03:10:13PM +0200, Felipe Balbi wrote:
Hi,
On Tue, Dec 18, 2012 at 09:09:40PM +0530, Vivek Gautam wrote:
This patch-set enables the samsung-usbphy driver on exynos5250,
which enables the support for USB2 type and USB3 type phys.
The corresponding phy driver patches
On Fri, Jan 11, 2013 at 08:32:29PM +0530, Vivek Gautam wrote:
Adding the phy driver to ehci-s5p. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Missing
Hi,
On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
This patch adds host phy support to samsung-usbphy driver and
further adds support for samsung's exynos5250 usb-phy.
Signed-off-by: Praveen Paneri p.pan...@samsung.com
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Hi Felipe,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
This patch adds host phy support to samsung-usbphy driver and
further adds support for samsung's exynos5250 usb-phy.
Signed-off-by: Praveen Paneri
On Fri, Jan 18, 2013 at 07:51:08PM +0530, Vivek Gautam wrote:
Hi Felipe,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
This patch adds host phy support to samsung-usbphy driver and
further adds
HI Balbi,
On Fri, Jan 18, 2013 at 7:52 PM, Felipe Balbi ba...@ti.com wrote:
On Fri, Jan 18, 2013 at 07:51:08PM +0530, Vivek Gautam wrote:
Hi Felipe,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Jan 14, 2013 at 05:52:15PM +0530, Vivek Gautam wrote:
Hi Alan,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi ba...@ti.com wrote:
On Fri, Jan 11, 2013 at 08:32:29PM +0530, Vivek Gautam wrote:
Adding the phy driver to ehci-s5p. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek
Hi,
Add the needed DT sections for twl4030 and twl6030 for the PWM childs.
Update the omap4-sdp to have working backlight and keypad/charging LED support.
Use the pwm-leds driver on BeagleBoard for the pmu_stat LED instead of the hacky
twl403-gpio mapped PWM.
Regards,
Peter
---
Peter Ujfalusi
Enable support for the PWMs and LEDs as PWM drivers.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/twl4030.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index ed0bc95..d216853
Enable support for the PWMs and LED as PWM drivers.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/twl6030.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/twl6030.dtsi b/arch/arm/boot/dts/twl6030.dtsi
index 9996cfc..d9b8b21
We have proper driver stack to handle the pmu_stat LED which is connected
PWMB of twl4030.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap3-beagle-xm.dts | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git
Sections to describe the pwm-leds in the system.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
index 43e5258..8101a94
Section to describe the backlight for the LCD panels.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
index 8101a94..c2dee41
On Fri, Jan 18, 2013 at 07:59:52PM +0530, Vivek Gautam wrote:
HI Balbi,
On Fri, Jan 18, 2013 at 7:52 PM, Felipe Balbi ba...@ti.com wrote:
On Fri, Jan 18, 2013 at 07:51:08PM +0530, Vivek Gautam wrote:
Hi Felipe,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi ba...@ti.com wrote:
On Tue, Jan 8, 2013 at 8:32 AM, Laxman Dewangan ldewan...@nvidia.com wrote:
From: Pritesh Raithatha praitha...@nvidia.com
NVIDIA's Tegra114 added two more configuration parameter in pinmux i.e.
rcv-sel and drive type.
rcv-sel: Select between High and Normal VIL/VIH receivers.
On Tue, Jan 8, 2013 at 8:32 AM, Laxman Dewangan ldewan...@nvidia.com wrote:
From: Pritesh Raithatha praitha...@nvidia.com
This adds a driver for the Tegra114 pinmux, and required
parameterization data for Tegra114.
The driver uses the common Tegra pincontrol driver utility
functions to
On Fri, 11 Jan 2013, Vivek Gautam wrote:
Adding the phy driver to ehci-s5p. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Acked-by: Alan Stern
On Fri, 11 Jan 2013, Vivek Gautam wrote:
Adding the phy-driver to ohci-exynos. Keeping the platform data
for continuing the smooth operation for boards which still uses it
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Jingoo Han jg1@samsung.com
Acked-by: Alan Stern
On Fri, 18 Jan 2013, Vivek Gautam wrote:
Hi Alan,
On Fri, Jan 18, 2013 at 6:46 PM, Felipe Balbi ba...@ti.com wrote:
On Fri, Jan 11, 2013 at 08:32:29PM +0530, Vivek Gautam wrote:
Adding the phy driver to ehci-s5p. Keeping the platform data
for continuing the smooth operation for boards
On 01/03/2013 06:09 PM, Sylwester Nawrocki wrote:
From: Guennadi Liakhovetski g.liakhovet...@gmx.de
Add a V4L2 OF parser, implementing bindings documented in
Documentation/devicetree/bindings/media/video-interfaces.txt.
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
On 01/18/2013 06:24 AM, Vineet Gupta wrote:
This is minimal infrastructure needed for devicetree work.
It uses an a sample skeleton devicetree - embedded in kernel image -
to print the board, manufacturer by parsing the top-level compatible
string.
As of now we don't need any additional
Hi,
On Fri, Jan 18, 2013 at 02:30:21PM +0530, Praveen Paneri wrote:
Changes from v8:
Resending this patch series after rebasing to the latest usb-next branch.
Rewording inline comments for better readability.
Removed IS_ENABLED(CONFIG_OF) as pdev-dev.of_node is enough to check for dt
On Tue, Jan 8, 2013 at 10:43 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
+config PINCTRL_SUNXI
+ bool
+ select PINMUX
+ select GENERIC_PINCONF
Very nice that you use generic pinconf!
+++ b/drivers/pinctrl/pinctrl-sunxi.c
(...)
+ switch
Tony,
On Tue, Jan 15, 2013 at 3:03 PM, Tony Lindgren t...@atomide.com wrote:
* Daniel Mack zon...@gmail.com [130114 15:30]:
On Jan 15, 2013 2:06 AM, Tony Lindgren t...@atomide.com wrote:
* Ezequiel Garcia elezegar...@gmail.com [121223 13:49]:
On Fri, Dec 14, 2012 at 7:36 AM, Daniel Mack
On Wed, Jan 16, 2013 at 10:13 AM, Philipp Zabel p.za...@pengutronix.de wrote:
The SRC has auto-deasserting reset bits that control reset lines to
the GPU, VPU, IPU, and OpenVG IP modules. This patch adds a reset
controller that can be controlled by those devices using the
reset controller API.
* Ezequiel Garcia elezegar...@gmail.com [130118 11:43]:
Tony,
On Tue, Jan 15, 2013 at 3:03 PM, Tony Lindgren t...@atomide.com wrote:
* Daniel Mack zon...@gmail.com [130114 15:30]:
On Jan 15, 2013 2:06 AM, Tony Lindgren t...@atomide.com wrote:
* Ezequiel Garcia elezegar...@gmail.com
The Allwinner SoCs have an IP module that handle both the muxing and the
GPIOs.
This IP has 8 banks of 32 bits, with a number of pins actually useful
for each of these banks varying from one to another, and depending on
the SoC used on the board.
This driver only implements the pinctrl part, the
On Fri, Jan 18, 2013 at 6:11 PM, Tony Lindgren t...@atomide.com wrote:
* Ezequiel Garcia elezegar...@gmail.com [130118 11:43]:
Tony,
On Tue, Jan 15, 2013 at 3:03 PM, Tony Lindgren t...@atomide.com wrote:
* Daniel Mack zon...@gmail.com [130114 15:30]:
On Jan 15, 2013 2:06 AM, Tony Lindgren
On 01/19/2013 01:07 AM, Nobuhiro Iwamatsu wrote:
Hi,
Thomas, Thank you for the detailed explanation.
Ezequiel, I checked your patch on OpenBlocks AX3, work fine.
But I have a question. your patch arm: mvebu: Add support for USB
host controllers in Armada 370/XP
was set USB controller
85 matches
Mail list logo
