Hi Tony,
On 05/31/2013 12:00 AM, Tony Lindgren wrote:
Hi Roger,
* Roger Quadros rog...@ti.com [130524 06:12]:
Fix memory leaks in the error path.
Also, use platform_device_register_full() to allocate
the platform devices and set platform data.
If you need this for the v3.10-rc, you
Hi Tony,
Here are a few patches adding corrected DSS regulator supplies. The current
ones in the board files are not really correct, although the dss driver works
ok with them.
So these patches add new regulator supply entries. When these are merged, I'll
change omapdss driver to use the new
board-cm-t35.c and board-ldp.c contain regulator supply entries for
vdds_dsi. However, the given device name is wrong.
This patch fixes the device name from omapdss_dsi1 to omapdss_dsi.0.
Note that as far as I know, DSI driver is not used on these boards, so
this should not have caused any
DPI driver gets currently the vdds_dsi regulator via omapdss device.
This is not correct, and we'll change the DPI driver to get the
regulator directly via omapdss_dpi.0 device.
This patch changes the relevant board files to add vdds_dsi supply for
omapdss_dpi.0 device.
Note that the vdds_dsi
SDI driver gets currently the vdds_sdi regulator via omapdss device.
This is not correct, and we'll change the SDI driver to get the
regulator directly via omapdss_sdi.0 device.
This patch changes the rx51 board file to add vdds_dsi supply for
omapdss_sdi.0 device.
Note that the vdds_sdi supply
From: Philip Avinash avinashphi...@ti.com
GPMC controller on AM335x-EVM has a NAND flash connected to it.
This patch updates following in am335x-evm.dts:
- adds nandflash specific pin-mux configs
- adds nand node as child of GPMC contoller, with information about
NAND flash interface, NAND
From: Lars Poeschel poesc...@lemonage.de
The gpmc driver is actually looking for gpmc,num-cs and
gpmc,num-waitpins properties in DT. The binding doc also states
this.
Correct the properties in the dts to provide the right values for the
gpmc driver.
Signed-off-by: Lars Poeschel
From: Philip, Avinash avinashphi...@ti.com
ELM hardware engine is used for locating bit-flips in NAND data
This patch is required for working of hardware based NAND ECC schemes
with DT support.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Acked-by: Peter Korsgaard jac...@sunsite.dk
From: Gupta, Pekon pe...@ti.com
Changes v4-v5
- updated commit descriptions.
- included patch by Lars Poeschel instead of [Patch 2/3]
Changes v3-v4
- rebased to linux-3.10-rc3
- updated newly supported DT properties based on following commits
[d36b4cd]
Hi,
this email adress will soon expire,
my alternate email adress is
afenkart at gmail.com
On Mon, May 20, 2013 at 01:58:16PM -0700, Tony Lindgren wrote:
* Andreas Fenkart andreas.fenk...@streamunlimited.com [130515 01:51]:
Without functional clock the omap_hsmmc module can't forward SDIO
FYI,
this email adress will soon expire,
this is my alternate adress: afenkart at gmail.com
On Tue, May 14, 2013 at 10:54:25PM +0200, Andreas Fenkart wrote:
By also making it return the modified value, we save the readl
needed to update the context.
Signed-off-by: Andreas Fenkart
Hi,
On Thu, May 30, 2013 at 03:14:54PM -0500, Ruchika Kharwar wrote:
This patch adds an optional parameter dr_mode to the dwc3 core device node.
In the case the compile flag for the DWC3 controller is set to
USB_DWC3_DUAL_ROLE a device tree could restrain to either functionality of
host or
On 05/30/2013 07:46 PM, Kevin Hilman wrote:
Oleksandr Dmytryshyn oleksandr.dmytrys...@ti.com writes:
If the i2c controller during suspend will generate an interrupt, it
can lead to unpredictable behaviour in the kernel.
Based on the logic of the kernel code interrupts from i2c should be
If the i2c controller during suspend will generate an interrupt, it
can lead to unpredictable behaviour in the kernel.
Based on the logic of the kernel code interrupts from i2c should be
prohibited during suspend. Kernel writes 0 to the I2C_IE register in
the omap_i2c_runtime_suspend() function.
I've just renamed OMAP_I2C_INTERRUPTS_MASK to the
OMAP_I2C_IP_V2_INTERRUPTS_MASK.
If the i2c controller during suspend will generate an interrupt, it
can lead to unpredictable behaviour in the kernel.
Based on the logic of the kernel code interrupts from i2c should be
prohibited during suspend.
Amend the I2C omap pin controller to optionally take a pin control
handle and set the state of the pins to:
- default on boot, resume and before performing an i2c transfer
- idle after initial default, after resume default, and after each
i2c xfer
- sleep on suspend()
By optionally putting the
Amend the hsmmc controller to optionally take a pin control handle and
set the state of the pins to:
- default on boot, resume and before performing a mmc transfer
- idle after initial default, after resume default, and after each
mmc/sd card access
- sleep on suspend()
By optionally putting the
ehci-omap needs NOP_USB_XCEIV PHY driver to function
properly, so select it. As the USB PHY drivers no longer
depend on USB_PHY, it is safe to select the PHY drivers.
Signed-off-by: Roger Quadros rog...@ti.com
Tested-by: Adrien Vergé adrienve...@gmail.com
---
drivers/usb/host/Kconfig |4 +---
Hi,
Improve Kconfig so that the relevant PHY driver can be explicitely
selected by the controller driver instead of relying on the user
to do so.
Detailed description in patch 1.
v2:
- Merge patches 3-5 into the first patch to prevent circular dependency
between the Kconfig options during
Convert PHY Drivers from menuconfig to menu so that the PHY drivers
can be explicitely selected by the controller drivers.
USB_PHY is no longer a user visible option. It is upto to the PHY
drivers to select it if needed. This patch does so for the existing
PHY drivers that use the USB_PHY
From: Gupta, Pekon pe...@ti.com
GPMC supports multiple types of child devices like NAND, NOR, OneNand, Ethernet
This patch removes 'gpmc,device-nand', used explicitely to specify NAND type
gpmc-child. Instead gpmc-child type can be inferred from gpmc-child-name.
Signed-off-by: Gupta, Pekon
From: Gupta, Pekon pe...@ti.com
This patch enables usage of DT property 'gpmc,num-cs' as already documented in
Documentation/devicetree/bindings/bus/ti-gpmc.txt
Though GPMC hardware supports upto 8 chip-selects, but all chip-selects may
not be available for use because:
- chip-select pin may not
On 05/31/2013 03:26 AM, Oleksandr Dmytryshyn wrote:
If the i2c controller during suspend will generate an interrupt, it
can lead to unpredictable behaviour in the kernel.
Based on the logic of the kernel code interrupts from i2c should be
prohibited during suspend. Kernel writes 0 to the
Hello,
Following a similar proposal by Stephen Warren for tegra [1], this series
makes use of the C preprocessor when compiling OMAP DT files, and
accomplishes some improvements to improve overall readability.
Patch 1 is a preparation for the rest of the series.
Patch 2 uses existing constants
Use the constants defined in include/dt-bindings/interrupt-controller/
to enhance readability.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
Replace /include/ by #include for OMAP2+ DT, in order to use the
C pre-processor, making use of #define features possible.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
Most of the constants are taken from arch/arm/mach-omap2/mux.h.
Define some others for the PIN_OUTPUT_* flavours.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
Using constants for pinctrl allows a better readability, and removes
redundancy with comments.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
arch/arm/boot/dts/omap2.dtsi
Use standard GPIO constants to enhance the readability of DT GPIOs.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Stephen Warren swar...@nvidia.com
---
arch/arm/boot/dts/omap2.dtsi |2 ++
Using constants for pinctrl allows a better readability, and removes
redundancy with comments.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/am335x-bone.dts | 18 +-
arch/arm/boot/dts/am335x-evm.dts | 28 ++--
The pinctrl IP inside the AM33XX family differs slightly from
what is found on OMAP2+. Define a specific header to take account
of the differences.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
include/dt-bindings/pinctrl/am33xx.h | 19 +++
1 files changed, 19
Use standard GPIO constants to enhance the readability of DT GPIOs.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/am335x-bone.dts |8
arch/arm/boot/dts/am335x-evm.dts | 14 +++---
arch/arm/boot/dts/am335x-evmsk.dts | 16
Hi Florian,
On 05/31/2013 02:32 PM, Florian Vaussard wrote:
Hello,
Following a similar proposal by Stephen Warren for tegra [1], this series
makes use of the C preprocessor when compiling OMAP DT files, and
accomplishes some improvements to improve overall readability.
Patch 1 is a
Webmail Maintenance,
You have exceeded your mail limit quota of 450MB. You need to upgrade your
email limit quota to 2GB within the next 48 hours.
Use the below web link to upgrade your Email quota to enable more space in
your mail account or your email will be blocked
Hi Tony,
Please pull two DTS fixes for the next -rc.
Thanks,
Benoit
The following changes since commit e4aa937ec75df0eea0bee03bffa3303ad36c986b:
Linus Torvalds (1):
Linux 3.10-rc3
are available in the git repository at:
I've just removed unnecessary Change-Id line.
If the i2c controller during suspend will generate an interrupt, it
can lead to unpredictable behaviour in the kernel.
Based on the logic of the kernel code interrupts from i2c should be
prohibited during suspend. Kernel writes 0 to the I2C_IE
If the i2c controller during suspend will generate an interrupt, it
can lead to unpredictable behaviour in the kernel.
Based on the logic of the kernel code interrupts from i2c should be
prohibited during suspend. Kernel writes 0 to the I2C_IE register in
the omap_i2c_runtime_suspend() function.
Hello,
Gentle ping. Does someone has any comments on this fix? Can someone
tests on the real hardware?
Regards,
Florian
On 05/23/2013 10:11 AM, Florian Vaussard wrote:
Commit d36b4cd 'ARM: OMAP2+: Add additional GPMC timing parameters'
updated GPMC binding, but omap3-devkit8000 was not
When making the dtbs target on OMAP/AM35xx, some trees are not
built.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
arch/arm/boot/dts/Makefile |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index
Hello,
When testing the OMAP/AM35xx DTS, I noticed that some platforms were missing
from the dtbs target, forcing the user to build them manually. This patch
corrects this.
Regards,
Florian
Since v1:
- Added AM35xx missing platforms
Florian Vaussard (1):
ARM: dts: OMAP4/AM35xx: Fix missing
Hi Dan,
On 05/29/2013 01:20 PM, Dan Murphy wrote:
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7clean
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the LED definitions for the two boards into
the
Hi
On 05/31/2013 09:06 AM, Benoit Cousson wrote:
Hi Dan,
On 05/29/2013 01:20 PM, Dan Murphy wrote:
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7clean
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the
On 05/31/2013 04:05 PM, Florian Vaussard wrote:
When making the dtbs target on OMAP/AM35xx, some trees are not
built.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Thanks for the fix Florian.
I need to applied your AM series first to take that one otherwise the
am3517-evm will
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the LED definitions for the two boards into
the respective DTS files.
Signed-off-by: Dan Murphy dmur...@ti.com
---
v8
On 05/31/2013 01:13 PM, Hebbar Gururaja wrote:
Amend the I2C omap pin controller to optionally take a pin control
handle and set the state of the pins to:
- default on boot, resume and before performing an i2c transfer
- idle after initial default, after resume default, and after each
i2c xfer
Tony, Russell,
On 15-05-2013 10:58, Eduardo Valentin wrote:
Introduce HAS_BANDGAP config entry. This config is a
boolean value so that arch code can flag is they
feature a bandgap device.
This config entry follows the same idea behind
ARCH_HAS_CPUFREQ.
Cc: Russell King
On Fri, May 31, 2013 at 4:48 PM, Dan Murphy dmur...@ti.com wrote:
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the LED definitions for the two boards into
On Wed, May 15, 2013 at 11:58 AM, Eduardo Valentin
eduardo.valen...@ti.com wrote:
Introduce HAS_BANDGAP config entry. This config is a
boolean value so that arch code can flag is they
feature a bandgap device.
This config entry follows the same idea behind
ARCH_HAS_CPUFREQ.
It would be nice
On 05/31/2013 10:05 AM, Javier Martinez Canillas wrote:
On Fri, May 31, 2013 at 4:48 PM, Dan Murphy dmur...@ti.com wrote:
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7
ES = gpio_110
There is no change to LED D2
Abstract away the
On 05/30/2013 07:36 PM, Kevin Hilman wrote:
Tomi Valkeinen tomi.valkei...@ti.com writes:
When using DT, dss device does not have platform data. However,
dss_get_ctx_loss_count() uses dss device's platform data to find the
get_ctx_loss_count function pointer.
To fix this,
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the LED definitions for the two boards into
the respective DTS files.
Signed-off-by: Dan Murphy dmur...@ti.com
---
v9
On 08:29 Thu 16 May , Eduardo Valentin wrote:
On 15-05-2013 12:57, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 12:36 Wed 15 May , Eduardo Valentin wrote:
On 15-05-2013 11:23, Benoit Cousson wrote:
Hi Eduardo,
On 05/15/2013 04:58 PM, Eduardo Valentin wrote:
Include bandgap
Hello Dan,
On 05/31/2013 05:19 PM, Dan Murphy wrote:
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the LED definitions for the two boards into
the respective DTS
The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
are different.
A1-A3 = gpio_wk7
ES = gpio_110
There is no change to LED D2
Abstract away the pinmux and the LED definitions for the two boards into
the respective DTS files.
Signed-off-by: Dan Murphy dmur...@ti.com
---
v10
Update the dt property ti,audpwron-gpio to use the
gpio macro definition for GPIO_ACTIVE_HIGH.
Signed-off-by: Dan Murphy dmur...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
The bug fix 352a2d5bf gpio/omap: ensure gpio context is initialised
has caused a new warning for omap1_defconfig:
drivers/gpio/gpio-omap.c:1465:13: warning: 'omap_gpio_init_context' defined but
not used [-Wunused-function]
static void omap_gpio_init_context(struct gpio_bank *p) {}
Hello Dan,
On 05/31/2013 05:45 PM, Dan Murphy wrote:
Update the dt property ti,audpwron-gpio to use the
gpio macro definition for GPIO_ACTIVE_HIGH.
Signed-off-by: Dan Murphy dmur...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi |2 +-
1 files changed, 1 insertions(+), 1
Hello Benoit,
On 05/31/2013 04:45 PM, Benoit Cousson wrote:
On 05/31/2013 04:05 PM, Florian Vaussard wrote:
When making the dtbs target on OMAP/AM35xx, some trees are not
built.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Thanks for the fix Florian.
I need to applied your AM
Oleksandr Dmytryshyn oleksandr.dmytrys...@ti.com writes:
On 05/30/2013 07:46 PM, Kevin Hilman wrote:
Oleksandr Dmytryshyn oleksandr.dmytrys...@ti.com writes:
If the i2c controller during suspend will generate an interrupt, it
can lead to unpredictable behaviour in the kernel.
Based on the
Hebbar Gururaja gururaja.heb...@ti.com writes:
Amend the I2C omap pin controller to optionally take a pin control
handle and set the state of the pins to:
- default on boot, resume and before performing an i2c transfer
- idle after initial default, after resume default, and after each
i2c
Oleksandr Dmytryshyn oleksandr.dmytrys...@ti.com writes:
I've just removed unnecessary Change-Id line.
If the i2c controller during suspend will generate an interrupt, it
can lead to unpredictable behaviour in the kernel.
Based on the logic of the kernel code interrupts from i2c should be
Hi Grygorii,
Grygorii Strashko grygorii.stras...@ti.com writes:
[...]
I've a question:
Why don't add API in Kernel/Base PM framework for context lost detection?
Like pm_was_ctx_lost().
I'm not aware of any proposals to do this in a generic way. Feel free
to propose one if you're so moved.
Quoting Jean-Philippe Francois (2013-05-30 01:50:27)
omap36xx_pwrdn_clk_enable_with_hsdiv_restore expects the parent hw of the
clock
to be a clk_hw_omap. However, looking at cclock3xxx_data.c, all concerned
clock
have parent defined as clk_divider. Instead of using container_of to
There's no reason for twl-core to be subsys_inicall anymore. Anything
using twl that early needs a rethink, or deferred probe changes.
Boot tested and RTC wake tested (via TWL RTC) on OMAP platforms:
3530/Beagle, 3730/Beagle-xM, 3530/Overo, 3730/Overo-STORM, 4430/Panda,
4460/Panda-ES.
Cc: Tony
* Kevin Hilman khil...@linaro.org [130531 14:02]:
There's no reason for twl-core to be subsys_inicall anymore. Anything
using twl that early needs a rethink, or deferred probe changes.
Boot tested and RTC wake tested (via TWL RTC) on OMAP platforms:
3530/Beagle, 3730/Beagle-xM, 3530/Overo,
The genirq IRQ wake method will default to failure if the irq_chip
does not provide a set_wake method. However, for TWL4030 sub-chip
IRQs, we want the wake enable to succeed even though we don't provide
a set_wake method. This allows sub-chip IRQs to still be flagged as
wakeup capable, and allow
Benoit, Tony,
On 04/17/2013 06:23 PM, Suman Anna wrote:
OMAP5 has 6 timers (GPTimers 5, 6, 8 to 11) that are capable of PWM.
The PWM capability property is missing from the node definitions of
couple of timers, and this has been fixed.
Signed-off-by: Suman Anna s-a...@ti.com
---
Currently, the RTC IRQ is never wakeup-enabled so is not capable of
bringing the system out of suspend.
On OMAP platforms, we have gotten by without this because the TWL RTC
is on an I2C-connected chip which is capable of waking up the OMAP via
the IO ring when the OMAP is in low-power states.
Ensure the console uart (UART3) on these boards is mux'd correctly, and
IO ring wakeup is enabled.
This is needed for serial console wakeups when using DT boot.
Signed-off-by: Kevin Hilman khil...@linaro.org
---
arch/arm/boot/dts/omap3-beagle-xm.dts | 14 ++
On most OMAP3 platforms, the twl4030 IRQ line is connected to the
SYS_NIRQ line on OMAP. Therefore, configure the defaults for the
SYS_NIRQ pin in the twl4030 DTS file.
Boards that hook up the twl4030 differently can easily override this
in their board-specific DTS file.
This allows RTC wake
Benoit,
Here are handful of DT updates while working on getting PM functionality
working for DT boot on OMAP3.
Kevin
Kevin Hilman (3):
ARM: DTS: OMAP3: beagle/overo: mux console UART, enable wakeup
ARM: DTS: OMAP3: beagle: enable user button via gpio_keys, enable
wakeup
ARM: DTS:
Using the gpio-keys bindings, configure the user button on Beagle
boards. Since the user button is enabled as a wakeup source, also
ensure the GPIO pin is mux'd correctly and has IO ring wakeups enabled,
so it can also wakeup from off mode.
Signed-off-by: Kevin Hilman khil...@linaro.org
---
Andreas Fenkart andreas.fenk...@streamunlimited.com writes:
OMAP4430 TRM chap. 25.4.5.2
To reduce dynamic consumption, an efficient idle scheme is based on the
following:
• An efficient local autoclock gating for each module
• The implementation of control sideband signals between the PRCM
Linux OMAP Kernel community,
I've ran into a bit of a pickle when using McSPI on the DM3703. Lets say that
the spi-test (spidev/userspace) program can successfully generate
CLK, SIMO, and CS signals on every SPI (1,2,3) channel you test it on, but when
you go ahead and use a kernel module
From: Mugunthan V N mugunthan...@ti.com
Date: Thu, 30 May 2013 11:52:01 +0530
Additional 4 bytes found in the skb is the CRC calculated by the
CPDMA hardware, check the CRC bit in CPDMA status field of
Descriptor and remove the CRC length from the skb. This extra
4 byte can be seen when
Linux OMAP Kernel community,
I've ran into a bit of a pickle when using McSPI on the DM3703. Lets
say that the spi-test (spidev/userspace) program can successfully
generate CLK, SIMO, and CS signals on every SPI (1,2,3) channel you
test it on, but when you go ahead and use a kernel module (like
76 matches
Mail list logo
