Hi Benoit,
On Tuesday 15 October 2013 12:19 PM, Benoit Cousson wrote:
Hi Lokesh,
On 12/10/2013 15:26, Lokesh Vutla wrote:
Hi Benoit,
On Thursday 29 August 2013 06:22 PM, Lokesh Vutla wrote:
Add the AM33xx RNG module's device tree data.
Also add Documentation file describing the data
for
On Wed, Oct 16, 2013 at 2:47 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
The OMAP GPIO driver keeps track about GPIO pins that are
used as IRQ lines for two reasons:
1) To prevent GPIO banks to be disabled while one of their
GPIO pins are only used as an interrupt
On 10/16/2013 10:06 AM, Linus Walleij wrote:
On Wed, Oct 16, 2013 at 2:47 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
The OMAP GPIO driver keeps track about GPIO pins that are
used as IRQ lines for two reasons:
1) To prevent GPIO banks to be disabled while one of
+ Rob and Mark
On Tuesday 15 October 2013 12:19 PM, Benoit Cousson wrote:
Hi Lokesh,
On 12/10/2013 15:26, Lokesh Vutla wrote:
Hi Benoit,
On Thursday 29 August 2013 06:22 PM, Lokesh Vutla wrote:
Add the AM33xx RNG module's device tree data.
Also add Documentation file describing the data
On Tuesday 15 October 2013 10:30 PM, Nishanth Menon wrote:
Currently, i2c1 and i2c5 defer probe due to pinctrl dependencies.
This changes the i2c ID each bus is registered with in i2c-dev
interface.
As a result of this, many userspace tools break and there is no
consistent manner to fix the
On Tue, Oct 08, 2013 at 12:04:09PM -0700, Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [130920 06:33]:
This driver provides kernel-side support for the Random Number
Generator hardware found on OMAP34xx processors.
This driver comes from Maemo 2.6.28 kernel and was tested on
On 10/16/2013 06:37 AM, Rajendra Nayak wrote:
On Tuesday 15 October 2013 10:30 PM, Nishanth Menon wrote:
Currently, i2c1 and i2c5 defer probe due to pinctrl dependencies.
This changes the i2c ID each bus is registered with in i2c-dev
interface.
As a result of this, many userspace tools break
Hi Kishon,
On 10/15/2013 10:54 PM, Kishon Vijay Abraham I wrote:
There can be systems which does not have a external usb_phy, so get
usb_phy only if dt data indicates the presence of PHY in the case of dt boot
or
if platform_data indicates the presence of PHY. Also remove checking if
return
Hi roger,
On Wednesday 16 October 2013 06:33 PM, Roger Quadros wrote:
Hi Kishon,
On 10/15/2013 10:54 PM, Kishon Vijay Abraham I wrote:
There can be systems which does not have a external usb_phy, so get
usb_phy only if dt data indicates the presence of PHY in the case of dt boot
or
if
Benoit,
On Tuesday 15 October 2013 11:19 AM, Kishon Vijay Abraham I wrote:
From: George Cherian george.cher...@ti.com
Added dr_mode property in dwc3 and set its default mode to device.
Currently dwc3 driver doesn't have support for OTG mode. So explicitly
setting to peripheral even dwc3 is
Benoit,
On Thursday 10 October 2013 04:19 PM, Kishon Vijay Abraham I wrote:
smps10 should be enabled only in the case of host mode. So stop
doing always_on, boot_on from smps10_out1. The driver will enable it in host
mode.
Can you take this patch too?
Thanks
Kishon
Signed-off-by: Kishon
Hi,
On 10/15/2013 10:54 PM, Kishon Vijay Abraham I wrote:
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
On 10/16/2013 06:40 AM, Vishwanathrao Badarkhe, Manish wrote:
From: Vishwanathrao Badarkhe, Manish manish...@ti.com
Currently, probe returns success(0) on debugfs_create_dir
function call failed. Return proper error on debugfs_create_dir
call failed.
Signed-off-by: Vishwanathrao Badarkhe,
On 10/16/2013 08:17 AM, Kishon Vijay Abraham I wrote:
Benoit,
On Thursday 10 October 2013 04:19 PM, Kishon Vijay Abraham I wrote:
smps10 should be enabled only in the case of host mode. So stop
doing always_on, boot_on from smps10_out1. The driver will enable it in host
mode.
Can you
On 10/16/2013 04:10 PM, Kishon Vijay Abraham I wrote:
Hi roger,
On Wednesday 16 October 2013 06:33 PM, Roger Quadros wrote:
Hi Kishon,
On 10/15/2013 10:54 PM, Kishon Vijay Abraham I wrote:
There can be systems which does not have a external usb_phy, so get
usb_phy only if dt data
Hi,
On 10/15/2013 10:54 PM, Kishon Vijay Abraham I wrote:
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-ti-pipe3 since this same driver will be used for SATA PHY and
PCIE PHY.
Hi,
On Wednesday 16 October 2013 06:48 PM, Roger Quadros wrote:
Hi,
On 10/15/2013 10:54 PM, Kishon Vijay Abraham I wrote:
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
On 10/16/2013 04:52 PM, Kishon Vijay Abraham I wrote:
Hi,
On Wednesday 16 October 2013 06:48 PM, Roger Quadros wrote:
Hi,
On 10/15/2013 10:54 PM, Kishon Vijay Abraham I wrote:
Adapted dwc3 core to use the Generic PHY Framework. So for init, exit,
power_on and power_off the following APIs
Hi Nishanth
On Wed, Oct 16, 2013 at 6:54 PM, Nishanth Menon n...@ti.com wrote:
On 10/16/2013 06:40 AM, Vishwanathrao Badarkhe, Manish wrote:
From: Vishwanathrao Badarkhe, Manish manish...@ti.com
Currently, probe returns success(0) on debugfs_create_dir
function call failed. Return proper
On Wed, Oct 16, 2013 at 9:24 AM, Manish Badarkhe
badarkhe.man...@gmail.com wrote:
IMHO, fail of creation of debugfs is not reason enough to fail the
probe - further, this code needs a major revamp to work with device tree.
Yes, fail of debugfs creation should not be enough reason to fail
On Thu, Oct 10, 2013 at 06:29:59PM +0100, Peter Ujfalusi wrote:
On 10/10/2013 07:59 PM, Mark Rutland wrote:
No, they're not actually of much practical use to us at the minute but
it was generally felt better to include the information and not use it
so that if someone does come up with a
From: Sekhar Nori nsek...@ti.com
Mark the eMMC module on BeagleBone black as non removable.
Signed-off-by: Sekhar Nori nsek...@ti.com
Signed-off-by: Balaji T K balaj...@ti.com
---
arch/arm/boot/dts/am335x-boneblack.dts |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
Mark the eMMC on dra7-evm as non removable.
Signed-off-by: Balaji T K balaj...@ti.com
---
arch/arm/boot/dts/dra7-evm.dts |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/dra7-evm.dts b/arch/arm/boot/dts/dra7-evm.dts
index 3abf5f4..799890f 100644
---
ti,vcc-aux-disable-is-sleep property does not exist, so remove it.
Signed-off-by: Balaji T K balaj...@ti.com
---
arch/arm/boot/dts/am335x-boneblack.dts |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/am335x-boneblack.dts
From: Sekhar Nori nsek...@ti.com
add generic non-removable binding support for omap_hsmmc
Signed-off-by: Sekhar Nori nsek...@ti.com
Signed-off-by: Balaji T K balaj...@ti.com
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt |2 +-
drivers/mmc/host/omap_hsmmc.c |
From: Sekhar Nori nsek...@ti.com
start using generic non-removable dt binding
Signed-off-by: Sekhar Nori nsek...@ti.com
Signed-off-by: Balaji T K balaj...@ti.com
---
arch/arm/boot/dts/omap4-var-som.dts |2 +-
arch/arm/boot/dts/omap5-uevm.dts|4 ++--
2 files changed, 3 insertions(+),
start using generic non-removable DT binding and few cleanups for
am335x-boneblack.dts and omap4-var-som.dts. Dropped changes for omap4-sdp and
omap4-panda-common.dtsi from Sekhar Nori's series [1] as non-removable already
exist for mmc5 on omap4-sdp and omap4-panda-common.dtsi
and
ti,bus-width does not exist, use generic bus-width binding
Signed-off-by: Balaji T K balaj...@ti.com
---
arch/arm/boot/dts/omap4-var-som.dts |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-var-som.dts
b/arch/arm/boot/dts/omap4-var-som.dts
index
OMAP34xx and OMAP36xx platforms use dpll1 clock. Add same to common
definition.
AM33XX, OMAP443x, OMAP446x and OMAP447x platforms use dpll_mpu clock
Add same to common definition.
OMAP5, DRA7 platforms use dpll_mpu_ck clock for CPU. Add same to common
definition.
Cc: Benoit Cousson
regulator smps123 supply from Palmas PMIC powers CPU0 on OMAP5uEVM.
Based on a patch by J Keerthy j-keer...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts |4
arch/arm/boot/dts/omap5.dtsi |2 +-
2 files changed, 5 insertions(+), 1
Hi,
This series enables the use of cpufreq-cpu0 generic driver for all
OMAP and related derivatives. Only patch#8 in the series, which
introduces CPU clock nodes, depends on Tero's V8 patch series for clock
nodes[1]
I will stop copy pasting the series complete history and point at [2].
Main
From: J Keerthy j-keer...@ti.com
Add DT OPP table for OMAP54xx family of devices. This data is
decoded by OF with of_init_opp_table() helper function.
The data is based on OMAP543x ES2.0 DM Operating Condition Addendum
Version 0.6(April 2013)
NOTE: The voltage and frequency values work well
AM335x, AM43xx, OMAP5 and DRA7 have missing late init hook. Introduce
SoC specific hook with a call to OMAP2+ generic lateinit hook. This
allows the generic late initializations such as cpufreq hooks to be
active.
Based on out-of-tree patches that need to be introduced in
mainline, this
With OMAP3+ and AM33xx supported SoC having defined CPU device tree
entries with operating-points and clock nodes defined, we can now use
the SoC generic cpufreq-cpu0 driver by registering appropriate device.
Cc: Benoit Cousson bcous...@baylibre.com
Cc: Kevin Hilman khil...@deeprootsystems.com
From: J Keerthy j-keer...@ti.com
regulator smps123 supply from Palmas PMIC powers CPU0 on DRA7 EVM.
[n...@ti.com: rebase to latest]
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: J Keerthy j-keer...@ti.com
---
arch/arm/boot/dts/dra7-evm.dts |4
arch/arm/boot/dts/dra7.dtsi
OMAP3+ supports both device tree and non-device tree boot.
Device tree bindings for OMAP3+ is supposed to be added via dts following:
Documentation/devicetree/bindings/power/opp.txt
Since we now have device tree entries for OMAP3+ cpu OPPs,
The current code wrongly adds duplicate OPPs. So, dont
From: J Keerthy j-keer...@ti.com
Add DT OPP table for DRA7xx family of devices. This data is decoded by
OF with of_init_opp_table() helper function.
The data is based on DRA75x, DRA74x Data Manual revision F (Sept 2013).
TODO: add OPP_HIGH after AVS-Class0 is functional
NOTE: The voltage and
On 10/16/2013 06:04 PM, Mark Rutland wrote:
On Thu, Oct 10, 2013 at 06:29:59PM +0100, Peter Ujfalusi wrote:
On 10/10/2013 07:59 PM, Mark Rutland wrote:
No, they're not actually of much practical use to us at the minute but
it was generally felt better to include the information and not use it
Hi Brian,
*changes v8 - v9*
[PATCH 1/9] no update from [PATCH v8 1/6]
[PATCH 2/9] only commit log updated from [PATCH v8 2/6]
As per feedbacks from Brian Norris computersforpe...@gmail.com
previous
revision [PATCH v8 3/6] and [PATCH 4/6] are split into following sub-patches:
- [PATCH
Add i2c aliases for OMAP and AM processor dts nodes to ensure proper
i2c ordering. Based on Benoit's for_13/dts branch[1]
Changes in V2:
- Following Rajendra's suggestion, done for all OMAP and AM
series SoCs, where i2c is defined.
V1:
Currently, on OMAP5, i2c1 and i2c5 defer probe due to pinctrl
dependencies. This changes the i2c ID each bus is registered with in
i2c-dev interface. As a result of this, many userspace tools break and
there is no consistent manner to fix the same if the i2c dev interface
have no consistent
Provide alias to allow ordering the i2c devices correctly.
Signed-off-by: Nishanth Menon n...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi |3 +++
arch/arm/boot/dts/am4372.dtsi |3 +++
2 files changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi
Hi Pekon,
On Tue, Oct 15, 2013 at 11:19:51AM +0530, Pekon Gupta wrote:
This patch updates following in omap_nand_probe() and omap_nand_remove()
- replaces info-nand with nand_chip (struct nand_chip *nand_chip)
- replaces info-mtd with mtd (struct mtd_info *mtd)
- white-space and formatting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tony,
The following changes since commit ace1e3ec4a2540c783e65884bb7be9cd45a0a295:
ARM: AM33xx: hwmod: Add RNG module data (2013-10-09 09:02:51 -0600)
are available in the git repository at:
On Tue, Oct 15, 2013 at 11:19:52AM +0530, Pekon Gupta wrote:
Autodetection of NAND device bus-width was added in generic NAND driver as
part of following commit
commit 64b37b2a63eb2f80b65c7185f0013f8ffc637ae3
Author: Matthieu CASTET matthieu.cas...@parrot.com
AuthorDate:
On Tue, Oct 15, 2013 at 11:19:53AM +0530, Pekon Gupta wrote:
current implementation in omap3_init_bch() has some redundant code like:
(1) omap3_init_bch() re-probes the DT-binding to detect presence of ELM h/w
engine on SoC. And based on that it selects implemetation of ecc-scheme.
On Tue, Oct 15, 2013 at 11:19:54AM +0530, Pekon Gupta wrote:
In current implementation omap3_init_bch_tail() is a common function to
define ecc layout for different BCHx ecc schemes.This patch:
(1) removes omap3_init_bch_tail() and defines ecc layout for individual
ecc-schemes along with
+ Ivan, as he has touched this stuff before
On Tue, Oct 15, 2013 at 11:19:55AM +0530, Pekon Gupta wrote:
generic frame-work in mtd/nand/nand_bch.c is a wrapper above lib/bch.h which
encapsulates all control information specific to BCH ecc algorithm in
software.
Thus this patch:
(1) replace
On Tue, Oct 15, 2013 at 11:19:57AM +0530, Pekon Gupta wrote:
Managed Device Resource or devm_xx calls takes care of automatic freeing
of the resource in case of:
- failure during driver probe
- failure during resource allocation
- detaching or unloading of driver module (rmmod)
Reference:
Hi,
On Tue, Oct 15, 2013 at 11:19:48AM +0530, Pekon Gupta wrote:
*changes v8 - v9*
[PATCH 1/9] no update from [PATCH v8 1/6]
[PATCH 2/9] only commit log updated from [PATCH v8 2/6]
As per feedbacks from Brian Norris computersforpe...@gmail.com previous
revision [PATCH v8 3/6] and [PATCH
Hi Brian,
From: Brian Norris [mailto:computersforpe...@gmail.com]
On Tue, Oct 15, 2013 at 11:19:52AM +0530, Pekon Gupta wrote:
Autodetection of NAND device bus-width was added in generic NAND
driver as
[...]
@@ -1904,6 +1903,21 @@ static int omap_nand_probe(struct
platform_device *pdev)
51 matches
Mail list logo
