Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined with PHY and moving to the new framework
will break
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle.
This framework will be of use only to devices that uses external PHY (PHY
functionality is not embedded
Now that omap-usb2 is adapted to the new generic PHY framework,
*set_suspend* ops can be removed from omap-usb2 driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb-xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy device name) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
Used the generic PHY framework API to create the PHY. For powering on
and powering off the PHY, power_on and power_off ops are used. Once the
MUSB OMAP glue is adapted to the new framework, the suspend and resume
ops of usb phy library will be removed.
However using the old usb phy library cannot
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.
PHY drivers should create the PHY by
On Tuesday 25 June 2013 03:57 AM, Joel A Fernandes wrote:
Hi Tony,
Following branch breaks MMC for me on am33xx (beaglebone):
http://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git/log/?h=omap-for-v3.11/cleanup
I tried to work around it by specifying interrupt and reg property in
Hi Balaji,
Can you share your branch with edma + 3.11 cleanup, so that I can reproduce
this
issue.
g...@github.com:joelagnel/linux-kernel.git (branch dma-devel-mmc2)
Thanks,
Joel
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
* Joel A Fernandes agnel.j...@gmail.com [130624 15:33]:
Hi Tony,
Following branch breaks MMC for me on am33xx (beaglebone):
http://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git/log/?h=omap-for-v3.11/cleanup
I tried to work around it by specifying interrupt and reg property in
* Benoit Cousson b-cous...@ti.com [130624 07:42]:
Hi Tony,
On 06/24/2013 12:19 PM, Tony Lindgren wrote:
Hi,
For merging this series, I suggest the following sets:
* Joel A Fernandes joelag...@ti.com [130620 14:13]:
Joel A Fernandes (3):
edma: config: Enable config options
* Linus Walleij linus.wall...@linaro.org [130624 05:13]:
On Fri, Jun 21, 2013 at 5:03 PM, Grygorii Strashko
grygorii.stras...@ti.com wrote:
Hence, add pinctrl handling in omap_device core:
1) on PM runtime resume
- switch pinctrl state to default (todo: active)
2) on PM runtime suspend
* Sricharan R r.sricha...@ti.com [130624 07:39]:
Hi,
On Tuesday 18 June 2013 08:14 PM, Santosh Shilimkar wrote:
On Tuesday 18 June 2013 04:24 AM, Tony Lindgren wrote:
* Santosh Shilimkar santosh.shilim...@ti.com [130612 14:14]:
Add ramdisk fileystem related options which lets OMAP5 and
* Grant Likely grant.lik...@secretlab.ca [130624 09:00]:
On Mon, Jun 24, 2013 at 8:21 AM, Tony Lindgren t...@atomide.com wrote:
* Javier Martinez Canillas martinez.jav...@gmail.com [130623 18:08]:
On Mon, Jun 24, 2013 at 1:43 AM, Aaro Koskinen aaro.koski...@iki.fi
wrote:
Hi,
On
* Rajendra Nayak rna...@ti.com [130624 05:24]:
Hi,
Over the years the PRM and CM headers for OMAP have been growing largely
due to autogeneration which creates headers for complete PRM and
CM register space, regardless of the actual usage of these registers in
software.
Thanks for working
* Arnd Bergmann a...@arndb.de [130624 07:25]:
If we build a kernel with CONFIG_ARCH_OMAP2PLUS enabled but all of the
individual SoCs disabled, we run into a large number of link errors
because if incorrect dependencies:
arch/arm/mach-omap2/built-in.o: In function `_add_initiator_dep':
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano Coelho coe...@ti.com
---
I created a new directory under net to contain wireless bindings documentation.
The actual
On Tuesday 25 June 2013 12:44 PM, Tony Lindgren wrote:
Rajendra Nayak (4):
ARM: OMAP2: PRM/CM: Cleanup unused header contents
ARM: OMAP3: PRM/CM: Cleanup unused header contents
ARM: OMAP4: PRM/CM: Cleanup unused header contents
ARM: OMAP5: PRM/CM: Cleanup unused header contents
Hi Samuel,
-Original Message-
From: J, KEERTHY
Sent: Friday, June 21, 2013 2:38 PM
To: sa...@linux.intel.com
Cc: broo...@kernel.org; ldewan...@nvidia.com;
grant.lik...@secretlab.ca; swar...@nvidia.com; linux-
ker...@vger.kernel.org; linux-...@vger.kernel.org; g...@slimlogic.co.uk;
On Mon, Jun 24, 2013 at 11:49:44PM -0700, Tony Lindgren wrote:
* Joel A Fernandes agnel.j...@gmail.com [130624 15:33]:
Hi Tony,
Following branch breaks MMC for me on am33xx (beaglebone):
http://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git/log/?h=omap-for-v3.11/cleanup
Hi,
On Tue, Jun 25, 2013 at 11:35:30AM +0300, Luciano Coelho wrote:
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano Coelho coe...@ti.com
---
I created a new
The OMAP4 Blaze Tablet is TI OMAP4 processor-based
development platform in a tablet formfactor.
The platform contains many of the features found in
present-day handsets (such as audio, video, wireless
functions and user interfaces) and in addition
contains features for software development and
On Tue, Jun 25, 2013 at 8:04 AM, Tony Lindgren t...@atomide.com wrote:
* Grant Likely grant.lik...@secretlab.ca [130624 09:00]:
On Mon, Jun 24, 2013 at 8:21 AM, Tony Lindgren t...@atomide.com wrote:
* Javier Martinez Canillas martinez.jav...@gmail.com [130623 18:08]:
On Mon, Jun 24, 2013 at
On Tue, 2013-06-25 at 14:12 +0300, Felipe Balbi wrote:
On Tue, Jun 25, 2013 at 11:35:30AM +0300, Luciano Coelho wrote:
+- tcxoclock: the internal WLAN TCXO clock frequency (required for
+ WiLink7 not used for WiLink6 and WiLink8). Must be one of the
+ following:
+ 0 = 19.200 MHz
+
On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
The OMAP4 Blaze Tablet is TI OMAP4 processor-based
development platform in a tablet formfactor.
The platform contains many of the features found in
present-day handsets (such as audio, video, wireless
functions and user interfaces) and in addition
This patch creates a unique node for each clock in the OMAP4 power,
reset and clock manager (PRCM).
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/boot/dts/omap4-clocks.dtsi | 1692 +++
arch/arm/boot/dts/omap4.dtsi|2 +
2 files changed, 1694
The OMAP clock driver now supports DPLL clock type. This patch also
adds support for DT DPLL nodes.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
drivers/clk/omap/Makefile |2 +-
drivers/clk/omap/clk.c|1 +
drivers/clk/omap/dpll.c | 307
Hi,
Changes compared to previous version:
PATCH 2 - removed some unnecessary headers + module defs
- added Mike under copyright
PATCH 4 - fixed the copyright in the header file
PATCH 8 - removed a few incorrect comments from the data file
- moved /include/ for the clock DT file
Some of the clock.h contents are needed by the new OMAP clock driver,
including dpll_data and clk_hw_omap. Thus, move these to the generic
omap header file which can be accessed by the driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/clock.h | 150
Some devices require their clocks to be available with a specific
dev-id con-id mapping. With DT, the clocks can be found by default
only with their name, or alternatively through the device node of
the consumer. With drivers, that don't support DT fully yet, add
mechanism to register specific
This node adds support for a clock node which allows control to the
clockdomain enable / disable.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
drivers/clk/omap/Makefile |2 +-
drivers/clk/omap/clk.c|1 +
drivers/clk/omap/gate.c | 88 +
clk_get_sys / clk_get can now find clocks from device-tree. If a DT clock
is found, an entry is added to the clk_lookup list also for subsequent
searches.
Signed-off-by: Tero Kristo t-kri...@ti.com
Cc: Russell King li...@arm.linux.org.uk
---
drivers/clk/clkdev.c | 32
OMAP clk driver now routes some of the basic clocks through own
registration routine to allow autoidle support. This routine just
checks a couple of device node properties and adds autoidle support
if required, and just passes the registration forward to basic clocks.
Signed-off-by: Tero Kristo
Parses OMAP clock data from DT and registers those clocks with the clock
framework. dt_omap_clk_init must be called early during boot for timer
initialization so it is exported and called from the existing clock code
instead of probing like a real driver. Based on initial work done by
Mike
On 06/25/2013 07:01 AM, Nishanth Menon wrote:
On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
The OMAP4 Blaze Tablet is TI OMAP4 processor-based
development platform in a tablet formfactor.
The platform contains many of the features found in
present-day handsets (such as audio, video, wireless
On Tue, Jun 25, 2013 at 02:56:10PM +0300, Luciano Coelho wrote:
On Tue, 2013-06-25 at 14:12 +0300, Felipe Balbi wrote:
On Tue, Jun 25, 2013 at 11:35:30AM +0300, Luciano Coelho wrote:
+- tcxoclock: the internal WLAN TCXO clock frequency (required for
+ WiLink7 not used for WiLink6 and
On Tue, Jun 25, 2013 at 5:40 AM, Felipe Balbi ba...@ti.com wrote:
On Mon, Jun 24, 2013 at 11:49:44PM -0700, Tony Lindgren wrote:
* Joel A Fernandes agnel.j...@gmail.com [130624 15:33]:
Hi Tony,
Following branch breaks MMC for me on am33xx (beaglebone):
On 06/24/2013 10:34 PM, Alan Stern wrote:
On Mon, 24 Jun 2013, Roger Quadros wrote:
OK I've tried to handle all this in an alternate way. Now the controller
suspend/resume
and runtime suspend/resume is independent of bus suspend.
The controller now runtime suspends when all devices on the
On 06/25/2013 06:32 AM, Ruslan Bilovol wrote:
The OMAP4 Blaze Tablet is TI OMAP4 processor-based
development platform in a tablet formfactor.
The platform contains many of the features found in
present-day handsets (such as audio, video, wireless
functions and user interfaces) and in addition
On 6/25/2013 12:24 PM, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [130624 07:42]:
Hi Tony,
On 06/24/2013 12:19 PM, Tony Lindgren wrote:
Hi,
For merging this series, I suggest the following sets:
* Joel A Fernandes joelag...@ti.com [130620 14:13]:
Joel A Fernandes (3):
On Tuesday 25 June 2013 10:16 AM, Sekhar Nori wrote:
On 6/25/2013 12:24 PM, Tony Lindgren wrote:
* Benoit Cousson b-cous...@ti.com [130624 07:42]:
Hi Tony,
On 06/24/2013 12:19 PM, Tony Lindgren wrote:
Hi,
For merging this series, I suggest the following sets:
* Joel A Fernandes
Hi,
On 06/25/2013 02:38 PM, Tero Kristo wrote:
Hi,
Changes compared to previous version:
PATCH 2 - removed some unnecessary headers + module defs
- added Mike under copyright
PATCH 4 - fixed the copyright in the header file
PATCH 8 - removed a few incorrect comments from the
Hi,
On Tue, Jun 25, 2013 at 11:28:39AM +0530, Kishon Vijay Abraham I wrote:
diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
new file mode 100644
index 000..7abf573
--- /dev/null
+++ b/include/linux/phy/phy.h
on this header, how about adding phy_set_drvdata() and
On Tue, Jun 25, 2013 at 11:28:42AM +0530, Kishon Vijay Abraham I wrote:
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy device name) should be added in the platform
data of the controller.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
On Tue, Jun 25, 2013 at 11:28:40AM +0530, Kishon Vijay Abraham I wrote:
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
However using the old USB PHY library cannot be completely removed
On Tue, Jun 25, 2013 at 11:28:44AM +0530, Kishon Vijay Abraham I wrote:
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb-xceiv can't be removed as of now because
On Tue, Jun 25, 2013 at 11:28:43AM +0530, Kishon Vijay Abraham I wrote:
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding
On Tue, Jun 25, 2013 at 11:28:41AM +0530, Kishon Vijay Abraham I wrote:
Used the generic PHY framework API to create the PHY. For powering on
and powering off the PHY, power_on and power_off ops are used. Once the
MUSB OMAP glue is adapted to the new framework, the suspend and resume
ops of
On Tue, Jun 25, 2013 at 11:28:45AM +0530, Kishon Vijay Abraham I wrote:
Now that omap-usb2 is adapted to the new generic PHY framework,
*set_suspend* ops can be removed from omap-usb2 driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
On Tue, Jun 25, 2013 at 11:28:46AM +0530, Kishon Vijay Abraham I wrote:
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Reviewed-by: Felipe Balbi
Hi,
On Mon, Jun 17, 2013 at 05:23:17AM +, Paul Walmsley wrote:
Boot to userspace:
FAIL ( 3/12): 37xxevm, am335xbone, am335xbonelt
Paul, we have at least 2 different folks who can't reproduce your bone
and bone black boot to userspace failures. I wonder how you're trying to
boot them.
ping
On 23 June 2013 13:53, Naresh Kamboju naresh.kamb...@linaro.org wrote:
Hi,
panda build broken on linux-next branch
kernel_config=omap2plus_defconfig
KERNEL_VERSION=3.10.0-rc6
KERNEL_GIT=git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
On Tue, 25 Jun 2013, Roger Quadros wrote:
On 06/24/2013 10:34 PM, Alan Stern wrote:
On Mon, 24 Jun 2013, Roger Quadros wrote:
OK I've tried to handle all this in an alternate way. Now the controller
suspend/resume
and runtime suspend/resume is independent of bus suspend.
The
On Mon, Jun 24, 2013 at 05:35:18PM +0200, Javier Martinez Canillas wrote:
Ok, so something like the following patch should do it (tested on an
OMAP3 board):
From b9e262c688fb7f3ad733f140b55dddbc8e4716e6 Mon Sep 17 00:00:00 2001
From: Javier Martinez Canillas javier.marti...@collabora.co.uk
are here (booted via serial from the boot
ROM):
http://www.pwsan.com/tmp/boneblack-20130625/
Please let me know if you need more binaries shared from the test runs!
...
Am certainly open to the idea that there's something wrong with the way
that I'm booting either of these. But AFAIK no one's
On Mon, Jun 24, 2013 at 05:22:24PM +0300, Felipe Balbi wrote:
On Fri, Jun 21, 2013 at 01:59:08PM +0530, George Cherian wrote:
Do a release_mem_region of the hcd resource. Without this the
subsequent insertion of module fails in request_mem_region.
Signed-off-by: George Cherian
Santosh,
On Fri, 21 Jun 2013, Nishanth Menon wrote:
/*
* XXX Will depend on the process, validation, and binning
* for the currently-running IC. Use OMAP4 data for time being.
*/
#ifdef CONFIG_PM_OPP
omap5_voltdm_mpu.volt_data = omap446x_vdd_mpu_volt_data;
On 06/25/2013 02:20 PM, Paul Walmsley wrote:
+ Vaibhav and Kevin
Hi,
On Tue, 25 Jun 2013, Felipe Balbi wrote:
On Mon, Jun 17, 2013 at 05:23:17AM +, Paul Walmsley wrote:
Boot to userspace:
FAIL ( 3/12): 37xxevm, am335xbone, am335xbonelt
Paul, we have at least 2 different folks
(fixed the ARM mailing list address)
On Tue, 2013-06-25 at 11:35 +0300, Luciano Coelho wrote:
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano Coelho coe...@ti.com
(oh crap, now *really* fixed the ARM mailing list address)
On Tue, 2013-06-25 at 11:35 +0300, Luciano Coelho wrote:
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano
On Tuesday 25 June 2013 03:20 PM, Paul Walmsley wrote:
Santosh,
On Fri, 21 Jun 2013, Nishanth Menon wrote:
/*
* XXX Will depend on the process, validation, and binning
* for the currently-running IC. Use OMAP4 data for time being.
*/
#ifdef CONFIG_PM_OPP
Tom Rini tr...@ti.com writes:
On 06/25/2013 02:20 PM, Paul Walmsley wrote:
+ Vaibhav and Kevin
Hi,
On Tue, 25 Jun 2013, Felipe Balbi wrote:
On Mon, Jun 17, 2013 at 05:23:17AM +, Paul Walmsley wrote:
Boot to userspace:
FAIL ( 3/12): 37xxevm, am335xbone, am335xbonelt
Paul, we
On 15:55-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 03:20 PM, Paul Walmsley wrote:
Santosh,
On Fri, 21 Jun 2013, Nishanth Menon wrote:
/*
* XXX Will depend on the process, validation, and binning
* for the currently-running IC. Use OMAP4 data for time
On Tuesday 25 June 2013 03:57 PM, Nishanth Menon wrote:
On 15:55-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 03:20 PM, Paul Walmsley wrote:
Santosh,
On Fri, 21 Jun 2013, Nishanth Menon wrote:
/*
* XXX Will depend on the process, validation, and binning
On Tue, Jun 25, 2013 at 3:12 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Well having voltage data in voltage domain was not my decision ;-)
Instead of creating another set of dummy data, I just used what
is out there(OMAP4) with clear comment that data needs to be updated.
I don't
On 06/25/2013 03:57 PM, Kevin Hilman wrote:
Tom Rini tr...@ti.com writes:
On 06/25/2013 02:20 PM, Paul Walmsley wrote:
+ Vaibhav and Kevin
Hi,
On Tue, 25 Jun 2013, Felipe Balbi wrote:
On Mon, Jun 17, 2013 at 05:23:17AM +, Paul Walmsley wrote:
Boot to userspace:
FAIL ( 3/12):
On Tuesday 25 June 2013 04:17 PM, Nishanth Menon wrote:
On Tue, Jun 25, 2013 at 3:12 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Well having voltage data in voltage domain was not my decision ;-)
Instead of creating another set of dummy data, I just used what
is out there(OMAP4)
Hi,
On Tue, Jun 25, 2013 at 06:20:51PM +, Paul Walmsley wrote:
Am certainly open to the idea that there's something wrong with the way
that I'm booting either of these. But AFAIK no one's been able to
identify exactly what it could be. I haven't had the time recently to
spend hours
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Tuesday 25 June 2013 04:17 PM, Nishanth Menon wrote:
On Tue, Jun 25, 2013 at 3:12 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Well having voltage data in voltage domain was not my decision ;-)
Instead of creating another set of
On Tuesday 25 June 2013 04:56 PM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Tuesday 25 June 2013 04:17 PM, Nishanth Menon wrote:
On Tue, Jun 25, 2013 at 3:12 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Well having voltage data in voltage domain was
Naresh Kamboju naresh.kamb...@linaro.org writes:
ping
This is a known issue[1] and already has some proposed fixes, they are just
not merged yet.
Kevin
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/178209.html
On 23 June 2013 13:53, Naresh Kamboju
On 16:59-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 04:56 PM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Tuesday 25 June 2013 04:17 PM, Nishanth Menon wrote:
On Tue, Jun 25, 2013 at 3:12 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote
On Tuesday 25 June 2013 06:36 PM, Nishanth Menon wrote:
On 16:59-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 04:56 PM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Tuesday 25 June 2013 04:17 PM, Nishanth Menon wrote:
On Tue, Jun 25, 2013 at 3:12 PM
On 18:43-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 06:36 PM, Nishanth Menon wrote:
On 16:59-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 04:56 PM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Tuesday 25 June 2013 04:17 PM
On Tuesday 25 June 2013 07:02 PM, Nishanth Menon wrote:
On 18:43-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 06:36 PM, Nishanth Menon wrote:
On 16:59-20130625, Santosh Shilimkar wrote:
On Tuesday 25 June 2013 04:56 PM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim
...@ti.com
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Paul Walmsley p...@pwsan.com
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
---
Discussed in thread: http://marc.info/?t=13718466442r=1w=2
Tested against
linux-next-20130625 +
git://git.kernel.org/pub/scm/linux/kernel
On Tuesday 25 June 2013 07:56 PM, Nishanth Menon wrote:
commit 20d49e9ccfece526db755940721aa13e331936d4
(ARM: OMAP5: voltagedomain data: Add OMAP5 voltage domain data)
Introduced dummy volt data for OMAP5 with OMAP4460 voltage information.
However with the fixes introduced in later patches
Nishanth Menon n...@ti.com writes:
commit 20d49e9ccfece526db755940721aa13e331936d4
(ARM: OMAP5: voltagedomain data: Add OMAP5 voltage domain data)
Introduced dummy volt data for OMAP5 with OMAP4460 voltage information.
However with the fixes introduced in later patches
commit
From: Joel A Fernandes agnel.j...@gmail.com
Minor patches remaining after EDMA series has been merged:
First patch adds the TI_EDMA option which people can forget to add and
can result in failure without any informative errors of why DMA is not
working.
Second patch adds comments to the EDMA
From: Joel A Fernandes agnel.j...@gmail.com
This series is fixes to get MMC working on AM33XX without HWMOD data.
On removal of HWMOD data, interrupt and register properties need to be provided
for the driver to function correctly.
Also instead of specifying offset in match-data, I've added
From: Matt Porter mpor...@ti.com
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
Acked-by: Arnd Bergmann a...@arndb.de
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 26
From: Joel A Fernandes agnel.j...@gmail.com
HWMOD irq entries for MMC were removed. We provide the same from DT for MMC.
This fixes issue where memory resource could not be found during probe.
Also, added the reg-offset property to account for the offset from start.
Signed-off-by: Joel A
From: Joel A Fernandes agnel.j...@gmail.com
A new reg-offset property was added to account for register offsets
in some omap-hsmmc's. Document the new property.
Signed-off-by: Joel A Fernandes agnel.j...@gmail.com
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt |3 +++
1 file
From: Joel A Fernandes agnel.j...@gmail.com
Some omap_hsmmc's need to start from a particular offset but
otherwise are same and can be reused. Let the DT tell us about
the HW difference, check for the reg-offset property and use
the same in the driver.
Signed-off-by: Joel A Fernandes
From: Matt Porter mpor...@ti.com
Adds AM33XX MMC support for am335x-bone, am335x-evm, and
am335x-evmsk.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/boot/dts/am335x-bone.dts |7 +++
arch/arm/boot/dts/am335x-evm.dts |7 +++
From: Joel A Fernandes agnel.j...@gmail.com
Build EDMA in my default to avoid fewer people stepping on their toes
with broken DMA on drivers needing EDMA.
Signed-off-by: Joel A Fernandes agnel.j...@gmail.com
---
arch/arm/configs/omap2plus_defconfig |1 +
1 file changed, 1 insertion(+)
diff
From: Joel A Fernandes agnel.j...@gmail.com
Minor patches remaining after EDMA series has been merged:
First patch adds the TI_EDMA option which people can forget to add and
can result in failure without any informative errors of why DMA is not
working.
Second patch adds comments to the EDMA
From: Joel A Fernandes agnel.j...@gmail.com
A-sync case in EDMA driver is tricky and not so obvious.
Document the reasons for the calculations and the scenarious
they are used.
Signed-off-by: Joel A Fernandes agnel.j...@gmail.com
---
drivers/dma/edma.c | 22 ++
1 file
On Wed, Jun 26, 2013 at 06:55:01, Fernandes, Joel wrote:
From: Joel A Fernandes agnel.j...@gmail.com
A new reg-offset property was added to account for register offsets
in some omap-hsmmc's. Document the new property.
Small nitpick
I usually get feedback that any driver DT changes and the
-Original Message-
From: linux-arm-kernel [mailto:linux-arm-kernel-
boun...@lists.infradead.org] On Behalf Of Kevin Hilman
Sent: Wednesday, June 26, 2013 1:28 AM
To: Rini, Tom
Cc: Paul Walmsley; linux-omap@vger.kernel.org; linux-arm-
ker...@lists.infradead.org; Balbi, Felipe;
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Paul Walmsley
Sent: Tuesday, June 25, 2013 11:51 PM
To: Balbi, Felipe
Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
Rini, Tom; Hiremath,
93 matches
Mail list logo
