On Wed, Jun 26, 2013 at 05:17:29PM +0530, Kishon Vijay Abraham I wrote:
+menuconfig GENERIC_PHY
+ tristate PHY Subsystem
+ help
+ Generic PHY support.
+
+ This framework is designed to provide a generic interface for PHY
+ devices present in the kernel. This layer
* Grygorii Strashko grygorii.stras...@ti.com [130716 07:32]:
Hi Tony,
On 07/16/2013 04:41 PM, Tony Lindgren wrote:
* Grygorii Strashko grygorii.stras...@ti.com [130716 06:22]:
Hi Tony,
This patch causes boot failure when I've applied my patch
[RFC] ARM: OMAP2+: omap_device: add pinctrl
On Tuesday 16 July 2013 03:57 PM, Grygorii Strashko wrote:
Hi Rajendra,
On 07/11/2013 12:17 PM, Rajendra Nayak wrote:
On Wednesday 10 July 2013 09:37 PM, Felipe Balbi wrote:
how about something like below ? It makes omap_device/hwmod and
pm_runtime agree on the initial state of the device
Hi,
On Wednesday 17 July 2013 11:59 AM, Greg KH wrote:
On Wed, Jun 26, 2013 at 05:17:29PM +0530, Kishon Vijay Abraham I wrote:
+menuconfig GENERIC_PHY
+tristate PHY Subsystem
+help
+ Generic PHY support.
+
+ This framework is designed to provide a generic interface for
Hello Jonathan,
Two very quick comments based on quick glance as it may be a while
before I can do a full review.
We still have channels that are only usable for temperature being
output to user space as voltage channels? Is the conversion so very hard?
Can you please clarify what should
On Tue, Jul 16, 2013 at 11:41:08AM -0500, Nishanth Menon wrote:
We seem to have a few missing updates to device tree bindings with the
latest set of changes getting merged in.
Applied both, thanks.
signature.asc
Description: Digital signature
Hi Stephen,
On Monday 15 July 2013 21:39:31 Stephen Warren wrote:
On 07/15/2013 07:10 PM, Laurent Pinchart wrote:
On Friday 12 July 2013 08:42:41 Stephen Warren wrote:
...
I think the values for any common system-wide flags should be defined
once in some system-wide place, and the
Hello,
v5 - gpadc DT node renamed from gpadc to generic adc, added
temperature channels; raw code is corracted with calibration
data.
v4 - addressed comments: fixed style violation, bug in freeing memory,
added comments explaining calibration method, removed test network
The GPADC is general purpose ADC found on TWL6030, and TWL6032 PMIC,
known also as Phoenix and PhoenixLite.
The TWL6030 and TWL6032 have GPADC with 17 and 19 channels
respectively. Some channels have current source and are used for
measuring voltage drop on resistive load for detecting battery ID
GPADC is the general purpose ADC present on twl6030.
The dt data is interrupt used to trigger end of ADC
conversion.
Signed-off-by: Oleksandr Kozaruk oleksandr.koza...@ti.com
---
arch/arm/boot/dts/twl6030.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git
Hi Tony, Kevin
This patch series introduces dynamic pinctrl handling in OMAP device framework
in the same way as it was before switching to DT.
This allow OMAP devices driver's developers to simply add dynamic pinctrl
handling for default, active, idle, sleep PIN states in their drivers
by
Add dynamic active/idle pin states for uart3/4 which will be applied
when uart3/4 state is switched from active to idle and back by Runtime
PM or during system suspend.
CC: Benoit Cousson benoit.cous...@linaro.org
CC: Linus Walleij linus.wall...@linaro.org
CC: Stephen Warren swar...@wwwdotorg.org
The pinctrl support in Device core assumed to be optional - so, It's
valid case, when there are no definition for default device's pinctrl
states in DT at all (default, active, idle, sleep).
And in this case dev-pins == NULL and pinctrl_pm_select*() API
should return 0 always.
Now the checks for
Before switching to DT pinctrl states of OMAP IPs have been handled by hwmod
framework. After switching to DT-boot the pinctrl handling was dropped from
hwmod framework and, as it was recommended, OMAP IP's drivers have to be updated
to handle pinctrl states by itself using pinctrl_pm_select_xx()
Hi Tony,
On 07/16/2013 12:05 PM, Tony Lindgren wrote:
Hi all,
As discussed earlier, the pinctrl support for changing some of the
consumer device pins during runtime needs some improvment.
Here are the patches to do that, I'll also post a minimal sample
patch as a reply to this thread on how
Hi Grygorii,
On 07/17/2013 02:41 PM, Grygorii Strashko wrote:
Hi Tony, Kevin
This patch series introduces dynamic pinctrl handling in OMAP device framework
in the same way as it was before switching to DT.
This allow OMAP devices driver's developers to simply add dynamic pinctrl
handling
On 07/17/2013 02:57 PM, Roger Quadros wrote:
Hi Grygorii,
On 07/17/2013 02:41 PM, Grygorii Strashko wrote:
Hi Tony, Kevin
This patch series introduces dynamic pinctrl handling in OMAP device framework
in the same way as it was before switching to DT.
This allow OMAP devices driver's
On 27/06/13 04:32, Joel Fernandes wrote:
From: Matt Porter mpor...@ti.com
Adds AM33XX MMC support for am335x-bone, am335x-evm, and am335x-evmsk.
Also added is the DMA binding definitions based on the generic DMA
request binding.
The HWMOD data removal was breaking MMC so some new
On Mon, Jul 15, 2013 at 01:33:53PM +0200, Lars-Peter Clausen wrote:
On 07/15/2013 01:09 PM, Kozaruk, Oleksandr wrote:
[...]
+ ret = devm_request_threaded_irq(dev, irq, NULL,
+ twl6030_gpadc_irq_handler,
+ IRQF_ONESHOT, twl6030_gpadc, gpadc);
You access memory in the interrupt
Hello.
On 17-07-2013 15:12, Oleksandr Kozaruk wrote:
GPADC is the general purpose ADC present on twl6030.
The dt data is interrupt used to trigger end of ADC
conversion.
Signed-off-by: Oleksandr Kozaruk oleksandr.koza...@ti.com
---
arch/arm/boot/dts/twl6030.dtsi | 6 ++
1 file
This patch changes the dtsi entry on omap4430 to contain
the thermal data. This data will enable the passive
cooling with CPUfreq cooling device at 100C and the
system will do a thermal shutdown at 125C.
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Russell King
This patch changes the dtsi entry on omap4430 to contain
the thermal data. This data will enable the passive
cooling with CPUfreq cooling device at 100C and the
system will do a thermal shutdown at 125C.
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Russell King
OMAP4430 devices can reach high temperatures and thus
needs to have cpufreq-cooling on systems running on it.
This patch adds the flag so that cpufreq-cpu0 driver
loads the cooling device to use cpufreq on OMAP4430.
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc:
On 07/17/2013 04:33 PM, Sergei Shtylyov wrote:
Hello.
On 17-07-2013 15:12, Oleksandr Kozaruk wrote:
GPADC is the general purpose ADC present on twl6030.
The dt data is interrupt used to trigger end of ADC
conversion.
Signed-off-by: Oleksandr Kozaruk oleksandr.koza...@ti.com
---
On 07/17/2013 03:45 PM, Oleksandr Kozaruk wrote:
On Mon, Jul 15, 2013 at 01:33:53PM +0200, Lars-Peter Clausen wrote:
On 07/15/2013 01:09 PM, Kozaruk, Oleksandr wrote:
[...]
+ ret = devm_request_threaded_irq(dev, irq, NULL,
+ twl6030_gpadc_irq_handler,
+ IRQF_ONESHOT, twl6030_gpadc,
OMAP4430 devices can reach high temperatures and thus
needs to have cpufreq-cooling on systems running on it.
This patch adds the flag so that cpufreq-cpu0 driver
loads the cooling device to use cpufreq on OMAP4430.
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc:
This patch changes the dtsi entry on omap4430 to contain
the thermal data. This data will enable the passive
cooling with CPUfreq cooling device at 100C and the
system will do a thermal shutdown at 125C.
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Russell King
OMAP4430 devices can reach high temperatures and thus
needs to have cpufreq-cooling on systems running on it.
This patch adds the flag so that cpufreq-cpu0 driver
loads the cooling device to use cpufreq on OMAP4430.
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc:
* Grygorii Strashko grygorii.stras...@ti.com [130717 04:49]:
Add dynamic active/idle pin states for uart3/4 which will be applied
when uart3/4 state is switched from active to idle and back by Runtime
PM or during system suspend.
This is good for testing code, but should not be merged because
* Grygorii Strashko grygorii.stras...@ti.com [130717 04:49]:
Before switching to DT pinctrl states of OMAP IPs have been handled by hwmod
framework. After switching to DT-boot the pinctrl handling was dropped from
hwmod framework and, as it was recommended, OMAP IP's drivers have to be
* Grygorii Strashko grygorii.stras...@ti.com [130717 04:49]:
The pinctrl support in Device core assumed to be optional - so, It's
valid case, when there are no definition for default device's pinctrl
states in DT at all (default, active, idle, sleep).
And in this case dev-pins == NULL and
I'm trying to get the MMC port working on our custom AM3352 CPU board.
I have added MMC entries to out dts file (similar to [1]), and I've
enabled CONFIG_TI_EDMA.
Our board boots fine without an SD card inserted ...
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version
On Wed, Jul 17, 2013 at 10:12:22AM +0530, Lokesh Vutla wrote:
Hi Mark,
Hi Lokesh.
On Wednesday 17 July 2013 04:59 AM, Mark A. Greer wrote:
From: Mark A. Greer mgr...@animalcreek.com
diff --git a/arch/arm/boot/dts/am335x-evmsk.dts
b/arch/arm/boot/dts/am335x-evmsk.dts
index
From: Mark A. Greer mgr...@animalcreek.com
Add the generic AM33XX SHAM module's device tree data and
enable it for the am335x-evm, am335x-evmsk, and am335x-bone
platforms. Also add Documentation file describing the data
for the SHAM module.
CC: Paul Walmsley p...@pwsan.com
Signed-off-by: Mark
From: Mark A. Greer mgr...@animalcreek.com
Add the generic AM33XX AES module's device tree data and
enable it for the am335x-evm, am335x-evmsk, and am335x-bone
platforms. Also add Documentation file describing the data
for the AES module.
CC: Paul Walmsley p...@pwsan.com
Signed-off-by: Mark A.
From: Mark A. Greer mgr...@animalcreek.com
Long overdue patches to add the device tree updates and
documentation for the SHAM and AES modules on the am33xx.
The supporting code is already in the mainline kernel.
This series is based on the current mainline kernel,
c0d15cc (linked-list: Remove
On 17/07/13 16:55, Mark Jackson wrote:
I'm trying to get the MMC port working on our custom AM3352 CPU board.
I have added MMC entries to out dts file (similar to [1]), and I've
enabled CONFIG_TI_EDMA.
Our board boots fine without an SD card inserted ...
[0.00] Booting Linux on
On 07/17/2013 10:55 AM, Mark Jackson wrote:
I'm trying to get the MMC port working on our custom AM3352 CPU board.
I have added MMC entries to out dts file (similar to [1]), and I've
enabled CONFIG_TI_EDMA.
Our board boots fine without an SD card inserted ...
[0.00] Booting
Hi,
On 07/17/2013 06:32 PM, Tony Lindgren wrote:
* Grygorii Strashko grygorii.stras...@ti.com [130717 04:49]:
Add dynamic active/idle pin states for uart3/4 which will be applied
when uart3/4 state is switched from active to idle and back by Runtime
PM or during system suspend.
This is good
commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.
However, The regulator information is based on an older temporary
pre-production board variant and does not reflect production board
750-2628-XXX
commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.
However, The regulator information is based on an older temporary
pre-production board variant and does not reflect production board
750-2628-XXX
commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.
However, The regulator information is based on an older temporary
pre-production board variant and does not reflect production board
750-2628-XXX
commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.
However, currently we use the Palmas regulator names which is used for
different purposes on uEVM. Document the same based on 750-2628-XXX
boards
commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.
However, The regulator information is based on an older temporary
pre-production board variant and does not reflect production board
750-2628-XXX
commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.
However, The regulator information is based on an older temporary
pre-production board variant and does not reflect production board
750-2628-XXX
Due to wrong older revision of documentation used as reference, we
seem to have a bunch of LDOs wrongly configured on OMAP5 uEVM. This
series is based power tree on production board 750-2628-XXX platform.
Unfortunately, the wrong voltages may be detrimental to OMAP5 as they
supply hardware blocks
commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.
However, The regulator information is based on an older temporary
pre-production board variant and does not reflect production board
750-2628-XXX
commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.
However, The regulator information is based on an older temporary
pre-production board variant and does not reflect production board
750-2628-XXX
commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.
However, The regulator information is based on an older temporary
pre-production board variant and does not reflect production board
750-2628-XXX
On 07/17/2013 06:38 PM, Tony Lindgren wrote:
* Grygorii Strashko grygorii.stras...@ti.com [130717 04:49]:
Before switching to DT pinctrl states of OMAP IPs have been handled by hwmod
framework. After switching to DT-boot the pinctrl handling was dropped from
hwmod framework and, as it was
On 07/17/2013 05:00 AM, Laurent Pinchart wrote:
On Monday 15 July 2013 21:39:31 Stephen Warren wrote:
...
But then there's a problem where people assume that the common flags are
always available, and somewhere they aren't... Care is needed in the
choice of which common flags to define and/or
* Ezequiel Garcia | 2013-07-06 18:39:50 [-0300]:
Hi Sebastian,
Hi Ezequiel,
After some minor DT tweaking on the current patchset,
I've managed to detect an USB mass storage device in the
second instance (host / usb1) using a Beaglebone black board.
Beaglebone black, that one has a different
On Wed, Jul 17, 2013 at 03:02:59PM +0530, Kishon Vijay Abraham I wrote:
Hi,
On Wednesday 17 July 2013 11:59 AM, Greg KH wrote:
On Wed, Jun 26, 2013 at 05:17:29PM +0530, Kishon Vijay Abraham I wrote:
+menuconfig GENERIC_PHY
+ tristate PHY Subsystem
+ help
+Generic PHY support.
Hi Sebastian,
On Wed, Jul 17, 2013 at 07:12:29PM +0200, Sebastian Andrzej Siewior wrote:
After some minor DT tweaking on the current patchset,
I've managed to detect an USB mass storage device in the
second instance (host / usb1) using a Beaglebone black board.
Beaglebone black, that one
On 07/17/2013 01:12 PM, Oleksandr Kozaruk wrote:
The GPADC is general purpose ADC found on TWL6030, and TWL6032 PMIC,
known also as Phoenix and PhoenixLite.
The TWL6030 and TWL6032 have GPADC with 17 and 19 channels
respectively. Some channels have current source and are used for
measuring
On Wed, Jul 17, 2013 at 11:11:19AM -0600, Stephen Warren wrote:
On 07/17/2013 05:00 AM, Laurent Pinchart wrote:
On Monday 15 July 2013 21:39:31 Stephen Warren wrote:
...
But then there's a problem where people assume that the common flags are
always available, and somewhere they aren't...
Oleksandr Kozaruk oleksandr.koza...@ti.com wrote:
Hello Jonathan,
Two very quick comments based on quick glance as it may be a while
before I can do a full review.
We still have channels that are only usable for temperature being
output to user space as voltage channels? Is the conversion
With increase in NAND flash densities occurence of bit-flips has increased.
Thus stronger ECC schemes are required for detecting and correcting multiple
simultaneous bit-flips in same NAND page. But stronger ECC schemes have large
ECC syndrome which require more space in OOB/Spare.
This patch add
With increase in NAND flash densities occurence of bit-flips has increased.
Thus stronger ECC schemes are required for detecting and correcting multiple
simultaneous bit-flips in same NAND page. But stronger ECC schemes have large
ECC syndrome which require more space in OOB/Spare.
This patch add
This patch series add support of BCH16_ECC scheme.
As BCH16_ECC scheme generates 26bytes of ECC syndrome per 512B data,
hence this scheme is usable only for NAND devices having 4K or above
page-size, as their OOB/spare area has enough space to accomodate ECC.
This patch series is applicable over
With increase in NAND flash densities occurence of bit-flips has increased.
Thus stronger ECC schemes are required for detecting and correcting multiple
simultaneous bit-flips in same NAND page. But stronger ECC schemes have large
ECC syndrome which require more space in OOB/Spare.
This patch add
With increase in NAND flash densities occurence of bit-flips has increased.
Thus stronger ECC schemes are required for detecting and correcting multiple
simultaneous bit-flips in same NAND page. But stronger ECC schemes have large
ECC syndrome which require more space in OOB/Spare.
This patch add
On 07/16/2013 03:05 AM, Tony Lindgren wrote:
It's quite common that we need to dynamically change some pins for a
device for runtime PM, or toggle a pin between rx and tx. Changing all
the pins for a device is not efficient way of doing it.
So let's allow setting up multiple active states
On 07/16/2013 03:05 AM, Tony Lindgren wrote:
To toggle dynamic states, let's add the optional active state in
addition to the static default state. Then if the optional active
state is defined, we can require that idle and sleep states cover
the same pingroups as the active state.
Then
On 07/16/2013 03:05 AM, Tony Lindgren wrote:
We want to have static pin states handled separately from
dynamic pin states, so let's add optional state_active.
Then if state_active is defined, let's check and make sure
state_idle and state_sleep match state_active for the
pin groups to avoid
On 07/16/2013 03:05 AM, Tony Lindgren wrote:
To toggle dynamic states, let's add the optional active state in
addition to the static default state. Then if the optional active
state is defined, we can require that idle and sleep states cover
the same pingroups as the active state.
Then
Replace the numerical polarity flags with the PWM_POLARITY_INVERTED
symbolic constant.
Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com
---
arch/arm/boot/dts/am335x-evmsk.dts | 3 ++-
arch/arm/boot/dts/wm8850-w70v2.dts | 3 ++-
2 files changed, 4 insertions(+), 2
Hello,
Here's a small patch set that replaces PWM polarity numerical constants with
macros in DT.
The series is the result of splitting the original patch into four patches
that
- add the flag macro (both in a header file and in the PWM DT binding core
documentation)
- use the macro in the
Don't redefine a PWM_SPEC_POLARITY macro with a value identical to
PWM_POLARITY_INVERTED, use the PWM DT macro directly.
Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com
---
drivers/pwm/core.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git
The PWM client cells format is documented in the generic pwm.txt
documentation and duplicated in all PWM driver bindings. Remove
duplicate information and reference pwm.txt instead.
Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com
---
Define a PWM_POLARITY_INVERTED macro in include/dt-bindings/pwm/pwm.h to
be used by device tree sources.
Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com
---
Documentation/devicetree/bindings/pwm/pwm.txt | 7 ---
include/dt-bindings/pwm/pwm.h | 14
Hi Luciano,
On Monday 01 July 2013 15:39:30 Luciano Coelho wrote:
On Fri, 2013-06-28 at 16:21 +0300, Luciano Coelho wrote:
On Fri, 2013-06-28 at 15:18 +0300, Felipe Balbi wrote:
On Fri, Jun 28, 2013 at 03:13:52PM +0300, Luciano Coelho wrote:
On Fri, 2013-06-28 at 14:41 +0300, Felipe
Hi all,
Now i worked on omp2 and met a probelm which someplace close_irq for
3.6second.
The kernel version is 2.6.37. I used trace to find in irq_action:omap_hsmmc_irq.
This problem occured by removed the sdcard when there are io operations.
I found the read problem is in
73 matches
Mail list logo
