This patch series adds device tree support for NAND flash in am335x-evm.
Also ELM node is populated in device tree and been used for BCH error
correction in NAND flash part. Also this patch series ensures RBL ecc
layout maintained in Linux kernel with BCH8 ecc scheme.
This patch series based on
From: Philip, Avinash avinashphi...@ti.com
Add ELM data node to AM33XX device tree file.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Acked-by: Peter Korsgaard jac...@sunsite.dk
---
Changes since v2:
- Replace xx literals to 52
- remove tab
arch/arm/boot/dts/am33xx.dtsi |
From: Philip, Avinash avinashphi...@ti.com
Add GPMC data node to AM33XX device tree file.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Acked-by: Peter Korsgaard jac...@sunsite.dk
---
Changes since v2:
- Change number of chip select to 7
arch/arm/boot/dts/am33xx.dtsi | 12
NAND flash connected in am335x-evm on GPMC controller. This patch adds
device tree node in am3355-evm with GPMC contoller timing for NAND flash
interface, NAND partition table, ECC scheme, elm handle id.
Signed-off-by: Philip Avinash avinashphi...@ti.com
---
arch/arm/boot/dts/am335x-evm.dts |
On Thu, Jan 24, 2013 at 10:44:50AM +0530, Leela Krishna Amudala wrote:
Steffen,
You can add my tested-by for this series.. :)
I have been using them for Exynos: smdk5250 board.
Thanks. I'll use that opportunity for a v17 that is rebased onto 3.8-rc4.
Regards,
Steffen
On Wed, Jan 23,
Philip == Philip Avinash avinashphi...@ti.com writes:
Philip As part of removing generalized dependency, replace xx
Philip literal fields in DT compatible field with 52 for am335x
Philip platforms.
Acked-by: Peter Korsgaard jac...@sunsite.dk
--
Bye, Peter Korsgaard
Add wdt DT node and OF_DEV_AUXDATA for wdt driver in
da850 board dt file to use wdt clock.
This series applies on top of v3.8-rc4.
This is tested on da850 EVM.
Test Procedure:
$watchdog -F /dev/watchdog (Device should not reboot)
After wdt heartbeat timeout(DEFAULT_HEARTBEAT is 60 sec)
$ctr +
Add da850 wdt DT node.
Signed-off-by: Kumar, Anil anilkuma...@ti.com
---
:100644 100644 37dc5a3... 4666ce9... M arch/arm/boot/dts/da850-evm.dts
:100644 100644 640ab75... 08bf974... M arch/arm/boot/dts/da850.dtsi
arch/arm/boot/dts/da850-evm.dts |3 +++
arch/arm/boot/dts/da850.dtsi|5
Add OF_DEV_AUXDATA for wdt driver in da850 board dt
file to use wdt clock.
Signed-off-by: Kumar, Anil anilkuma...@ti.com
---
:100644 100644 37c27af... 1b295d2... M arch/arm/mach-davinci/da8xx-dt.c
arch/arm/mach-davinci/da8xx-dt.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
Hi Steffen,
On Thu, Jan 24, 2013 at 13:49:58, Steffen Trumtrar wrote:
Thanks. I'll use that opportunity for a v17 that is rebased onto 3.8-rc4.
As you are going to have a v17, if you can fold the diff[1]
(that I mentioned earlier) into the patch,
fbmon: add of_videomode helpers, it would be
Hi linux-mtd, Artem, David,
Ping?
It's been a month, and this is a simple uninitialized pointer dereference bug
fix.
baruch
On Sun, Dec 23, 2012 at 01:10:50PM +0200, Baruch Siach wrote:
Commit d68cbdd4fb (mtd: physmap_of: allow to specify the mtd name for retro
compatiblity) broke cmdline
From: Lad, Prabhakar prabhakar@ti.com
add OF support for the tvp514x driver.
Signed-off-by: Lad, Prabhakar prabhakar@ti.com
Cc: Hans Verkuil hans.verk...@cisco.com
Cc: Laurent Pinchart laurent.pinch...@ideasonboard.com
Cc: Mauro Carvalho Chehab mche...@redhat.com
Cc: Guennadi
On Wed, Jan 23, 2013 at 21:18:12, Mark Brown wrote:
On Wed, Jan 23, 2013 at 12:39:35PM +, Hebbar, Gururaja wrote:
On Fri, Jan 04, 2013 at 17:56:12, Mark Brown wrote:
The CODEC driver biases should be changed over to be supplies, this
makes the above much more natural - the routing
Peter Chen peter.c...@freescale.com writes:
On Tue, Nov 27, 2012 at 05:16:55PM +0100, Michael Grzeschik wrote:
Nearly every SoC from Freescale has this non-core usb registers. This series
adds support for more users of this driver.
This series is based on Peter Chen's work. Its needed to
On Thu, Jan 24, 2013 at 09:33:34AM +, Hebbar, Gururaja wrote:
So, by just using the SND_SOC_DAPM_POST_PMU SND_SOC_DAPM_PRE_PMD I can mask
handle one particular voltage.
What makes you say that? That is just not true.
signature.asc
Description: Digital signature
On Thu, Jan 24, 2013 at 15:32:55, Mark Brown wrote:
On Thu, Jan 24, 2013 at 09:33:34AM +, Hebbar, Gururaja wrote:
So, by just using the SND_SOC_DAPM_POST_PMU SND_SOC_DAPM_PRE_PMD I can
mask
handle one particular voltage.
What makes you say that? That is just not true.
What I
Hello Prabhakar,
On 24.01.2013 10:12, Prabhakar Lad wrote:
From: Lad, Prabhakar prabhakar@ti.com
add OF support for the tvp514x driver.
Signed-off-by: Lad, Prabhakar prabhakar@ti.com
Cc: Hans Verkuil hans.verk...@cisco.com
Cc: Laurent Pinchart laurent.pinch...@ideasonboard.com
On Thu, Jan 24, 2013 at 10:06:42AM +, Hebbar, Gururaja wrote:
What I meant was that by using this macro (SND_SOC_DAPM_POST_PMU
SND_SOC_DAPM_PRE_PMD) I can just save and restore existing voltage values
inside
the event. They will not be user configurable (available to user through some
Hi Sylwester,
Thanks for the patch.
On Wednesday 23 January 2013 20:31:16 Sylwester Nawrocki wrote:
From: Guennadi Liakhovetski g.liakhovet...@gmx.de
This patch adds a document describing common OF bindings for video
capture, output and video processing devices. It is curently mainly
Hi Heiko,
On Thu, Jan 24, 2013 at 4:30 PM, Heiko Schocher h...@denx.de wrote:
Hello Prabhakar,
On 24.01.2013 10:12, Prabhakar Lad wrote:
From: Lad, Prabhakar prabhakar@ti.com
add OF support for the tvp514x driver.
Signed-off-by: Lad, Prabhakar prabhakar@ti.com
Cc: Hans Verkuil
On Thu, Jan 24, 2013 at 15:43:03, Mark Brown wrote:
On Thu, Jan 24, 2013 at 10:06:42AM +, Hebbar, Gururaja wrote:
What I meant was that by using this macro (SND_SOC_DAPM_POST_PMU
SND_SOC_DAPM_PRE_PMD) I can just save and restore existing voltage values
inside
the event. They will
Hi Prabhakar,
Thank you for the patch.
Sylwester and Guennadi have posted a DT bindings proposal for V4L2 devices.
Shouldn't you base this patch on those bindings ?
On Thursday 24 January 2013 14:42:20 Prabhakar Lad wrote:
From: Lad, Prabhakar prabhakar@ti.com
add OF support for the
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 Sat, Dec 15, 2012 at 11:21:36PM +0900, Mark Brown wrote:
On Fri, Dec 14, 2012 at 09:06:49AM -0700, Stephen Warren wrote:
On 12/13/2012 10:50 PM, Naveen Krishna Chatradhi wrote:
+The first should be an output, and is used to claim the I2C bus,
+the second should be an input, and
Hi Simon,
On Monday 21 January 2013 09:38:28 Simon Horman wrote:
On Tue, Jan 15, 2013 at 10:10:19AM +0900, Simon Horman wrote:
On Sat, Jan 12, 2013 at 06:18:54PM +0100, Guennadi Liakhovetski wrote:
On Wed, 9 Jan 2013, Laurent Pinchart wrote:
Support device instantiation through the
On Thu, Jan 24, 2013 at 12:13:29PM +0100, Wolfram Sang wrote:
On Sat, Dec 15, 2012 at 11:21:36PM +0900, Mark Brown wrote:
also get things like read operations which appear as multiple
transactions on the I2C bus so require something higher level than what
multi-master provides.
I don't
Hi Guennadi,
On Saturday 12 January 2013 18:18:54 Guennadi Liakhovetski wrote:
On Wed, 9 Jan 2013, Laurent Pinchart wrote:
Support device instantiation through the device tree. The compatible
property is used to select the SoC pinmux information.
Set the gpio_chip device field to the
Hi Mike,
On Thu, Jan 24, 2013 at 01:52:04, Mike Turquette wrote:
Quoting Afzal Mohammed (2013-01-23 03:48:56)
+static inline void da8xx_fb_clkc_enable(void)
+{
if (lcd_revision == LCD_VERSION_2)
lcdc_write(LCD_V2_DMA_CLK_EN | LCD_V2_LIDD_CLK_EN |
On Thu, Jan 24, 2013 at 07:18:47PM +0800, Mark Brown wrote:
On Thu, Jan 24, 2013 at 12:13:29PM +0100, Wolfram Sang wrote:
On Sat, Dec 15, 2012 at 11:21:36PM +0900, Mark Brown wrote:
also get things like read operations which appear as multiple
transactions on the I2C bus so require
Hi Laurent,
On Thu, Jan 24, 2013 at 4:17 PM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Prabhakar,
Thank you for the patch.
Sylwester and Guennadi have posted a DT bindings proposal for V4L2 devices.
Shouldn't you base this patch on those bindings ?
Yes I'll base on it
Hi Kishon,
On Wed, Jan 23, 2013 at 19:56:37, ABRAHAM, KISHON VIJAY wrote:
On Wednesday 23 January 2013 07:28 PM, Mohammed, Afzal wrote:
USB first instance of am335x works in mainline as of now.
Can you check if this series indeed breaks am335x?
Thanks for your help.
Do you have a tree
On Thu, Jan 24, 2013 at 04:25:19PM +0530, Vishwanathrao Badarkhe, Manish wrote:
---
arch/arm/boot/dts/tps6507x.dtsi | 47
+++
Why are you putting this in arch/arm?
signature.asc
Description: Digital signature
+ Peter who did the original PWM
Hi Florian,
On 01/23/2013 06:56 PM, Florian Vaussard wrote:
Hello Benoit,
This patchset adds some new DT supports to the Overo products.
The first patch converts the PMIC LEDB output to use the pwm-leds,
newly merged in your branch for_3.9/dts. The second
On Sun, Jan 06, 2013 at 09:00:59PM +0100, Julia Lawall wrote:
The function davinci_i2c_remove in drivers/i2c/busses/i2c-davinci.c
contains the following code:
put_device(pdev-dev);
clk_disable_unprepare(dev-clk);
clk_put(dev-clk);
dev-clk = NULL;
Hi Santosh,
On 01/23/2013 11:55 AM, Santosh Shilimkar wrote:
Looping Marc, Benoit
On Wednesday 23 January 2013 04:06 PM, Mark Rutland wrote:
On Tue, Jan 22, 2013 at 10:05:18PM +, Kukjin Kim wrote:
Mark Rutland wrote:
+ devicetree-discuss, Grant Likely, Rob Herring and Tony Lindgren
On Thursday 24 January 2013 06:12 PM, Benoit Cousson wrote:
Hi Santosh,
On 01/23/2013 11:55 AM, Santosh Shilimkar wrote:
Looping Marc, Benoit
On Wednesday 23 January 2013 04:06 PM, Mark Rutland wrote:
On Tue, Jan 22, 2013 at 10:05:18PM +, Kukjin Kim wrote:
Mark Rutland wrote:
+
Hi Benoit,
On 24/01/13 12:42, Benoit Cousson wrote:
Hi Santosh,
On 01/23/2013 11:55 AM, Santosh Shilimkar wrote:
Looping Marc, Benoit
On Wednesday 23 January 2013 04:06 PM, Mark Rutland wrote:
On Tue, Jan 22, 2013 at 10:05:18PM +, Kukjin Kim wrote:
Mark Rutland wrote:
+
Using chip specific compatible string as it should be.
So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
which till now used a generic 'exynos' in their compatible strings.
Changes from v1:
- Changing compatible string from samsung,exynos5250-dwc3 to
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
Reviewed-by: Doug Anderson diand...@chromium.org
---
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
Reviewed-by: Doug Anderson diand...@chromium.org
---
On Thu, Jan 24, 2013 at 7:15 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Using chip specific compatible string as it should be.
So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
which till now used a generic 'exynos' in their compatible strings.
Changes from v1:
-
On 01/23/2013 10:18 PM, Alexander Shiyan wrote:
This patch adds a device tree vendor prefix for Cirrus Logic, Inc.
Signed-off-by: Alexander Shiyan shc_w...@mail.ru
---
Applied. Thanks.
Rob
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
Hi,
On 01/23/2013 06:56 PM, Florian Vaussard wrote:
Convert the on-board LED connected to the TWL4030 (LEDB) to use
pwm-leds.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
Hi,
On 01/23/2013 06:56 PM, Florian Vaussard wrote:
Add the needed sections to enable audio support on Overo.
Looks fine for me.
Reviewed-by: Peter Ujfalusi peter.ujfal...@ti.com
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/omap3-overo.dtsi | 14
Hi Peter,
diff --git a/arch/arm/boot/dts/omap3-overo.dtsi
b/arch/arm/boot/dts/omap3-overo.dtsi
index 89808ce..800be29 100644
--- a/arch/arm/boot/dts/omap3-overo.dtsi
+++ b/arch/arm/boot/dts/omap3-overo.dtsi
@@ -14,12 +14,13 @@
/include/ omap3.dtsi
/ {
- leds {
-
On 01/24/2013 04:42 PM, Florian Vaussard wrote:
I did it at first, but the led API executes in atomic context, where the
pwm-twl-led driver uses i2c communication. Setting a trigger will result in a
kernel panic.
Now that you mentioned it, this might be true.
I am working on a patch for
If an ethernet PHY can be reset by a GPIO, it can be specified in DT. Add
a binding and code to parse it, request the GPIO and take the PHY out of
reset.
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
Cc: devicetree-discuss@lists.ozlabs.org
Cc: net...@vger.kernel.org
---
Signed-off-by: Guennadi Liakhovetski g.liakhovet...@gmx.de
---
.../devicetree/bindings/vendor-prefixes.txt|2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
On Thu, 24 Jan 2013, Vivek Gautam wrote:
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
Reviewed-by: Doug Anderson
Jon,
David informed me the master is generally stable enough to consume
True.
but I'd feel more comfortable using an official DTC release.
It's in the works. I have a few more patch I'll apply first for sure.
(At least 1 through 3 of the recent 6 patch series.)
One additional item I
I did it at first, but the led API executes in atomic context, where the
pwm-twl-led driver uses i2c communication. Setting a trigger will result in a
kernel panic.
Now that you mentioned it, this might be true.
[c0013204] (unwind_backtrace+0x0/0xec) from [c00348ac]
Quoting Mohammed, Afzal (2013-01-24 03:36:02)
Hi Mike,
On Thu, Jan 24, 2013 at 01:52:04, Mike Turquette wrote:
Quoting Afzal Mohammed (2013-01-23 03:48:56)
+static inline void da8xx_fb_clkc_enable(void)
+{
if (lcd_revision == LCD_VERSION_2)
On 01/24/2013 05:50 PM, Florian Vaussard wrote:
I did it at first, but the led API executes in atomic context, where the
pwm-twl-led driver uses i2c communication. Setting a trigger will result in
a
kernel panic.
Now that you mentioned it, this might be true.
[c0013204]
This patch adds the driver for the PTN3460 LVDS/DP bridge chip.
The driver allows the EDID emulation to be selected from device tree,
along with specifying the GPIOs driving powerdown and reset pins.
The chip has a bug in it such that when the powerdown and reset pins
are toggled, the hotplug
Hi Laurent,
Thanks for the review.
On 01/24/2013 11:16 AM, Laurent Pinchart wrote:
[...]
+Data interfaces on all video devices are described by their child 'port'
+nodes. Configuration of a port depends on other devices participating in
+the data transfer and is described by 'endpoint'
Signed-off-by: Marek Belisko marek.beli...@open-nandra.com
---
arch/arm/boot/dts/omap3-gta04.dts | 94 +
1 file changed, 94 insertions(+)
create mode 100644 arch/arm/boot/dts/omap3-gta04.dts
diff --git a/arch/arm/boot/dts/omap3-gta04.dts
Hi,
On Tuesday 22 January 2013 07:39 PM, Roger Quadros wrote:
On 01/22/2013 11:58 AM, Kishon Vijay Abraham I wrote:
New PHY lib APIs like usb_add_phy_dev() and devm_usb_get_phy_dev() are
used in MUSB (OMAP), in order to make use of the binding information
provided in the board file (of OMAP
On Thu, Jan 24, 2013 at 05:14:13AM +, Sekhar Nori wrote:
Matt,
On 1/24/2013 3:07 AM, Matt Porter wrote:
On Wed, Jan 23, 2013 at 10:21:42AM +0800, Mark Brown wrote:
On Tue, Jan 22, 2013 at 09:26:34PM +0530, Sekhar Nori wrote:
On 1/16/2013 2:02 AM, Matt Porter wrote:
This series
On Thu, Jan 24, 2013 at 05:12:05AM +, Shilimkar, Santosh wrote:
On Thursday 24 January 2013 02:19 AM, Matt Porter wrote:
On Wed, Jan 23, 2013 at 04:37:55PM +0530, Santosh Shilimkar wrote:
Matt,
On Wednesday 16 January 2013 02:02 AM, Matt Porter wrote:
[..]
This series adds DMA
Hi
I am working on a patch for pwm-twl-led to defer using a workqueue right now.
Great!
The only thing I worry about is the latency we are going to get with the
workqueue.
If the latency becomes critical, we can create our own workqueue.
Hrm, when we handled the led via gpio-leds it
On Thu, Jan 24, 2013 at 7:09 PM, Sean Paul seanp...@chromium.org wrote:
This patch adds the driver for the PTN3460 LVDS/DP bridge chip.
The driver allows the EDID emulation to be selected from device tree,
along with specifying the GPIOs driving powerdown and reset pins.
The chip has a bug
On Thu, Jan 24, 2013 at 07:15:30PM +0530, Vivek Gautam wrote:
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
On Thu, Jan 24, 2013 at 4:22 PM, Daniel Vetter dan...@ffwll.ch wrote:
On Thu, Jan 24, 2013 at 7:09 PM, Sean Paul seanp...@chromium.org wrote:
This patch adds the driver for the PTN3460 LVDS/DP bridge chip.
The driver allows the EDID emulation to be selected from device tree,
along with
On Thu, Jan 24, 2013 at 02:47:10AM +0900, Dongjin Kim wrote:
Added device tree support for usb3503 driver and add new document with device
tree binding information.
Signed-off-by: Dongjin Kim tobet...@gmail.com
---
Documentation/devicetree/bindings/usb/usb3503.txt | 20 +
Hi,
On Thu, Jan 24, 2013 at 01:32:13PM -0800, Greg KH wrote:
On Thu, Jan 24, 2013 at 07:15:30PM +0530, Vivek Gautam wrote:
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam
Hi Sylwester,
On Thursday 24 January 2013 19:30:10 Sylwester Nawrocki wrote:
On 01/24/2013 11:16 AM, Laurent Pinchart wrote:
[...]
+Data interfaces on all video devices are described by their child 'port'
+nodes. Configuration of a port depends on other devices participating in
+the
On Thursday, January 24, 2013 10:45 PM, Vivek Gautam wrote
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
On Thursday, January 24, 2013 10:45 PM, Vivek Gautam wrote
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
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
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 ++
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 +++
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.
Also added an API to power on usb3 phy (omap5).
Writing to control module registers for doing the
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. The information about this data node is availabe @
Documentation/devicetree/bindings/usb/usb-phy.txt
Acked-by: Felipe Balbi ba...@ti.com
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 23, 2013 at 01:01:58PM +0200, Pantelis Antoniou wrote:
On Jan 23, 2013, at 7:12 AM, David Gibson wrote:
On Tue, Jan 22, 2013 at 01:08:04PM +0200, Pantelis Antoniou wrote:
Hi
On Jan 22, 2013, at 5:50 AM, David Gibson wrote:
On Fri, Jan 04, 2013 at 09:31:10PM +0200,
On Thu, Jan 24, 2013 at 12:17:32PM +0100, Laurent Pinchart wrote:
Hi Simon,
On Monday 21 January 2013 09:38:28 Simon Horman wrote:
On Tue, Jan 15, 2013 at 10:10:19AM +0900, Simon Horman wrote:
On Sat, Jan 12, 2013 at 06:18:54PM +0100, Guennadi Liakhovetski wrote:
On Wed, 9 Jan 2013,
Apologies for the delay in sending this version.
Added a driver for usb3 phy that handles the interaction between usb phy
device and dwc3 controller.
Changes from v2:
* used control module driver APIs to write to control module register.
* Added pm_runtime_put and pm_runtime_disable in the usb3
usb_otg_ss_refclk960m is needed for usb2 phy present in omap5. For
omap4, the clk_get of this clock will fail since it does not have this
clock.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/phy/omap-usb2.c | 28 +++-
1 file changed, 27
Added a driver for usb3 phy that handles the interaction between usb phy
device and dwc3 controller.
This also includes device tree support for usb3 phy driver and
the documentation with device tree binding information is updated.
Currently writing to control module register is taken care in
The runtime API's takes care of setting the SYSCONFIG register with
appropriate values. Hence explicit writes to SYSCONFIG register is
removed.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c | 26 --
1 file changed, 26 deletions(-)
Add an API in the omap glue layer to write to the mailbox register which
can be used by comparator driver(twl). To pass the detection of the attached
device (signified by VBUS, ID) to the dwc3 core, dwc3 core has to write
to the mailbox regiter.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Used device_for_each_child() to handle child device (dwc3 core) removal
during devexit of dwc3 omap. This is in preparation for creating the child
devices from subnode of dwc3 omap glue using of_platform_populate.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Now that we have drivers for omap-usb2 phy and omap-usb3 phy, stop
using nop-usb-xceiv.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c | 67 --
1 file changed, 67 deletions(-)
diff --git
Before accessing any register, runtime API's should be invoked to enable
the clocks. runtime API's are added here to prevent abort during register
access.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c | 10 ++
1 file changed, 10 insertions(+)
Used of_platform_populate() to create dwc3 core platform_device
from device tree data.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c | 40 ++--
1 file changed, 10 insertions(+), 30 deletions(-)
diff --git
Includes few minor fixes in dwc3-omap like populating the compatible
string in a correct way, extracting the utmi-mode property properly and
changing the index of get_irq since irq of core is removed from hwmod
entry.
Also updated the documentation with dwc3-omap device tree binding
information.
omap5 is not going to have support for non-dt boot making the platform
data associated with dwc3 useless. Removed it here.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c| 24 ++--
include/linux/platform_data/dwc3-omap.h |
Added dt support for dwc3 core and update the documentation with
device tree binding information. Getting a PHY is now done using
devm_usb_get_phy_by_phandle() for dt boot.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
Documentation/devicetree/bindings/usb/dwc3.txt | 22
Enabled the USB2 and USB3 PHY in probe by calling usb_phy_set_suspend
and disabled the PHYs on driver removal. When PM is implemented this
will be optimized to enable the PHYs only when needed.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/core.c |6 ++
1 file
No functional change. Stray statements where removed from dwc3 core.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/dwc3/core.c |3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index af189d5..ee1fa18 100644
---
used devres API while allocating resources so that these resources are
released automatically on driver detach.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/otg/palmas-usb.c | 47 ++
1 file changed, 15 insertions(+), 32
This includes a series of patches that should be used for testing
dwc3 in omap5.
Among other changes, palmas is made as a comparator driver
to the phy. And includes a fix to get a regulator by having phandle.
This patch series is developed on
git://github.com/rrnayak/linux.git
Whenever palmas detects a VBUS or ID event, the mailbox API in dwc3 glue
is called. The mailbox API takes care of notifying it to the core.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Signed-off-by: Moiz Sonasath m-sonas...@ti.com
---
drivers/usb/otg/palmas-usb.c | 32
The calls to regulator enable/disable was done unconditionally which
might result in warn dumps if *no_control_vbus* is set. So always call
regulator enable/disable on valid regulator.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/otg/palmas-usb.c | 17 +
palmas-usb is made as a comparator driver to omap usb2 phy, so that
omap usb can make use of palmas for srp and also to set vbus.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/otg/palmas-usb.c | 20 ++--
include/linux/mfd/palmas.h |3 +++
2 files
regulator_get is passing the device pointer of the parent (palmas)
instead of the child (palmas-usb). It's been fixed here.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/otg/palmas-usb.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
properies like wakeup and no_control_vbus can be represented in boolean,
so read those properties using of_property_read_bool.
Also updated the documentation with device tree binding information for
palmas-usb.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
commit 696c5c04 (USB: Palmas OTG Transceiver Driver) introduced empty
palmas_vbus_irq/palmas_id_irq with only *palmas_usb* declaration.
Removed these unnecessary functions.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/otg/palmas-usb.c | 38
1 - 100 of 115 matches
Mail list logo
