The patch series add DT support on TPS65090 device.
Also remove the suspend/resume implementation as it duplicates with
irq_suspend/irq_resume().
Resending this patch series incase of it is missed.
Laxman Dewangan (4):
mfd: tps65090: add DT support for tps65090
regulator: tps65090: add DT
Add DT support for TI PMIC tps65090 regulator driver. The DT of this
device have node regulator and all regulator's node of this device is
added under this node.
The device tree binding document has the required information for
adding this device on DTS file.
Signed-off-by: Laxman Dewangan
When device is get added through DT then irq_base is 0 (zero)
and in this case regmap_irq_chip_get_base() generates warning.
The interrupt of this device get added through irq_domain_add_linear()
when irq_base is 0.
Hence pass the irq domain in place of base_irq when calling
mfd_add_devices().
Add device tree support for the TI PMIC TPS65090.
The device can be registered through platform or DT.
Add device tree binding document for this device.
Signed-off-by: Laxman Dewangan ldewan...@nvidia.com
---
.../devicetree/bindings/regulator/tps65090.txt | 121
The tps65090 mfd driver implement the suspend/resume callbacks
which just disable and enable irqs in suspend/resume respectively.
This operation is already done in irq suspend and irq_resume and
hence it is not require to implement the same in the driver.
Remove this non-require code.
On Tuesday 22 January 2013 03:37 PM, Linus Walleij wrote:
On Tue, Jan 22, 2013 at 10:54 AM, Rajendra Nayak rna...@ti.com wrote:
On Tuesday 22 January 2013 01:52 PM, Linus Walleij wrote:
In the Nomadik I had a similar situation with a GPIO used for the
ethernet IRQ. I put the GPIO number in a
P == Patil, Rachna rac...@ti.com writes:
Hi,
P From: Patil, Rachna rac...@ti.com
P Signed-off-by: Patil, Rachna rac...@ti.com
P ---
P Changes in v4:
P Subnodes and their properties documentation added.
P Non-standard properties prefixed with vendor name.
P
This commit which changed the behaviour of this function broke one
of the tests. Also the comment should be updated to reflect its new
behaviour.
Signed-off-by: Simon Glass s...@chromium.org
---
Changes in v2:
- Add new test to check byte output of a string list property
tests/run_tests.sh | 3
Hi David,
On Tue, Jan 22, 2013 at 6:33 PM, David Gibson
da...@gibson.dropbear.id.au wrote:
On Mon, Jan 21, 2013 at 12:59:15PM -0800, Simon Glass wrote:
This commit which changed the behaviour of this function broke one
of the tests. Also the comment should be updated to reflect its new
On Sun, Jan 27, 2013 at 08:36:00PM +0100, Hauke Mehrtens wrote:
Hi,
when building 3.8-rc5 I get the following section mismatch:
WARNING: drivers/w1/masters/w1-gpio.o(.data+0x188): Section mismatch in
reference from the variable w1_gpio_driver to the function
.init.text:w1_gpio_probe()
This commit which changed the behaviour of this function broke one
of the tests. Also the comment should be updated to reflect its new
behaviour.
Signed-off-by: Simon Glass s...@chromium.org
---
Changes in v2:
- Add new test to check byte output of a string list property
Applied.
The function that prints a property can be useful to other programs,
so move it into util.
Signed-off-by: Simon Glass s...@chromium.org
Applied.
Thanks,
jdl
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
Ignore any patch files that we find, since these are likely to be
used when sending patches upstream.
Signed-off-by: Simon Glass s...@chromium.org
Applied.
Thanks,
jdl
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
This function is useful outside libfdt, so export it.
Signed-off-by: Simon Glass s...@chromium.org
Applied.
Thanks,
jdl
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
Hi,
On 01/25/2013 11:39 AM, Rahul Sharma wrote:
Signed-off-by: Rahul Sharmarahul.sha...@samsung.com
Please explain why this patch is needed, in more detail...
---
arch/arm/boot/dts/exynos4.dtsi | 1 -
arch/arm/boot/dts/exynos4412-origen.dts | 13 +
2 files changed,
Hi,
On 01/25/2013 11:39 AM, Rahul Sharma wrote:
This patch enables hdmi support for Samsung Exynos4412 soc based Origen Board.
This set is base on for next branch at
git.kernel.org/?p=linux/kernel/git/kgene/linux-samsung.git
Rahul Sharma (4):
ARM: dts: add support for hdmi to exynos4
On 01/25/2013 11:39 AM, Rahul Sharma wrote:
Signed-off-by: Rahul Sharmarahul.sha...@samsung.com
Please provide proper commit text.
Conflicts:
arch/arm/mach-exynos/mach-exynos4-dt.c
And make sure things like this are removed when submitting patches.
---
On 01/25/2013 11:39 AM, Rahul Sharma wrote:
diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arch/arm/boot/dts/exynos4.dtsi
index 6c2c79d..07cb7d4 100644
--- a/arch/arm/boot/dts/exynos4.dtsi
+++ b/arch/arm/boot/dts/exynos4.dtsi
@@ -296,4 +296,12 @@
interrupts =0 95 0;
On 01/25/2013 12:21 PM, Paul Gortmaker wrote:
From: Thomas Gleixner t...@linutronix.de
There is no real reason to use a rwlock for devtree_lock. It even
could be a mutex, but unfortunately it's locked from cpu hotplug
paths which can't schedule :(
So it needs to become a raw lock on rt as
libfdt.h is the libfdt interface definition. It includes fdt.h and
libfdt_env.h, so there is no reason to include those in the general code.
Signed-off-by: Gerald Van Baren vanba...@cideas.com
---
No code changes, just cleaning up the #include situation WRT libfdt.h,
fdt.h, and libfdt_env.h
Arguably they belong there since they are fundamental to the fdt.
As a side effect, I had to flip the order of #includes of fdt.h and
libfdt_env.h in libfdt.h since libfdt_env.h needs the fdt*_t definitions.
Signed-off-by: Gerald Van Baren g...@unssw.com
---
I'm not sure I like this, but submit
On Sun, Jan 27, 2013 at 09:44:37PM -0500, Gerald Van Baren wrote:
Arguably they belong there since they are fundamental to the fdt.
As a side effect, I had to flip the order of #includes of fdt.h and
libfdt_env.h in libfdt.h since libfdt_env.h needs the fdt*_t definitions.
Signed-off-by:
22 matches
Mail list logo
