Hi,
-Ursprüngliche Nachricht-
Von: linux-usb-ow...@vger.kernel.org
[mailto:linux-usb-ow...@vger.kernel.org] Im Auftrag von Paul Walmsley
Gesendet: Mittwoch, 19. September 2012 03:24
An: Maximilian Schwerin
Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org
Betreff: Re: USB
On Wednesday 19 September 2012 09:37 PM, Pantelis Antoniou wrote:
#include linux/pm_runtime.h
+#include linux/pinctrl/consumer.h
+#include linux/err.h
err.h include may be removed.
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
Hi,
On Tue, 2012-09-18 at 16:41 +, Marc Murphy wrote:
Hello all,
I have been moving from the ti 2.6.37 BSP to the 3.x kernel with quite a bit
of success, the main issue I have at the moment is trying to get the frame
buffer and any displays I have initialised.
[2.805358] omapfb
On Tue, 2012-08-21 at 13:39 +0300, Tomi Valkeinen wrote:
Hi,
On Wed, 2012-08-15 at 15:16 -0400, Raphael Assenat wrote:
On our AM3505 based board, dpi.c complains that there is no VDSS_DSI
regulator
and the framebuffer cannot be enabled. However, this check does not seem to
apply to
Tony,
Here is the pull request which enables the architected cpu local timer
support for OMAP5 devices.
The following changes since commit 5698bd757d55b1bb87edd1a9744ab09c142abfc2:
Linux 3.6-rc6 (2012-09-16 14:58:51 -0700)
are available in the git repository at:
(With fixed git URL)
On Wed, Sep 19, 2012 at 1:21 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Tony,
Here is the pull request which enables the architected cpu local timer
support for OMAP5 devices.
The following changes since commit
5698bd757d55b1bb87edd1a9744ab09c142abfc2:
On Tue, Sep 18, 2012 at 11:23 PM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120917 23:07]:
On Tue, Sep 18, 2012 at 3:09 AM, Tony Lindgren t...@atomide.com wrote:
* Tony Lindgren t...@atomide.com [120917 14:39]:
* Benoit Cousson b-cous...@ti.com
Hi,
This series contains patches that change how omapdss's panel devices
(omap_dss_device) are initialized and registered. There are two patches that
change behaviour, the rest should be just cleanups:
The patch omap_dss_register_device() doesn't take display index affects the
number for the
Add function dss_get_default_display_name() which returns the name of
the default display, given from the board file or via module parameters.
The default display name can be used by output drivers to decide which
display is the wanted one.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
We used to have all the displays of the board in one list, and we made a
displayX directory in the sysfs, where X was the index of the display
in the list.
This doesn't work anymore with device tree, as there's no single list to
get the number from, and it doesn't work very well even with non-DT
We have boards with multiple panel devices connected to the same
physical output, of which only one panel can be enabled at one time.
Examples of these are Overo, where you can use different daughter boards
that have different LCDs, and 3430SDP which has an LCD and a DVI output
and a physical
Add error handling to dss_init_device(), which has, for some reason,
been missing.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/core.c|4 +++-
drivers/video/omap2/dss/display.c | 23 ++-
drivers/video/omap2/dss/dss.h |2 +-
HDMI and VENC outputs always use the DIGIT output from DISPC. The dssdev
struct contains channel field which is used to specify the DISPC
output for the display, but this was not used for HDMI and VENC.
This patch fills the channel field explicitely for HDMI and VENC
displays so that we can
We currently create omap_dss_devices statically in board files, and use
those devices directly in the omapdss driver. This model prevents us
from having the platform data (which the dssdevs in board files
practically are) as read-only, and it's also different than what we will
use with device
Cleanup dss_recheck_connections, move and rename it to a static
dss_init_connections function inside display.c. Improve the function to
return errors, and implement a matching dss_uninit_connections that can
be used to free the mgr-dssdev link.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
dss_recheck_connections is quite a mess. With the previous commit that
initializes the channel field for HDMI and VENC displays, we can greatly
simplify the dss_recheck_connections.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/overlay.c | 49
Hi Samuel,
On 09/19/2012 03:24 AM, Samuel Ortiz wrote:
Hi Peter,
On Mon, Sep 10, 2012 at 01:46:18PM +0300, Peter Ujfalusi wrote:
Hello,
Generated on top of:
git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git topic/omap
I applied the first 8 patches, but I'd like to get Mark's ACK
Hi
On Sep 19, 2012, at 10:09 AM, Shubhrajyoti wrote:
On Wednesday 19 September 2012 09:37 PM, Pantelis Antoniou wrote:
#include linux/pm_runtime.h
+#include linux/pinctrl/consumer.h
+#include linux/err.h
err.h include may be removed.
Right, Updated patch series (without the message patch
Pinctrl-fy the OMAP I2C driver.
Due to the requirement of early usage of I2C for
regulators and such, earlier initialization of pinctrl
is required.
This patch series is against
git://gitorious.org/linus-tree/linus-tree.git for_3.7/i2c/big_cleanups
Note that the I2C DT bindings are against the
Add support for pinctrl mux settings in the OMAP I2C driver.
If no such pinctl bindings are found a warning message is printed.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
drivers/i2c/busses/i2c-omap.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
When using pinctrl-single to handle i2c initialization, it has
to be done early.
On the beaglebone the regulator is connected to the i2c0 bus,
and for sure that's the case for many other am33xx boards.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
On Tue, 2012-09-18 at 22:25 +, Paul Walmsley wrote:
Hi Tero,
just looking at the usecounting series to see what is mergeable and
noticed this:
On Fri, 13 Jul 2012, Tero Kristo wrote:
Secondly, there are multiple erratas for omap3, which say that the
wakedeps should be enabled
Add twl6030-usb data node in twl6030 device tree file. twl6030-usb is the
comparator driver for USB that detects VBUS and ID events. The dt data is
comprised of two interrupts, one for ID and one for VBUS and a phandle to the
regulator.
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Kishon
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
Add twl4030-usb data node in twl4030 device tree file. twl4030-usb is the phy
driver for MUSB used in omap3 chipsets. The dt data is comprised of two
interrupts, one for ID and one for VBUS and three phandles to regulator.
Acked-by: Felipe Balbi ba...@ti.com
Signed-off-by: Kishon Vijay Abraham I
This patch series adds dt data to get MUSB working in omap4 and omap3
Changes from v2:
* Changes the subject of all the patches to include ARM: dts:
* Added reg property and interrupt property for usb_otg_hs. Previously these
were obtained from ti,hwmods property.
* Rebased on
On Wednesday 12 September 2012 14:45:44 Omar Ramirez Luna wrote:
If included without IOMMU_API being selected it will break
compilation:
arch/arm/plat-omap/include/plat/iommu.h:
In function 'dev_to_omap_iommu':
arch/arm/plat-omap/include/plat/iommu.h:148:
error: 'struct
Hello,
The following two patch is needed for the twl6040 GPO driver (going via MFD
tree) to work correctly.
Regards,
Peter
---
Peter Ujfalusi (2):
ARM/dts: omap4-sdp: Enable GPO functionality for twl6040
ARM/dts: omap4-panda: Enable GPO functionality for twl6040
Add the needed properties for twl6040 so the GPO functionality can be used
by other drivers.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-sdp.dts
Add the needed properties for twl6040 so the GPO functionality can be used
by other drivers.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-panda.dts
Hi Benoit,
On Sep 18, 2012, at 10:24 PM, a0919096 wrote:
Hi Panto,
That patch is good, but a similar one was already posted by Florian.
https://patchwork.kernel.org/patch/1392671/
Checking the email thread it seems that Wolfram pulled it.
Regards,
Benoit
Great. One less
On Thu, Sep 20, 2012 at 12:04 PM, Pantelis Antoniou
pa...@antoniou-consulting.com wrote:
Add support for pinctrl mux settings in the OMAP I2C driver.
If no such pinctl bindings are found a warning message is printed.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
looks
Hi Peter,
On Thu, Aug 16, 2012 at 03:13:12PM +0300, Peter Ujfalusi wrote:
Hello,
Changes since v1:
- Removed the ti,use-gpo property from DT bindings
- Register the GPO driver if we booted with DT blob or in legacy if the pdata
for the GPO driver is present
- DT binding Documentation
On Tuesday 18 September 2012, Mitch Bradley wrote:
There is a delicious irony here with respect to Shark. Shark has real
Open Firmware. It's the platform that I used for the first OFW port to
ARM. We (the Shark design team) had a version of NetBSD that would run
on Shark without any native
Hi Peter,
On Thu, Aug 16, 2012 at 03:13:12PM +0300, Peter Ujfalusi wrote:
Hello,
Changes since v1:
- Removed the ti,use-gpo property from DT bindings
- Register the GPO driver if we booted with DT blob or in legacy if the pdata
for the GPO driver is present
- DT binding Documentation
Hi Keshava,
On Mon, Jul 16, 2012 at 07:01:06PM +0530, Keshava Munegowda wrote:
The TLL (Transceiver Less Link) is an separate IP block, independent of
the host controller. Basically this TLL operates like USB PHY which allows
the user to connect two USB transceiver interfaces together directly
Added a driver for usb3 phy that handles the interaction between usb phy
device and dwc3 controller. Currently writing to control module register
is taken care in this driver which will be removed once the control
module driver is in place.
Also included the patch from Moiz to fix gadget pullup
usb_otg_ss_refclk960m is needed by 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
---
Documentation/devicetree/bindings/usb/usb-phy.txt |3 +++
drivers/usb/phy/omap-usb2.c
From: Moiz Sonasath m-sonas...@ti.com
For the gadget pullup functionality to work in
SS mode it requires a particular sequence of
toggling the run-stop bit. Here is the required
sequence:
- Set DCTL[31]
- Clear DCTL[31]
- Clear OMAP5430_CONTROL_CORE__PHY_POWER_USB[14]
- Clear DCTL[8:5] = 0x00
-
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
Power-cycling the PHY (partially) decreases the number of transitions to
Recovery state. Hence changed the power up sequence to a partial
power-up before a full power-up of the PHY.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Signed-off-by: Moiz Sonasath m-sonas...@ti.com
---
On Tue, Sep 18, 2012 at 5:02 PM, Felipe Balbi ba...@ti.com wrote:
On Tue, Sep 18, 2012 at 06:10:50PM +0530, Sourav Poddar wrote:
Greg's tty-next is not booting on 2420 based N800. The failure is
observed at serial init itself. The reason might be that n800 tries to
resume even though it is not
Hi,
On Wed, Sep 19, 2012 at 05:00:27PM +0530, Kishon Vijay Abraham I wrote:
From: Moiz Sonasath m-sonas...@ti.com
For the gadget pullup functionality to work in
SS mode it requires a particular sequence of
toggling the run-stop bit. Here is the required
sequence:
- Set DCTL[31]
- Clear
On Wed, Sep 19, 2012 at 05:00:28PM +0530, Kishon Vijay Abraham I wrote:
Power-cycling the PHY (partially) decreases the number of transitions to
Recovery state. Hence changed the power up sequence to a partial
power-up before a full power-up of the PHY.
Signed-off-by: Kishon Vijay Abraham I
On Wed, Sep 19, 2012 at 05:00:29PM +0530, Kishon Vijay Abraham I wrote:
usb_otg_ss_refclk960m is needed by 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
---
Hello,
Here's the second version of my tidspbridge MMU-related cleanup patches. The
first version has been sent privately only, don't try to search the mailing
list archive for it :-)
Replacing hw/hw_mmu.c and part of core/tiomap3430.c with generic IOMMU calls
should be less difficult now.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/staging/tidspbridge/hw/hw_mmu.c | 95 +--
1 files changed, 39 insertions(+), 56 deletions(-)
diff --git
The hw_mmu_tlb_flush() function is unused, and the mmu_flush_entry()
function is used by hw_mmu_tlb_flush() only. Remove them both.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/staging/tidspbridge/hw/hw_mmu.c |
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/staging/tidspbridge/core/tiomap3430.c | 1123 -
1 files changed, 537 insertions(+), 586 deletions(-)
diff --git
Most function that takes a device context as argument immediately assign
it to a local variable of the same type and use the local variable.
Remove the variable and use the function parameter directly. Rename all
remaining occurences of dev_context to dev_ctxt to be consistent with
the rest of the
The same block of code is used in two places to release pages. Factor it
out to a function.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/staging/tidspbridge/core/tiomap3430.c | 81 ++---
1
Several local variables just hold copies of function arguments.
Remove them and use the function arguments directly.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/staging/tidspbridge/core/tiomap3430.c | 60
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/staging/tidspbridge/core/tiomap3430.c |4
drivers/staging/tidspbridge/hw/hw_mmu.h |1 -
2 files changed, 0 insertions(+), 5 deletions(-)
diff --git
There's no need to prefix all u32 variables with ul_.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/staging/tidspbridge/core/tiomap3430.c | 183 -
1 files changed, 87 insertions(+), 96
From: Omar Ramirez Luna omar.l...@linaro.org
If included without IOMMU_API being selected it will break
compilation:
arch/arm/plat-omap/include/plat/iommu.h:
In function 'dev_to_omap_iommu':
arch/arm/plat-omap/include/plat/iommu.h:148:
error: 'struct dev_archdata' has no member
Both headers make use of externally defined structures, types or
functions. Include the appropriate headers.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
arch/arm/plat-omap/include/plat/iommu.h |4
arch/arm/plat-omap/include/plat/iopgtable.h |2 ++
2
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/staging/tidspbridge/core/tiomap3430.c | 148 +++-
1 files changed, 68 insertions(+), 80 deletions(-)
diff --git
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/staging/tidspbridge/core/io_sm.c |7 +-
drivers/staging/tidspbridge/core/tiomap3430.c | 38 +++-
drivers/staging/tidspbridge/core/tiomap_io.c |2 +-
Physical addresses: name them 'pa' and use the phys_addr_t type
MPU virtual addresses: name them 'va' and use the unsigned long type
DSP virtual addresses: name them 'da' and use the u32 type
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/staging/tidspbridge/core/tiomap3430.c | 83 ---
drivers/staging/tidspbridge/core/ue_deh.c |8 +--
VMAs marked with the VM_PFNMAP flag have no struct page associated with
the memory PFNs. Don't call get_page()/put_page() on the pages
supposedly associated with the PFNs.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Reviewed-by: Omar Ramirez Luna omar.rami...@ti.com
---
On Tue, Sep 18, 2012 at 07:12:52PM +0100, Nicolas Pitre wrote:
On Tue, 18 Sep 2012, Lorenzo Pieralisi wrote:
ARM v7 architecture introduced the concept of cache levels and related
control registers. New processors like A7 and A15 embed an L2 unified cache
controller that becomes part of
Hi,
This version - v7 as compared to previous version, takes care of
rounding issues due to the usage of nanoseconds in generic timing
routine. All calculations are now in picoseconds. Once all timings
are calculated it is converted to nanoseconds so that calculated
timing values are compatible
Helper function for updating nand platform data has been
added the capability to take timing structure arguement.
Usage of omap_nand_flash_init() has been replaced by modifed
one, omap_nand_flash_init was doing things similar to
board_nand_init except that NAND CS# were being acquired
based on
gpmc_cs_set_timings() calculate ticks to be programmed by
rounding time in ns to next tick value. Hence remove
redundant rounding of nanosecond timing.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/gpmc-nand.c | 30 +-
1 file changed, 13
Configure busturnaround, cycle2cycledelay, waitmonitoringtime,
clkactivationtime in gpmc_cs_set_timings(). This is done so
that boards can configure these parameters of gpmc in Kernel
instead of relying on bootloader. Also configure bool type
timings like extradelay.
This needed change to the
Refactor set_async_mode set_sync_mode functions to
separate out timing calculation actual configuration
(GPMC OneNAND side).
Thanks to Jon for his suggestions.
Signed-off-by: Afzal Mohammed af...@ti.com
Reviewed-by: Jon Hunter jon-hun...@ti.com
---
v6:
1. Set OneNAND part to async
From: Jon Hunter jon-hun...@ti.com
A platform function pointer for getting the frequency of a OneNAND device
was added so that a platform could specify a custom function for returning
the frequency and not just rely on the OneNAND version to determine the
frequency. However, this platform
Newer IP's have wr_access and wr_data_mux_bus fields. Use
IP revision values to determine availability of these
fields and hence decide on whether to configure them.
Signed-off-by: Afzal Mohammed af...@ti.com
Reviewed-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 12
Divider value for a certain sync clk is determined solely
based on gpmc fclk. CS# does not have any role here, thus
remove presence of CS# in clock divider calculation API.
Signed-off-by: Afzal Mohammed af...@ti.com
Reviewed-by: Jon Hunter jon-hun...@ti.com
---
arch/arm/mach-omap2/gpmc-onenand.c
Presently there are three peripherals that gets it timing
by runtime calculation. Those peripherals can work with
frequency scaling that affects gpmc clock. But timing
calculation for them are in different ways.
Here a generic runtime calculation method is proposed. Input
to this function were
Generic gpmc timing calculation helper is available now, use
it instead of custom timing calculation.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/gpmc-onenand.c | 124 +
1 file changed, 43 insertions(+), 81 deletions(-)
diff --git
Generic gpmc timing calculation helper is available now, use
it instead of custom timing calculation.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/gpmc-smc91x.c | 43 ---
1 file changed, 17 insertions(+), 26 deletions(-)
diff --git
Generic gpmc timing calculation helper is available now, use
it instead of custom timing calculation.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/usb-tusb6010.c | 182 +
1 file changed, 44 insertions(+), 138 deletions(-)
diff --git
Hi Tony,
On Tue, Sep 18, 2012 at 04:40:02, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [120917 15:54]:
Can you please try with the attached patch ?
Gave it a quick try and it seemed to work.. But when I tried
rebasing my patches for the cbus to keep things working with
On Tue, Sep 18, 2012 at 05:35:33PM +0100, Lorenzo Pieralisi wrote:
In processors like A15/A7 L2 cache is unified and integrated within the
processor cache hierarchy, so that it is not considered an outer cache
anymore. For processors like A15/A7 flush_cache_all() ends up cleaning
all cache
On Fri, Sep 14, 2012 at 05:41:56PM -0500, Jon Hunter wrote:
...
Typo nits in the binding examples below...
Documentation/devicetree/bindings/dma/dma.txt | 81 +
drivers/of/Makefile |2 +-
drivers/of/dma.c | 219
Some semicolons were left out in the examples.
Signed-off-by: Matt Porter mpor...@ti.com
---
Documentation/devicetree/bindings/dma/dma.txt |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/dma/dma.txt
On Tue, Sep 18, 2012 at 05:35:32PM +0100, Lorenzo Pieralisi wrote:
This patch renames jump labels in v7_flush_dcache_all in order to define
a specific flush cache levels entry point.
TODO: factor out the level flushing loop if considered worthwhile and
define the input registers
On Fri, Sep 14, 2012 at 05:41:56PM -0500, Jon Hunter wrote:
diff --git a/Documentation/devicetree/bindings/dma/dma.txt
b/Documentation/devicetree/bindings/dma/dma.txt
new file mode 100644
index 000..a4f59a5
--- /dev/null
+++ b/Documentation/devicetree/bindings/dma/dma.txt
@@ -0,0 +1,81
On 09/14/2012 05:41 PM, Jon Hunter wrote:
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
[snip]
Reviewed-by: Arnd Bergmann a...@arndb.de
Reviewed-by: Nicolas
On Wednesday 19 September 2012, Matt Porter wrote:
+Optional properties:
+- #dma-channels: Number of DMA channels supported by the controller.
+- #dma-requests: Number of DMA requests signals supported by the
+ controller.
Shouldn't these two optional
On 09/19/2012 09:24 AM, Arnd Bergmann wrote:
On Wednesday 19 September 2012, Matt Porter wrote:
+Optional properties:
+- #dma-channels: Number of DMA channels supported by the controller.
+- #dma-requests: Number of DMA requests signals supported by the
+
On Wed, Sep 19, 2012 at 09:36:36AM -0500, Rob Herring wrote:
On 09/19/2012 09:24 AM, Arnd Bergmann wrote:
On Wednesday 19 September 2012, Matt Porter wrote:
+Optional properties:
+- #dma-channels: Number of DMA channels supported by the controller.
+- #dma-requests: Number of DMA
On 09/19/2012 01:30 PM, Kishon Vijay Abraham I wrote:
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.
On 9/19/2012 7:09 PM, Arnd Bergmann wrote:
On Tuesday 18 September 2012, Mitch Bradley wrote:
There is a delicious irony here with respect to Shark. Shark has real
Open Firmware. It's the platform that I used for the first OFW port to
ARM. We (the Shark design team) had a version of NetBSD
On 09/19/2012 01:56 PM, Felipe Balbi wrote:
On Wed, Sep 19, 2012 at 05:00:29PM +0530, Kishon Vijay Abraham I wrote:
usb_otg_ss_refclk960m is needed by 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
On Wed, Sep 19, 2012 at 04:45:01PM +0200, Marc Kleine-Budde wrote:
On 09/19/2012 01:56 PM, Felipe Balbi wrote:
On Wed, Sep 19, 2012 at 05:00:29PM +0530, Kishon Vijay Abraham I wrote:
usb_otg_ss_refclk960m is needed by usb2 phy present in omap5. For
omap4, the clk_get of this clock will fail
Some semicolons were left out in the examples.
The #dma-channels and #dma-requests properties have a prefix
that is, by convention, reserved for cell size properties.
Rename those properties to dma-channels and dma-requests.
Signed-off-by: Matt Porter mpor...@ti.com
---
On Tuesday 18 September 2012, Peter Ujfalusi wrote:
I thought I have replied to this...
Whichever way you prefer. I can craft a series to clean up the plat/mcbsp.h
usage and move the mcbsp header via ASoC tree.
I'm also fine if you do the move.
Let me know what you prefer.
I think I'll
On 09/19/2012 04:42 PM, Felipe Balbi wrote:
On Wed, Sep 19, 2012 at 04:45:01PM +0200, Marc Kleine-Budde wrote:
On 09/19/2012 01:56 PM, Felipe Balbi wrote:
On Wed, Sep 19, 2012 at 05:00:29PM +0530, Kishon Vijay Abraham I wrote:
usb_otg_ss_refclk960m is needed by usb2 phy present in omap5. For
On Wednesday 19 September 2012, Matt Porter wrote:
On Wed, Sep 19, 2012 at 09:36:36AM -0500, Rob Herring wrote:
On 09/19/2012 09:24 AM, Arnd Bergmann wrote:
On Wednesday 19 September 2012, Matt Porter wrote:
+Optional properties:
+- #dma-channels: Number of DMA channels supported
On Monday 17 September 2012, Tony Lindgren wrote:
* Santosh Shilimkar santosh.shilim...@ti.com [120914 02:21]:
OMAP interconnect drivers are used for the interconnect error handling.
Since they are bus driver, lets move it to newly created drivers/bus.
Cc: Arnd Bergmann a...@arndb.de
On Wed, Sep 19, 2012 at 7:58 AM, Arnd Bergmann a...@arndb.de wrote:
On Monday 17 September 2012, Tony Lindgren wrote:
* Santosh Shilimkar santosh.shilim...@ti.com [120914 02:21]:
OMAP interconnect drivers are used for the interconnect error handling.
Since they are bus driver, lets move it
On Wednesday 19 September 2012, Matt Porter wrote:
Some semicolons were left out in the examples.
The #dma-channels and #dma-requests properties have a prefix
that is, by convention, reserved for cell size properties.
Rename those properties to dma-channels and dma-requests.
From: Jerome Kurtz jrm.ku...@gmail.com
When I try to compile with TWL6030_USB=y, TWL4030_USB=y and
USB_MUSB_OMAP2PLUS=m, I get the following error:
drivers/built-in.o: In function `twl4030_usb_irq':
/home/xxx/kernel/linux/drivers/usb/otg/twl4030-usb.c:518: undefined
reference to
Hi Matthias,
On Tue, Sep 18, 2012 at 10:05:07PM +0200, Matthias Kaehlcke wrote:
The MFD API probably allows you to do exactly that by defining a specific
cell
for bl. Could you please try to use this API or otherwise justify not using
it?
you seem to have missed v3 of the patch which
Hi Aaro,
On Wed, Aug 29, 2012 at 12:34:24AM +0300, Aaro Koskinen wrote:
Retu is a multi-function device found on Nokia Internet Tablets
implementing at least watchdog, RTC, headset detection and power button
functionality.
This patch implements a minimum functionality providing only
Hi Aaro,
On Mon, Sep 03, 2012 at 11:23:23PM +0300, Aaro Koskinen wrote:
Retu is a multi-function device found on Nokia Internet Tablets
implementing at least watchdog, RTC, headset detection and power button
functionality.
This patch implements minimum functionality providing register
On Wed, 19 Sep 2012, Maximilian Schwerin wrote:
They're BeagleBoard XM clones. We're still trying to find out what the
real problem is. The problem persists across three separate layouts
using the same USB device and application. We're currently trying to see
if this is related to MUSB
1 - 100 of 186 matches
Mail list logo
