The qspi node defines crossbar number as its interrupt number. But,
the crossbar dts patches are not yet there, this causes a warning during
boot. So interrupts = property should be removed from DT and added
later by crossbar series.
Reported-by: Sricharan R r.sricha...@ti.com
Signed-off-by:
On 16/06/14 12:22, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140613 09:17]:
From: Sathya Prakash M R sath...@ti.com
Add DSS hwmod data for AM43xx.
Cc: Andrew Morton a...@linux-foundation.org
Acked-by: Rajendra Nayak rna...@ti.com
Signed-off-by: Sathya Prakash M R sath...@ti.com
Hi Jason,
From: Jason Kridner
Adding devicetree and linux-arm-kernel lists based on feedback on IRC...
On Tue, Jun 10, 2014 at 12:46 PM, Jason Kridner jkrid...@gmail.com wrote:
I'd like to discuss moving our current library of cape devicetree
overlay sources into a single tree, including the
* Tomi Valkeinen tomi.valkei...@ti.com [140617 00:10]:
On 16/06/14 12:22, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140613 09:17]:
From: Sathya Prakash M R sath...@ti.com
Add DSS hwmod data for AM43xx.
Cc: Andrew Morton a...@linux-foundation.org
Acked-by: Rajendra Nayak
While implementing DSS support for AM43xx I encountered a problem with clock
mux: clk mux may change the parent clock automatically, and with
set-rate-parent this leads to changing clocks for other devices. The problem is
described in more detail in the actual patch.
The problem doesn't seem to
When setting the rate of a clock, by default the clock framework will
change the parent of the clock to the most suitable one in
__clk_mux_determine_rate() (most suitable by looking at the clock rate).
This is a rather dangerous default, and causes problems on AM43x when
using display and
On 06/17/2014 11:04 AM, Tomi Valkeinen wrote:
When setting the rate of a clock, by default the clock framework will
change the parent of the clock to the most suitable one in
__clk_mux_determine_rate() (most suitable by looking at the clock rate).
This is a rather dangerous default, and causes
On Tue, 17 Jun 2014, Tomi Valkeinen wrote:
When setting the rate of a clock, by default the clock framework will
change the parent of the clock to the most suitable one in
__clk_mux_determine_rate() (most suitable by looking at the clock rate).
That is just insane.
This is a rather
On Tue, 17 Jun 2014, Tero Kristo wrote:
I am fine with this approach, as it seems pretty much all the other mux-clock
users are setting this flag also. The TI clocks have had this way of using mux
clocks from the legacy times... might just be a design flaw.
The non-CCF clock framework never
On 06/17/2014 11:19 AM, Paul Walmsley wrote:
On Tue, 17 Jun 2014, Tero Kristo wrote:
I am fine with this approach, as it seems pretty much all the other mux-clock
users are setting this flag also. The TI clocks have had this way of using mux
clocks from the legacy times... might just be a
From: Sathya Prakash M R sath...@ti.com
Add DSS hwmod data for AM43xx.
Signed-off-by: Sathya Prakash M R sath...@ti.com
[tomi.valkei...@ti.com: added missing dispc flags]
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
Acked-by: Rajendra Nayak rna...@ti.com
---
Changes to v1:
* added
* David R. Piegdon l...@p23q.org [140616 16:44]:
Fix a parser-bug in the omap2 muxing code where muxtable-entries will be
wrongly selected if the requested muxname is a *prefix* of their
m0-entry and they have a matching mN-entry. Fix by additionally checking
that the length of the m0_entry is
On Monday 16 June 2014 07:34 PM, Santosh Shilimkar wrote:
Sricharan,
On Monday 16 June 2014 07:23 AM, Sricharan R wrote:
This series does some cleanups, fixes for handling two interrupts
getting mapped twice to same crossbar and provides support for
hardwired IRQ and crossbar definitions.
* Tomi Valkeinen tomi.valkei...@ti.com [140617 01:39]:
From: Sathya Prakash M R sath...@ti.com
Add DSS hwmod data for AM43xx.
Signed-off-by: Sathya Prakash M R sath...@ti.com
[tomi.valkei...@ti.com: added missing dispc flags]
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
Acked-by:
On Mon, Jun 16, 2014 at 09:22:50AM -0400, Jason Kridner wrote:
Adding devicetree and linux-arm-kernel lists based on feedback on IRC...
On Tue, Jun 10, 2014 at 12:46 PM, Jason Kridner jkrid...@gmail.com wrote:
I'd like to discuss moving our current library of cape devicetree
overlay
On 17/06/14 11:58, Tony Lindgren wrote:
+/* rfbi */
I think we're still missing am43x_rfbi_sysc entry though?
+static struct omap_hwmod am43xx_dss_rfbi_hwmod = {
+.name = dss_rfbi,
+.class = omap2_rfbi_hwmod_class,
+.clkdm_name = dss_clkdm,
+
Some variants of the Pixcir touch controller support upto 5
simultaneous fingers and hardware tracking IDs. Prepare the driver
for that.
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/input/touchscreen/pixcir_i2c_ts.c | 74 ---
include/linux/input/pixcir_ts.h
Update the bindings for touchscreen size.
CC: Benoit Cousson bcous...@baylibre.com
CC: Tony Lindgren t...@atomide.com
CC: Mugunthan V N mugunthan...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/am43x-epos-evm.dts | 4 ++--
1 file changed, 2 insertions(+), 2
Switch to using the Type-B Multi-Touch protocol.
Reviewed-by: Henrik Rydberg rydb...@euromail.se
Signed-off-by: Roger Quadros rog...@ti.com
---
drivers/input/touchscreen/pixcir_i2c_ts.c | 125 ++
1 file changed, 94 insertions(+), 31 deletions(-)
diff --git
Update the bindings for touchscreen size.
CC: Benoit Cousson bcous...@baylibre.com
CC: Tony Lindgren t...@atomide.com
CC: Mugunthan V N mugunthan...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/am437x-gp-evm.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Hi Dmitry,
These are the pending patches that didn't go through in the 3.16 merge window.
Please queue them for -next. Thanks.
The series does the following
- convert to Type-B multi touch protocol
- support upto 5 fingers with hardware supplied tracking IDs
- device tree support
Tony,
The
Provide device tree support and binding information.
Also provide support for a new chip pixcir_tangoc.
Signed-off-by: Roger Quadros rog...@ti.com
---
.../bindings/input/touchscreen/pixcir_i2c_ts.txt | 26
.../devicetree/bindings/vendor-prefixes.txt| 1 +
* Roger Quadros rog...@ti.com [140617 02:33]:
Update the bindings for touchscreen size.
CC: Benoit Cousson bcous...@baylibre.com
CC: Tony Lindgren t...@atomide.com
CC: Mugunthan V N mugunthan...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
This too:
Acked-by: Tony Lindgren
* Roger Quadros rog...@ti.com [140617 02:33]:
Update the bindings for touchscreen size.
CC: Benoit Cousson bcous...@baylibre.com
CC: Tony Lindgren t...@atomide.com
CC: Mugunthan V N mugunthan...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
This should be fine to queue along with the
* Roger Quadros rog...@ti.com [140617 02:33]:
Hi Dmitry,
These are the pending patches that didn't go through in the 3.16 merge window.
Please queue them for -next. Thanks.
The series does the following
- convert to Type-B multi touch protocol
- support upto 5 fingers with hardware
On 06/17/2014 12:51 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [140617 02:33]:
Hi Dmitry,
These are the pending patches that didn't go through in the 3.16 merge
window.
Please queue them for -next. Thanks.
The series does the following
- convert to Type-B multi touch protocol
IP blocks within a clock domain generally come with their own CM_X_CLKCTRL
registers, each having it's own MODULEMODE field to manage the module. This is
not the case for DSS, though. DSS contains contains sub modules, each of which
are represented by hwmods, but DSS itself has only one register
DSS hwmods share the MODULEMODE field. Create a new 'mmode_shared' struct which
the DSS hwmods refer to.
This will allow the hwmods to reset properly during boot, and not break things
when the omapdss module is inserted.
(Note: hdmi and rfbi hwmods still don't reset properly as they don't have
Generally, IP blocks/modules within a clock domain come with their own
CM_x_CLKCTRL registers, each having it's own MODULEMODE field to manage the
module.
DSS clockdomain, however, has multiple modules in it, but only one register
named CM_DSS_DSS_CLKCTRL, which contains one MODULEMODE register
* Tomi Valkeinen tomi.valkei...@ti.com [140617 02:26]:
On 17/06/14 11:58, Tony Lindgren wrote:
+/* rfbi */
I think we're still missing am43x_rfbi_sysc entry though?
+static struct omap_hwmod am43xx_dss_rfbi_hwmod = {
+ .name = dss_rfbi,
+ .class =
ROM code on AM437x does not support writing to L2C-310 power control
register. The L2C driver, however, tries writing to this register for
all revisions = r3p0.
This leads to a warning dump on boot which leads most users to believe
that L2 cache is non-functional.
Since the problem is
Hi,
On Fri, Jun 13, 2014 at 3:59 PM, Tomasz Figa t.f...@samsung.com wrote:
I have attached, three patches which make the kernel boot fine with L2
cache enabled on ODROID-U3. Could you test them on your setup to verify
that they indeed fix the issue?
Nice work, now my ODROID-U2 boots fine.
On 06/17/2014 05:09 AM, Russell King - ARM Linux wrote:
On Mon, Jun 16, 2014 at 09:22:50AM -0400, Jason Kridner wrote:
Adding devicetree and linux-arm-kernel lists based on feedback on IRC...
On Tue, Jun 10, 2014 at 12:46 PM, Jason Kridner jkrid...@gmail.com wrote:
I'd like to discuss moving
On Tue, Jun 17, 2014 at 08:37:09AM -0400, Tom Rini wrote:
On 06/17/2014 05:09 AM, Russell King - ARM Linux wrote:
A good way that this could have been done is to put an I2C EEPROM on
each cape, and have that store the DT fragment. The boot loader could
have then read that from each cape,
On Tue, Jun 17, 2014 at 10:09:31AM +0100, Russell King wrote:
On Mon, Jun 16, 2014 at 09:22:50AM -0400, Jason Kridner wrote:
Adding devicetree and linux-arm-kernel lists based on feedback on IRC...
On Tue, Jun 10, 2014 at 12:46 PM, Jason Kridner jkrid...@gmail.com wrote:
I'd like to
On Tue, Jun 17, 2014 at 08:58:31AM -0400, Matt Porter wrote:
On Tue, Jun 17, 2014 at 10:09:31AM +0100, Russell King wrote:
Why should kernel developers go to the extent of adding support for DT
modification at runtime when the platform you want this for doesn't even
support hotplugging of
On Tue, Jun 17, 2014 at 11:37:13AM +0300, Tomi Valkeinen wrote:
From: Sathya Prakash M R sath...@ti.com
Add DSS hwmod data for AM43xx.
Signed-off-by: Sathya Prakash M R sath...@ti.com
[tomi.valkei...@ti.com: added missing dispc flags]
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
On Tue, Jun 17, 2014 at 04:04:51PM +0530, Sekhar Nori wrote:
ROM code on AM437x does not support writing to L2C-310 power control
register. The L2C driver, however, tries writing to this register for
all revisions = r3p0.
This leads to a warning dump on boot which leads most users to believe
On Tue, Jun 17, 2014 at 11:04:32AM +0300, Tomi Valkeinen wrote:
When setting the rate of a clock, by default the clock framework will
change the parent of the clock to the most suitable one in
__clk_mux_determine_rate() (most suitable by looking at the clock rate).
This is a rather dangerous
On Tue, Jun 17, 2014 at 02:15:22PM +0100, Russell King wrote:
On Tue, Jun 17, 2014 at 08:58:31AM -0400, Matt Porter wrote:
On Tue, Jun 17, 2014 at 10:09:31AM +0100, Russell King wrote:
Why should kernel developers go to the extent of adding support for DT
modification at runtime when the
Hi Russell,
CCing gcl.
On Jun 17, 2014, at 4:15 PM, Russell King - ARM Linux wrote:
On Tue, Jun 17, 2014 at 08:58:31AM -0400, Matt Porter wrote:
On Tue, Jun 17, 2014 at 10:09:31AM +0100, Russell King wrote:
Why should kernel developers go to the extent of adding support for DT
modification
On 06/17/2014 11:09 AM, Russell King - ARM Linux wrote:
Here's the most obvious question in the world on this topic. Are capes
hot-pluggable?
capes as in Beaglebone capes might not be due to the mechanical
constraints you listed.
capes as a concept of pluggable hardware might well be.
On Tue, 17 Jun 2014 10:09:31 +0100, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Mon, Jun 16, 2014 at 09:22:50AM -0400, Jason Kridner wrote:
Adding devicetree and linux-arm-kernel lists based on feedback on IRC...
On Tue, Jun 10, 2014 at 12:46 PM, Jason Kridner
On Monday 16 June 2014, Rob Herring wrote:
So far I have not come up with no great ideas on fixing this
properly short of requiring all omap .config files to add
CONFIG_ARCH_OMAP=y manually. Anybody got good ideas for that?
I've failed to come up with anything...
I have two ideas, but
Define ti_clk_register_dpll_x2() and of_ti_am3_dpll_x2_setup() if
AM43XX is defined.
Fixes the below boot issue.
[2.157258] gpmc_l3_clk not enabled
[2.161194] gpmc_l3_clk not enabled
[2.164896] Division by zero in kernel.
[2.169055] CPU: 0 PID: 321 Comm: kworker/u2:2 Tainted: G
On 17/06/14 10:09, Russell King - ARM Linux wrote:
Why should kernel developers go to the extent of adding support for DT
modification at runtime when the platform you want this for doesn't even
support hotplugging of these capes?
I'm not convinced you should, but Grant Likely seemed to be
The tilcdc driver could be compiled as a module, but was severely broken
and could not be used as such. This patchset attempts to fix the issues
preventing a proper load/unload of the module.
Issues included dangling sysfs nodes, dangling devices, memory leaks and
a double kfree.
It now seems to
Currently tda998x_encoder_destroy() calls cec_write() and reg_clear(),
as part of the release procedure. Such calls need to access the I2C bus
and therefore, we need to call them before drm_i2c_encoder_destroy()
which unregisters the I2C device.
This commit moves the latter so it's done
Add a drm_sysfs_connector_remove call when we destroy the panel to make
sure the connector node in sysfs gets deleted.
This is required for proper unload and re-load of this driver as a
module. Without this, we would get a warning at re-load time like so:
[ cut here ]
Add a drm_sysfs_connector_remove call when we destroy the panel to make
sure the connector node in sysfs gets deleted.
This is required for proper unload and re-load of this driver as a
module. Without this, we would get a warning at re-load time like so:
tda998x 0-0070: found TDA19988
The driver did not unregister the allocated framebuffer, which caused
memory leaks (and memory manager WARNs) when unloading. Also, the
framebuffer device under /dev still existed after unloading.
Add a call to drm_fbdev_cma_fini when unloading the module to prevent
both issues.
Signed-off-by:
Add a drm_sysfs_connector_remove call when we destroy the panel to make
sure the connector node in sysfs gets deleted.
This is required for proper unload and re-load of this driver, otherwise
we will get a warning about a duplicate filename in sysfs.
Signed-off-by: Guido Martínez
Use module_init instead of late_initcall, as is the norm for modular
drivers.
module_init was used until 6e8de0bd6a51fdeebd5d975c4fcc426f730b339b
(drm/tilcdc: add encoder slave (v2)) changed it to a late_initcall,
but it does not explain why. Tests show it's working properly with
module_init.
Unregister resources in the correct order on tilcdc_drm_fini, which is
the reverse order they were registered during tilcdc_drm_init.
This also means unregistering the driver before releasing its resources.
Signed-off-by: Guido Martínez gu...@vanguardiasur.com.ar
Cc: sta...@vger.kernel.org
The TI tilcdc driver is designed with a notion of submodules. Currently,
at unload time, these submodules are iterated and destroyed.
Now that the tilcdc remove order is fixed, this can be handled perfectly
by the kernel using the device infrastructure, since each submodule
is a kernel driver
display_timings_release calls kfree on the display_timings object passed
to it. Calling kfree after it is wrong. SLUB debug showed the following
warning:
=
BUG kmalloc-64 (Tainted: GW): Object already
On 06/17/2014 08:56 AM, Russell King - ARM Linux wrote:
On Tue, Jun 17, 2014 at 08:37:09AM -0400, Tom Rini wrote:
On 06/17/2014 05:09 AM, Russell King - ARM Linux wrote:
A good way that this could have been done is to put an I2C EEPROM on
each cape, and have that store the DT fragment. The
The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v3.16/fixes-against-rc1
for you to fetch changes up
On Tue, Jun 17, 2014 at 8:57 AM, Arnd Bergmann a...@arndb.de wrote:
On Monday 16 June 2014, Rob Herring wrote:
So far I have not come up with no great ideas on fixing this
properly short of requiring all omap .config files to add
CONFIG_ARCH_OMAP=y manually. Anybody got good ideas for that?
* Rob Herring robherri...@gmail.com [140617 08:05]:
On Tue, Jun 17, 2014 at 8:57 AM, Arnd Bergmann a...@arndb.de wrote:
On Monday 16 June 2014, Rob Herring wrote:
So far I have not come up with no great ideas on fixing this
properly short of requiring all omap .config files to add
On 06/05/2014 10:35 PM, Nishanth Menon wrote:
Hi,
The following series is a minimal set of cleanups and generalization
in the direction of supporting daisychain wakeup on all OMAP4+
platforms. We cannot still add IO_WAKEUP ability for OMAP5/DRA7/AM437x
yet pending further pinctrl patches.
On Tue, Jun 17, 2014 at 04:32:11PM +0300, Pantelis Antoniou wrote:
The complexity is absolutely required, and it has nothing to do with
beaglebone capes.
The fact of the matter is that reconfigurable hardware is here, on
shipping system, and we, as the linux kernel community have to make
Add tps65917 specific definitions and enums.
Signed-off-by: Keerthy j-keer...@ti.com
---
include/linux/mfd/palmas.h | 793
1 file changed, 793 insertions(+)
Acked-by: Lee Jones lee.jo...@linaro.org
diff --git a/include/linux/mfd/palmas.h
Add tps65917 PMIC support. tps65917 is a subset of palmas PMIC.
Some of the register definitions and the interrupt mappings
are different.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 176
--
1 file changed, 171
On Tue, Jun 17, 2014 at 12:01 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Tue, Jun 17, 2014 at 04:32:11PM +0300, Pantelis Antoniou wrote:
The complexity is absolutely required, and it has nothing to do with
beaglebone capes.
The fact of the matter is that reconfigurable
On Wed, 28 May 2014, Keerthy wrote:
Shift the reg_info structure definition to the header file.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/regulator/palmas-regulator.c |9 -
include/linux/mfd/palmas.h |9 +
2 files changed, 9 insertions(+), 9
On Wed, 28 May 2014, Keerthy wrote:
shift the palmas_sleep_requestor_info structure definition to the header file.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 10 --
include/linux/mfd/palmas.h | 10 ++
2 files changed, 10 insertions(+), 10
On Wed, 28 May 2014, Keerthy wrote:
Add palmas_pmic_driver_data structure.
Signed-off-by: Keerthy j-keer...@ti.com
---
include/linux/mfd/palmas.h | 25 +
1 file changed, 25 insertions(+)
diff --git a/include/linux/mfd/palmas.h b/include/linux/mfd/palmas.h
On Tue, Jun 17, 2014 at 10:25 AM, Tony Lindgren t...@atomide.com wrote:
* Rob Herring robherri...@gmail.com [140617 08:05]:
On Tue, Jun 17, 2014 at 8:57 AM, Arnd Bergmann a...@arndb.de wrote:
On Monday 16 June 2014, Rob Herring wrote:
So far I have not come up with no great ideas on fixing
On Tue, Jun 17, 2014 at 3:11 AM, Gupta, Pekon pe...@ti.com wrote:
Hi Jason,
From: Jason Kridner
Adding devicetree and linux-arm-kernel lists based on feedback on IRC...
On Tue, Jun 10, 2014 at 12:46 PM, Jason Kridner jkrid...@gmail.com wrote:
I'd like to discuss moving our current library of
add driver data and modularize the probe.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 42 +--
drivers/regulator/palmas-regulator.c | 656
--
2 files changed, 395 insertions(+), 303 deletions(-)
diff --git
Hi Russell,
On Jun 17, 2014, at 7:01 PM, Russell King - ARM Linux wrote:
On Tue, Jun 17, 2014 at 04:32:11PM +0300, Pantelis Antoniou wrote:
The complexity is absolutely required, and it has nothing to do with
beaglebone capes.
The fact of the matter is that reconfigurable hardware is here,
On Tue, Jun 17, 2014 at 07:59:21PM +0300, Pantelis Antoniou wrote:
That case might already work on FPGA people's trees. I know Altera for sure
uses overlays, and some xilinx guys popped up on past discussions.
Their vendor trees probably use an older revision of the patches.
BTW, there is
Hi Russell,
On Jun 17, 2014, at 8:05 PM, Russell King - ARM Linux wrote:
On Tue, Jun 17, 2014 at 07:59:21PM +0300, Pantelis Antoniou wrote:
That case might already work on FPGA people's trees. I know Altera for sure
uses overlays, and some xilinx guys popped up on past discussions.
Their
On Tue, Jun 17, 2014 at 08:10:46PM +0300, Pantelis Antoniou wrote:
Hi Russell,
On Jun 17, 2014, at 8:05 PM, Russell King - ARM Linux wrote:
DRM is not hotpluggable in any shape or form, and David Airlie has
indicated that he does strongly opposes moving it in that direction.
DRM
Hi Rusell,
On Jun 17, 2014, at 8:41 PM, Russell King - ARM Linux wrote:
On Tue, Jun 17, 2014 at 08:10:46PM +0300, Pantelis Antoniou wrote:
Hi Russell,
On Jun 17, 2014, at 8:05 PM, Russell King - ARM Linux wrote:
DRM is not hotpluggable in any shape or form, and David Airlie has
indicated
Quoting Paul Walmsley (2014-06-17 01:15:09)
On Tue, 17 Jun 2014, Tomi Valkeinen wrote:
When setting the rate of a clock, by default the clock framework will
change the parent of the clock to the most suitable one in
__clk_mux_determine_rate() (most suitable by looking at the clock rate).
Quoting Tero Kristo (2014-06-17 01:23:31)
On 06/17/2014 11:19 AM, Paul Walmsley wrote:
On Tue, 17 Jun 2014, Tero Kristo wrote:
I am fine with this approach, as it seems pretty much all the other
mux-clock
users are setting this flag also. The TI clocks have had this way of using
mux
Hi,
On Mon, Jun 16, 2014 at 12:27:21AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140613 09:33]:
On Fri, Jun 13, 2014 at 11:23:34AM -0500, Felipe Balbi wrote:
On Fri, Jun 13, 2014 at 11:15:47AM -0500, Felipe Balbi wrote:
--- /dev/null
+++
On Tuesday 17 June 2014 10:15 PM, Lee Jones wrote:
add driver data and modularize the probe.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 42 +--
drivers/regulator/palmas-regulator.c | 656 --
2 files changed, 395
On Tuesday 17 June 2014 10:07 PM, Lee Jones wrote:
On Wed, 28 May 2014, Keerthy wrote:
Add palmas_pmic_driver_data structure.
Signed-off-by: Keerthy j-keer...@ti.com
---
include/linux/mfd/palmas.h | 25 +
1 file changed, 25 insertions(+)
diff --git
On Tuesday 17 June 2014 10:03 PM, Lee Jones wrote:
On Wed, 28 May 2014, Keerthy wrote:
shift the palmas_sleep_requestor_info structure definition to the header file.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 10 --
include/linux/mfd/palmas.h | 10
On Tuesday 17 June 2014 10:02 PM, Lee Jones wrote:
On Wed, 28 May 2014, Keerthy wrote:
Shift the reg_info structure definition to the header file.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/regulator/palmas-regulator.c |9 -
include/linux/mfd/palmas.h |9
On Tuesday 17 June 2014 09:49 PM, Lee Jones wrote:
Add tps65917 PMIC support. tps65917 is a subset of palmas PMIC.
Some of the register definitions and the interrupt mappings
are different.
Signed-off-by: Keerthy j-keer...@ti.com
---
drivers/mfd/palmas.c | 176
On Tuesday 17 June 2014 09:41 PM, Lee Jones wrote:
Add tps65917 specific definitions and enums.
Signed-off-by: Keerthy j-keer...@ti.com
---
include/linux/mfd/palmas.h | 793
1 file changed, 793 insertions(+)
Acked-by: Lee Jones
85 matches
Mail list logo
