Benoit,
On Monday 26 August 2013 11:06 AM, Keerthy wrote:
The Patch adds nodes for TPS659038 PMIC for DRA7 boards.
It is based on top of:
http://comments.gmane.org/gmane.linux.ports.arm.omap/102459.
Documentation: Documentation/devicetree/bindings/mfd/palmas.txt
Documentation
Hi,
There are a couple of options here.
On Tuesday 03 September 2013 06:14 AM, Sid Boyce wrote:
The Pandaboard list seems dormant so I am seeking help here.
The previous kernel with HDMI video output was 3.2.7x5.
I built and installed this new kernel with this xorg.conf, it does not
work.
Sec
On Thu, Aug 29, 2013 at 06:05:41PM -0500, Joel Fernandes wrote:
> Process SG-elements in batches of MAX_NR_SG if they are greater
> than MAX_NR_SG. Due to this, at any given time only those many
> slots will be used in the given channel no matter how long the
> scatter list is. We keep track of how
The Pandaboard list seems dormant so I am seeking help here.
The previous kernel with HDMI video output was 3.2.7x5.
I built and installed this new kernel with this xorg.conf, it does not
work.
Section "Device"
Identifier "fb0"
Driver "omapfb"
Option "fb" "/dev/fb0
Here are some basic OMAP test results for Linux v3.11.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.11/20130902150604/
Test summary
Build: zImage:
Pass ( 1/ 1): omap2plus_defconfig
Build: uImage:
Pass (14/14): n800_multi_omap2xxx, n800_only_a,
On 8/29/2013 7:21 PM, Santosh Shilimkar wrote:
> On Thursday 29 August 2013 09:50 AM, Rajendra Nayak wrote:
>> On Thursday 29 August 2013 07:01 PM, Santosh Shilimkar wrote:
>>> On Thursday 29 August 2013 09:26 AM, Sekhar Nori wrote:
On 8/29/2013 4:53 PM, Rajendra Nayak wrote:
> diff --git
Adapted dwc3 core to use the Generic PHY Framework. So for init, exit,
power_on and power_off the following APIs are used phy_init(), phy_exit(),
phy_power_on() and phy_power_off().
However using the old USB phy library wont be removed till the PHYs of all
other SoC's using dwc3 core is adapted to
There can be systems which does not have a external usb_phy, so get
usb_phy only if usb-phy property is added in the case of dt boot or if
platform_data indicates the presence of PHY. Also remove checking if
return value is -ENXIO since it's now changed to always enable usb_phy layer.
Signed-off-b
Since now we have a separate folder for phy, move the PHY dt binding
documentation of OMAP to that folder.
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/{usb/usb-phy.txt => phy/omap-phy.txt}|2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename Documentation
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap5.dtsi |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 94abef5..9fe71ff 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/om
Adapted omap-usb3 PHY driver to Generic PHY Framework and moved phy-omap-usb3
driver in drivers/usb/phy to drivers/phy and also renamed the file to
phy-omap-pipe3 since this same driver will be used for SATA PHY and
PCIE PHY.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bin
No functional change. Moved omap_usb.h from linux/usb/ to linux/phy/.
Also removed the unused members of struct omap_usb (after phy-omap-pipe3
started using it's own header file)
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-omap-usb2.c |2 +-
drivers/usb/phy/phy-twl603
renamed struct omap_control_usb to struct omap_control_phy since it can
be used to control PHY of USB, SATA and PCIE. Also moved the driver and
include files under *phy* and made the corresponding changes in the users
of phy-omap-control.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/Kco
Modified dwc3 core to find PHYs only if the platform indicates that it has
to use a PHY. Adapted DWC3 and USB3 PHY to use Generic PHY framework. Also
changed the name of USB3 PHY driver to PIPE3 PHY driver since the same driver
has to be used for SATA and PCIE too.
This series also includes a bunc
Add AM335x prcm node with reset binding.
Signed-off-by: Afzal Mohammed
---
arch/arm/boot/dts/am33xx.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 4701e3c..c2ccf94 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b
Add AM4372 prcm node with reset binding.
Signed-off-by: Afzal Mohammed
---
arch/arm/boot/dts/am4372.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
index 5a68fde..d0d11b3 100644
--- a/arch/arm/boot/dts/am4372.dtsi
+++ b
AM43x, AM335x have reset block as part of prcm, let reset driver be
usable with these SoC's.
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index 3eed000..fa28d1d 100644
Driver to handle reset block in prcm of AM43x, AM335x SoC's. There are
three reset's that can be handled by this reset driver - gfx, m3 and
pruss. Of this only gfx has been handled here, adding support for the
remaining only require adding array entries with details of pruss and
m3.
Signed-off-by:
prcm reset binding for AM43x/AM335x SoC's.
This was started with an attempt to add reset binding without a clear
idea on the device node where binding should appear. So a new node
with compatible "am4372-reset" to represent reset managment in prcm
was added. But finally ended up with a node to rep
Enhance reset framework with "is_reset" and "clear_reset" api's.
is_reset - used by client driver to know reset status
clear_reset - used by client driver to clear reset status
These functionalities may sometimes be achieved by using existing api
like deassert. But in some scenarios, steps to achi
Hi,
This is an attempt to achieve reset on AM43x/AM335x based SoC's with
reset driver making use of the reset framework.
prcm node is added in device tree, which would hold reset bindings.
Initially node was made as a one that represents reset functionality
of SoC. but ended up with node for prcm
On 8/30/2013 4:35 AM, Joel Fernandes wrote:
> Manual trigger for events missed as a result of splitting a
> scatter gather list and DMA'ing it in batches. Add a helper
> function to trigger a channel incase any such events are missed.
>
> Signed-off-by: Joel Fernandes
Acked-by: Sekhar Nori
Tha
On Thu, 2013-08-29 at 18:05 -0500, Joel Fernandes wrote:
> The following series adds support to EDMA driver to enable DMA of
> scatter-gather lists of arbitrary length, but still make use of only
> a certain MAX number of slots at a time for a given channel. Thus
> free-ing up the rest of the slots
On 22/08/13 00:07, Laurent Pinchart wrote:
Thanks for the comments!
>> The exception to the above are DSI and DBI. DSI and DBI are combined control
>> and video busses, but the use of the busses for control purposes is not
>> independent of the video stream. Also, the the busses are, in practice,
On 9/2/2013 12:25 PM, Kuninori Morimoto wrote:
Hi
Sorry for my many response.
No Issues. and thanks for the review.
This patch series
- removes the irq_demux_work
- Uses devm_request_threaded_irq
- Call the user handler iff gpio_to_irq is done.
v1 --> v2
Sp
Hi Michael,
On 08/30/2013 08:59 PM, Michael Trimarchi wrote:
> Hi Roger
>
> On Thu, Jul 4, 2013 at 10:53 AM, Michael Trimarchi
> wrote:
>> Hi
>>
>> On 07/02/2013 05:03 PM, Roger Quadros wrote:
>>>
>>> On 07/02/2013 05:49 PM, Michael Trimarchi wrote:
Hi Roger
On 07/02/2013 04:42 PM
26 matches
Mail list logo
