-Original Message-
From: Vutla, Lokesh
Sent: Tuesday, June 11, 2013 9:45 AM
To: Kevin Hilman
Cc: Paul Walmsley; Shilimkar, Santosh; t...@atomide.com; linux-arm-
ker...@lists.infradead.org; linux-omap@vger.kernel.org; Hiremath,
Vaibhav; R, Sricharan; Nayak, Rajendra
Subject: Re:
-Original Message-
From: Kevin Hilman [mailto:khil...@linaro.org]
Sent: Friday, June 07, 2013 3:57 AM
To: Paul Walmsley
Cc: Shilimkar, Santosh; t...@atomide.com; linux-arm-
ker...@lists.infradead.org; linux-omap@vger.kernel.org; Hiremath,
Vaibhav; R, Sricharan
Subject: Re: [PATCH
Hi,
On 10/06/13 10:57, Andreas Naumann wrote:
Currently the maximum number of display is hardcoded in the array
omapfb2_device. Made the number a #define and check it in init routine.
Signed-off-by: Andreas Naumann anaum...@ultratronik.de
---
Our board supports a lot of panels and we
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Hiremath, Vaibhav
Sent: Wednesday, June 12, 2013 11:34 AM
To: Kevin Hilman; Paul Walmsley
Cc: Shilimkar, Santosh; t...@atomide.com; linux-arm-
Hello Grant,
On 06/11/2013 11:57 PM, Grant Likely wrote:
On Tue, 11 Jun 2013 16:50:50 +0200, Florian Vaussard florian.vauss...@epfl.ch
wrote:
Pinctrl headers were not protected with #ifndef.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
Obviously this needs to go in via whatever
Hi Chanwoo Choi,
On Wednesday 12 June 2013 07:09 AM, Chanwoo Choi wrote:
From: Kishon Vijay Abraham I kis...@ti.com
Added an API of_extcon_get_extcon_dev() to be used by drivers to get
extcon device in the case of dt boot (this can be used instead of
extcon_get_extcon_dev()).
Signed-off-by:
-Original Message-
From: Stephen Warren [mailto:swar...@wwwdotorg.org]
Sent: Tuesday, June 11, 2013 9:32 PM
To: J, KEERTHY
Cc: Cousson, Benoit; devicetree-disc...@lists.ozlabs.org; linux-
o...@vger.kernel.org; linux-ker...@vger.kernel.org;
ldewan...@nvidia.com;
This patch adds Palmas MFD node and the regulator nodes for OMAP5.
The node definitions are based on: https://lkml.org/lkml/2013/6/6/25
Boot tested on omap5-uevm board.
Signed-off-by: Graeme Gregory g...@slimlogic.co.uk
Signed-off-by: J Keerthy j-keer...@ti.com
---
AM437x and OMAP5 dwc3 subsytem have different register map.
Major differences are as follows.
OMAP5 has one main interrupt and one misc interrupt
Aegis has four main interrupts and one misc interrupt.
Miscellanous Interrupt offsets are changed.
UTMI OTG Control and Status Registers offsets are
This patch adds wrappers to dwc3_omap_readl/writel calls to accomodate
both OMAP5 and AM437x reg maps (It uses the cached register offsets).
Also renames OMAP5 IRQ1 as IRQMISC and IRQ1 bits as IRQMISC bits.
Signed-off-by: George Cherian george.cher...@ti.com
---
drivers/usb/dwc3/dwc3-omap.c |
Initial patch set to add support for dwc3 in am437x platform.
This patch series addresses the regiter map differences between
OMAP5 and AM437x, to re-use the same driver.
AM437x and OMAP5 dwc3 subsytem have different register map.
Major differences are as follows.
OMAP5 has one main interrupt
This patch Initializes the register offset values depending
on the X_MAJOR of USBOTGSS_REVISION register. Also adds register
offset defines and new debug register defines.
X_MAJOR is 2 for both OMAP5 and AM437x. But both have different glue register
layout. Differentiate AM437x using dt
On Tue, Jun 11, 2013 at 11:25 PM, Grant Likely
grant.lik...@secretlab.ca wrote:
On Fri, 26 Apr 2013 16:31:24 -0500, Jon Hunter jon-hun...@ti.com wrote:
On 04/26/2013 02:31 AM, Linus Walleij wrote:
On Wed, Apr 17, 2013 at 2:41 AM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
This patch series adds low power transition support for OMAP NAND driver.
[Patch 1/3]: Adds pm_runtime calls to handle GPMC module probe and remove
[Patch 2/3]: Adds GPMC suspend/resume support.
[Patch 3/3]: Adds ELM suspend/resume support.
Tested on am335x-evm with NAND flash support, using
From: avinash philip avinashphi...@ti.com
Support for pm_runtime add to GPMC driver.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Signed-off-by: Pekon Gupta pe...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git
From: avinash philip avinashphi...@ti.com
With GPMC converted to platform driver recently, adds low power
transition support in driver itself.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Signed-off-by: Pekon Gupta pe...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 19 +++
1
From: avinash philip avinashphi...@ti.com
In low power modes of AM335X platforms, peripherals power is cut off.
This patch supports low power sleep transition support for ELM driver.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Signed-off-by: Pekon Gupta pe...@ti.com
---
On 31/05/13 10:37, Tomi Valkeinen wrote:
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
This patch adds Palmas MFD node and the regulator nodes for OMAP5.
The node definitions are based on: https://lkml.org/lkml/2013/6/6/25
Boot tested on omap5-uevm board.
Signed-off-by: Graeme Gregory g...@slimlogic.co.uk
Signed-off-by: J Keerthy j-keer...@ti.com
---
V5:
Corrected the IRQ_TYPE
This patch series adds low power transition support for OMAP NAND driver.
[Patch 1/3]: Adds pm_runtime calls to handle GPMC module probe and remove
[Patch 2/3]: Adds GPMC suspend/resume support.
[Patch 3/3]: Adds ELM suspend/resume support.
Tested on am335x-evm with NAND flash support, using
From: avinash philip avinashphi...@ti.com
In low power modes of AM335X platforms, peripherals power is cut off.
This patch supports low power sleep transition support for ELM driver.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Signed-off-by: Pekon Gupta pe...@ti.com
---
From: avinash philip avinashphi...@ti.com
Support for pm_runtime add to GPMC driver.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Signed-off-by: Pekon Gupta pe...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git
From: avinash philip avinashphi...@ti.com
With GPMC converted to platform driver recently, adds low power
transition support in driver itself.
Signed-off-by: Philip Avinash avinashphi...@ti.com
Signed-off-by: Pekon Gupta pe...@ti.com
---
arch/arm/mach-omap2/gpmc.c | 19 +++
1
On Tue, 11 Jun 2013 16:48:56 +0200, Florian Vaussard florian.vauss...@epfl.ch
wrote:
These constants can be used to easily declare MTD partitions inside
DTS.
The constants MTDPART_OFS_* are purposely not included. Indeed,
parse_ofpart_partitions() is expecting u64, but a DT cell is u32.
On Tue, 11 Jun 2013 17:29:43 +0200, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
On 06/11/2013 04:48 PM, Florian Vaussard wrote:
Use the MTD constants for NAND and OneNAND nodes used in OMAP3
DTS.
Signed-off-by: Florian Vaussard florian.vauss...@epfl.ch
---
* Linus Walleij linus.wall...@linaro.org [130611 01:00]:
On Mon, Jun 10, 2013 at 6:23 PM, Tony Lindgren t...@atomide.com wrote:
We only should remux the pins that need remuxing as that's done
every time hitting idle. So I think we should have the following
default groups:
default
On 06/11/2013 07:55 PM, Samuel Ortiz wrote:
Hi Jonathan,
Hi Samuel,
Sebastian, please address the commit log and cosmetic issues I pointed out,
keep the regmap code and I'll pull this patchset in.
By keep the regmap code you mean I am allowed to remove the regmap
usage in mfd (keep patch #1)
* Roger Quadros rog...@ti.com [130611 05:57]:
On 06/10/2013 06:21 PM, Tony Lindgren wrote:
* Quadros, Roger rog...@ti.com [130610 03:09]:
+
+static int __init pcs_omap_init(void)
+{
+ platform_driver_register(pcs_omap_soc_driver);
+
* Kevin Hilman khil...@linaro.org [130610 10:58]:
Andrii Tseglytskyi andrii.tseglyts...@ti.com writes:
SmartReflex consists of three entities: SR device, SR class and
SR driver. SmartReflex driver depends on SmartReflex class, but
order of their initialization is not clear. They both use
Hi Sebastian,
On Wed, Jun 12, 2013 at 03:29:43PM +0200, Sebastian Andrzej Siewior wrote:
On 06/11/2013 07:55 PM, Samuel Ortiz wrote:
Hi Jonathan,
Hi Samuel,
Sebastian, please address the commit log and cosmetic issues I pointed out,
keep the regmap code and I'll pull this patchset in.
* Tomi Valkeinen tomi.valkei...@iki.fi [130611 00:49]:
On 10/06/13 17:14, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@iki.fi [130610 03:44]:
DSS does not have DT bindings, and removing DSS from hwmod data will
break DSS for omap4.
Ah that's right. Care to post a patch
On 06/12/2013 03:50 PM, Samuel Ortiz wrote:
Hi Sebastian,
Hi Samuel,
By keep the regmap code you mean I am allowed to remove the regmap
usage in mfd (keep patch #1) or do you insist on adding its usage in
iio and input?
I insist on keeping it on the MFD driver, i.e. _not_ keeping patch #1.
* Tomi Valkeinen tomi.valkei...@ti.com [130612 03:44]:
On 31/05/13 10:37, Tomi Valkeinen wrote:
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
* Peter Ujfalusi peter.ujfal...@ti.com [130611 01:37]:
Hi,
Small patches to silence the hwmod lookup failures in case when we boot the
kernel on boards where the IPs are not present (OMAP2/3 vs McPDM, DMIC,
HDMI audio).
Thanks applying into omap-for-v3.11/fixes-non-critical.
Regards,
Tony
* Ruslan Bilovol ruslan.bilo...@ti.com [130606 06:48]:
Hi Sebastian,
On Thu, Jun 6, 2013 at 4:24 PM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
The itention was probably to make both pointers const but as it is now,
it is just const used twice.
Yes, it's a typo I did
* Balaji T K balaj...@ti.com [130606 12:20]:
Add needs_vmmc and needs_vmmc_aux to indicate whether regulator is
applicable so that omap_hsmmc can handle deferred probe error
properly for regulators.
Remove the assumption that vmmc_aux regulator to be available only if vmmc is
present.
* Balaji T K balaj...@ti.com [130606 12:20]:
handle vcc and vcc_aux independently
Signed-off-by: Balaji T K balaj...@ti.com
---
drivers/mmc/host/omap_hsmmc.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc.c
On Wednesday 12 June 2013 07:55 PM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [130606 12:20]:
handle vcc and vcc_aux independently
Signed-off-by: Balaji T K balaj...@ti.com
---
drivers/mmc/host/omap_hsmmc.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff
* Balaji T K balaj...@ti.com [130606 12:20]:
omap3_pmx_core: padconf register are in two banks 0x48003000 to 0x48002268
and 0x480025c0 to 0x480025f8.
split omap3_pmx_core into 2 banks as register between 0x48002270 and
0x48002564
belongs to type pinctrl-single,bit-per-mux with access to
* Balaji T K balaj...@ti.com [130606 12:20]:
add pbias states for pbias 0, 1.8V, 3V
add omap3 sd/mmc2 loop back clock config for devconf1 in mmc2_init pinctrl
state
add OMAP3430 sd/mmc1 loop back clock config for devconf0 in mmc1_init pinctrl
state
add OMAP3630 sd/mmc1 speed mode config
* Balaji T K balaj...@ti.com [130606 12:20]:
add pbias states for pbias 0, 1.8V, 3V
add sd/mmc1 pull strength values for control_mmc1 in mmc_init pinctrl state
This too should be under mmc1 in the omap4.dtsi file.
Tony
Signed-off-by: Balaji T K balaj...@ti.com
---
* Balaji T K balaj...@ti.com [130606 12:20]:
PBIAS register configuration is based on the regulator voltage
which supplies these pbias cells, sd i/o pads.
With PBIAS register address and bit definitions different across
omap[3,4,5], Simplify PBIAS configuration under three different
regulator
* Balaji T K balaj...@ti.com [130612 07:39]:
On Wednesday 12 June 2013 07:55 PM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [130606 12:20]:
handle vcc and vcc_aux independently
Signed-off-by: Balaji T K balaj...@ti.com
---
drivers/mmc/host/omap_hsmmc.c |9 +
1 files
On Wed, Jun 12, 2013 at 04:02:00PM +0200, Sebastian Andrzej Siewior wrote:
By keep the regmap code you mean I am allowed to remove the regmap
usage in mfd (keep patch #1) or do you insist on adding its usage in
iio and input?
I insist on keeping it on the MFD driver, i.e. _not_ keeping
On 06/12/2013 04:41 PM, Samuel Ortiz wrote:
This forces me redo a few things and most likely adding it to the
iio and input driver to be consistent here.
I'm not asking for that. The current MFD code uses regmap fine without
the iio and input using it, I don't see why you would have to add
Hi,
On Mon, Jun 10, 2013 at 01:40:05AM +0300, Aaro Koskinen wrote:
+void omap_otg_set_mode(enum omap_otg_mode mode)
+{
+ if (!otg_dev) {
+ WARN(1, %s: controller not present\n, __func__);
+ return;
+ }
+ mutex_lock(otg_dev-serialize);
+ switch
On 06/12/2013 04:32 PM, Tony Lindgren wrote:
* Kevin Hilman khil...@linaro.org [130610 10:58]:
Andrii Tseglytskyi andrii.tseglyts...@ti.com writes:
SmartReflex consists of three entities: SR device, SR class and
SR driver. SmartReflex driver depends on SmartReflex class, but
order of their
On Tue, Jun 11, 2013 at 08:09:15PM +0300, Illia Smyrnov wrote:
The MCSPI controller has a built-in FIFO buffer to unload the DMA or interrupt
handler and improve data throughput. This patch adds FIFO buffer support for
SPI
transfers in DMA mode.
The FIFO could be enabled for SPI module by
On 06/12/2013 02:19 AM, J Keerthy wrote:
This patch adds Palmas MFD node and the regulator nodes for OMAP5.
The node definitions are based on: https://lkml.org/lkml/2013/6/6/25
Boot tested on omap5-uevm board.
Reviewed-by: Stephen Warren swar...@nvidia.com
diff --git
On 06/06/2013 03:52 PM, Sebastian Andrzej Siewior wrote:
From: Philip Avinash avinashphi...@ti.com
Add PWMSS device tree nodes in relation with ECAP EHRPWM DT nodes to
AM33XX SoC family. Also populates device tree nodes for ECAP EHRPWM by
adding necessary properties like pwm-cells, base
Hi Florian,
On 6/12/2013 8:42 AM, Florian Vaussard wrote:
Hello Grant,
On 06/11/2013 11:57 PM, Grant Likely wrote:
On Tue, 11 Jun 2013 16:50:50 +0200, Florian Vaussard
florian.vauss...@epfl.ch wrote:
Pinctrl headers were not protected with #ifndef.
Signed-off-by: Florian Vaussard
* Ming Lei tom.leim...@gmail.com [130603 08:34]:
Hi,
On Sat, May 18, 2013 at 3:17 AM, Tony Lindgren t...@atomide.com wrote:
We can now boot with device tree. If you don't want to update u-boot,
you can boot with appended DTB with the following instructions:
1. Make sure you have the
Hi,
On Wed, Jun 12, 2013 at 06:10:32PM +0200, Sebastian Andrzej Siewior wrote:
On 06/06/2013 03:52 PM, Sebastian Andrzej Siewior wrote:
From: Philip Avinash avinashphi...@ti.com
Add PWMSS device tree nodes in relation with ECAP EHRPWM DT nodes to
AM33XX SoC family. Also populates
* Gupta, Pekon pe...@ti.com [130531 05:07]:
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
Hi Samuel,
I did the cosmetic changes of the subject line and removed the changes
from within the sob lines in each patch. I dropped the #define XPP
STEPCONFIG_XPP thingy and patch #1 which removed regmap from mfd. Not
that I agree with it, I just do not want to miss the merge window due to
this.
This patch removes access to platform data mfd_tscadc_board because the
platform is DT only.
Acked-by: Jonathan Cameron ji...@kernel.org
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
drivers/iio/adc/ti_am335x_adc.c | 21 +++--
1 file changed, 7
* Gupta, Pekon pe...@ti.com [130531 05:07]:
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
This patch removes access to platform data mfd_tscadc_board because the
platform is DT only.
Acked-by: Dmitry Torokhov dmitry.torok...@gmail.com
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
drivers/input/touchscreen/ti_am335x_tsc.c | 25 +
1 file
From: Patil, Rachna rac...@ti.com
The current driver expected touchscreen input
wires(XP,XN,YP,YN) to be connected in a particular order.
Making changes to accept this as platform data.
Sebastian reworked the original patch and removed a lot of the not
required pieces.
Signed-off-by: Patil,
From: Patil, Rachna rac...@ti.com
Add DT support in the MFD core driver. The node name is am3359 because
it was tested on this platform.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
Signed-off-by: Patil, Rachna rac...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
From: Patil, Rachna rac...@ti.com
Add DT support for client ADC driver.
Acked-by: Jonathan Cameron ji...@kernel.org
Signed-off-by: Patil, Rachna rac...@ti.com
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Sebastian Andrzej
On Wednesday 12 June 2013 07:54 PM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [130606 12:20]:
Add needs_vmmc and needs_vmmc_aux to indicate whether regulator is
applicable so that omap_hsmmc can handle deferred probe error
properly for regulators.
Remove the assumption that vmmc_aux
The mfd driver creates platform data for the child devices and it is the
ti_tscadc_dev struct. This struct is copied for the two devices.
The copy of the structure makes a common lock in this structure a little
less usefull. Therefore the platform data is not a pointer to the
structure and the
From: Patil, Rachna rac...@ti.com
Current code has hard coded value written to
step enable bits. Now the bits are updated based
on how many steps are needed to be configured got
from platform data.
The user needs to take care not to exceed
the count more than 16. While using ADC and TSC
one
From: Patil, Rachna rac...@ti.com
When touchscreen and ADC are used together, this
unwanted fifo flush leads to loss of ADC data.
Signed-off-by: Patil, Rachna rac...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
* Pekon Gupta pe...@ti.com [130612 04:07]:
From: avinash philip avinashphi...@ti.com
With GPMC converted to platform driver recently, adds low power
transition support in driver itself.
Applying the first two patches of this series into omap-for-v3.11/gpmc.
Not taking the MTD patch, if it
* Roger Quadros rog...@ti.com [130531 00:23]:
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
* Eduardo Valentin eduardo.valen...@ti.com [130607 13:53]:
Bandgap is a device used to measure temperature on
electronic equipments. It is widely used in digital
integrated circuits. It is based on the dependency
between silicon voltage and temperature.
This patch introduce HAS_BANDGAP
From: Patil, Rachna rac...@ti.com
This patch adds DT support to touch driver. It also provides a binding
document which is used by the MFD and IIO part of the device.
This patch also renames steps_to_configure to coordinate_readouts
because the original name misleads the purpose of the variable.
On Wednesday 12 June 2013 08:05 PM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [130606 12:20]:
omap3_pmx_core: padconf register are in two banks 0x48003000 to 0x48002268
and 0x480025c0 to 0x480025f8.
split omap3_pmx_core into 2 banks as register between 0x48002270 and 0x48002564
belongs
From: Patil, Rachna rac...@ti.com
Add support for core multifunctional device along
with its clients touchscreen and ADC.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
Signed-off-by: Patil, Rachna rac...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Sebastian
From: Pantelis Antoniou pa...@antoniou-consulting.com
This patch provides the members datasheet_name and scan_type. This is
the remaining part of the earlier patch where I (bigeasy) removed iio_map
because it is now supplied by the device tree. It also static names as
suggested by Jonathan.
The interrupt source IRQENB_HW_PEN is enabled in suspend and suposed to
be used as a wake up source. Once this interrupt source is unmaksed, the
devices ends up in ISR and never continues.
This change ACKs the interrupt and disables it so the system does not
freeze.
Signed-off-by: Sebastian
From: Pantelis Antoniou pa...@antoniou-consulting.com
Fix the mfd device in the case where a subdevice might not be activated.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
The driver programs a threshold of coordinate_readouts say 5. The
REG_FIFO0THR registers says it should it be programmed to threshold
minus one. The driver does not expect just 5 coordinates but 5 * 2 + 2.
Multiplied by two because 5 for X and 5 for Y and plus 2 because we have
two Z.
The whole
* Afzal Mohammed af...@ti.com [130527 07:41]:
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -149,6 +149,16 @@ config SOC_AM33XX
select MULTI_IRQ_HANDLER
select COMMON_CLK
+config SOC_AM43XX
+ bool TI AM43x
+ depends on ARCH_OMAP2PLUS
+
The TSC part allows to specify the input lines. The IIO part assumes
that it usues always the last few, that means if IIO has adc-channels
set to 2 it will use channel 6 and 7. However it might make sense to use
only 6.
This patch changes the device property (which was introduced recently
and was
TI-adc reads a little better compared to tiadc. And if we add am335x to
it then we have the same naming scheme as the tsc side.
Acked-by: Jonathan Cameron ji...@kernel.org
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
drivers/iio/adc/ti_am335x_adc.c |3 +--
Usually we get all the values we wanted but it is possible, that te ADC
unit is busy performing the conversation for the HW events. In that case
-EBUSY is returned and the user may re-call the function.
Acked-by: Jonathan Cameron ji...@kernel.org
Signed-off-by: Sebastian Andrzej Siewior
This patch removes access to platform data mfd_tscadc_board because the
platform is DT only.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
drivers/mfd/ti_am335x_tscadc.c | 23 ++-
1 file changed, 6 insertions(+), 17 deletions(-)
diff --git
* Tony Lindgren t...@atomide.com [130612 09:37]:
* Ming Lei tom.leim...@gmail.com [130603 08:34]:
Hi,
On Sat, May 18, 2013 at 3:17 AM, Tony Lindgren t...@atomide.com wrote:
We can now boot with device tree. If you don't want to update u-boot,
you can boot with appended DTB with the
tsc is a very generic name. This patch adds a TI and HW prefix to it
less generic.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
drivers/input/touchscreen/ti_am335x_tsc.c |2 +-
drivers/mfd/ti_am335x_tscadc.c|2 +-
2 files changed, 2 insertions(+), 2
* Afzal Mohammed af...@ti.com [130527 07:42]:
--- a/arch/arm/mach-omap2/io.c
+++ b/arch/arm/mach-omap2/io.c
@@ -586,6 +586,20 @@ void __init am33xx_init_early(void)
}
#endif
+#ifdef CONFIG_SOC_AM43XX
+void __init am43xx_init_early(void)
+{
+ omap2_set_globals_tap(AM335X_CLASS,
+
The previous patch (input/ti_am335x_tsc: ACK the HW_PEN irq in ISR)
acked the interrupt so we don't freeze if we don't handle an enabled
interrupt source. The interrupt core has a mechanism for this and to get
it work one should only say that it handled an interrupt if it is
actually the case.
The two header files removed here are unused and have no users as this
platform was never used with platform devices.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
include/linux/input/ti_am335x_tsc.h | 35 ---
* Sricharan R r.sricha...@ti.com [130609 23:51]:
Commit '3b9b10151c6838af52244cec4af41a938bb5b7ec' cleaned up the
data file to remove all irq and dma entries for all hwmods, which
are now populated by DT. But mcspi and mmc irq, dma entries were
retained since MMC, NFS boot was not working.
* Tony Lindgren t...@atomide.com [130612 10:08]:
* Pekon Gupta pe...@ti.com [130612 04:07]:
From: avinash philip avinashphi...@ti.com
With GPMC converted to platform driver recently, adds low power
transition support in driver itself.
Applying the first two patches of this series into
On Wednesday 12 June 2013 08:05 PM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [130606 12:20]:
add pbias states for pbias 0, 1.8V, 3V
add omap3 sd/mmc2 loop back clock config for devconf1 in mmc2_init pinctrl state
add OMAP3430 sd/mmc1 loop back clock config for devconf0 in mmc1_init
On Wednesday 12 June 2013 08:07 PM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [130606 12:20]:
PBIAS register configuration is based on the regulator voltage
which supplies these pbias cells, sd i/o pads.
With PBIAS register address and bit definitions different across
omap[3,4,5],
* Paul Walmsley p...@pwsan.com [130610 00:27]:
Hi folks -- particularly TIers working on mainline,
There are several regressions that started with v3.10-rc that no one's
fixed for over a month. Some of them should be quite easy:
* 37xx EVM: boot fails
- as of v3.10-rc1
- Cause
* Balaji T K balaj...@ti.com [130612 10:50]:
On Wednesday 12 June 2013 08:05 PM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [130606 12:20]:
add pbias states for pbias 0, 1.8V, 3V
add omap3 sd/mmc2 loop back clock config for devconf1 in mmc2_init pinctrl
state
add OMAP3430 sd/mmc1
* Balaji T K balaj...@ti.com [130612 10:14]:
On Wednesday 12 June 2013 08:05 PM, Tony Lindgren wrote:
* Balaji T K balaj...@ti.com [130606 12:20]:
omap3_pmx_core: padconf register are in two banks 0x48003000 to 0x48002268
and 0x480025c0 to 0x480025f8.
split omap3_pmx_core into 2 banks as
On Mon, Jun 03, 2013 at 10:37:20AM +0300, Oleksandr Dmytryshyn wrote:
We've been lucky not to have any interrupts fire during the suspend
path, otherwise we would have unpredictable behaviour in the kernel.
Based on the logic of the kernel code interrupts from i2c should be
prohibited during
The following changes since commit 317ddd256b9c24b0d78fa8018f80f1e495481a10:
Linux 3.10-rc5 (2013-06-08 17:41:04 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v3.11/fixes-non-critical-signed
for you to fetch
On Wednesday 12 June 2013 02:24 PM, Tony Lindgren wrote:
The following changes since commit 317ddd256b9c24b0d78fa8018f80f1e495481a10:
Linux 3.10-rc5 (2013-06-08 17:41:04 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
Add ramdisk fileystem related options which lets OMAP5 and Keystone
SOCs to boot till shell with multi_v7_config.
Cc: Olof Johansson o...@lixom.net
Cc: Arnd Bergmann a...@arndb.de
Signed-off-by: Sricharan R r.sricha...@ti.com
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
The
The following changes since commit 317ddd256b9c24b0d78fa8018f80f1e495481a10:
Linux 3.10-rc5 (2013-06-08 17:41:04 -0700)
are available in the git repository at:
g...@github.com:sumananna/mailbox.git tags/omap-mailbox-for-v3.11
for you to fetch changes up to
Hi Vaibhav,
Hiremath, Vaibhav hvaib...@ti.com writes:
[...]
Paul/Kevin/Santosh,
AM335x is booting up from Mainline, starting from v3.7, that’s where HWMOD
data got merged to
Mainline.
We have discussed on this in the past as well, let me explain the issue here
in detail
again for
Hi,
On Wed, Jun 12, 2013 at 04:58:26PM -0500, Suman Anna wrote:
The following changes since commit 317ddd256b9c24b0d78fa8018f80f1e495481a10:
Linux 3.10-rc5 (2013-06-08 17:41:04 -0700)
are available in the git repository at:
g...@github.com:sumananna/mailbox.git
Hi Stephen,
-Original Message-
From: Stephen Warren [mailto:swar...@wwwdotorg.org]
Sent: Wednesday, June 12, 2013 9:22 PM
To: J, KEERTHY
Cc: Cousson, Benoit; devicetree-disc...@lists.ozlabs.org; linux-
o...@vger.kernel.org; linux-ker...@vger.kernel.org;
ldewan...@nvidia.com;
1 - 100 of 102 matches
Mail list logo