Hi Bjorn,
On Wed, 2015-06-17 at 23:47 -0700, Bjorn Andersson wrote:
When the MPP is configured for analog output the output level is selected by
the AOUT_CTL register, this patch makes it possible to control this.
snip
}
@@ -748,6 +765,10 @@ static int pmic_mpp_populate(struct
On Wed, Jun 24, 2015 at 9:06 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
Adding Mike's new email address..
On 23-06-15, 23:31, Pi-Cheng Chen wrote:
On Mon, Jun 8, 2015 at 8:29 PM, Pi-Cheng Chen pi-cheng.c...@linaro.org
wrote:
This patch adds device tree binding document for MT8173
Just a small update to this series with a memory corruption bug fixed.
This series adds support for the MediaTek SCPSYS unit.
The SCPSYS unit handles several power management related tasks such
as thermal measurement, DVFS, interrupt filter and low level sleep
control.
The initial support only
This adds documentation for the MediaTek SCPSYS unit found in MT8173 SoCs.
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
---
.../devicetree/bindings/soc/mediatek/scpsys.txt| 41 ++
1 file changed, 41 insertions(+)
create mode 100644
For non-dt platform (eg i686), how it changes otg capabilities
through their platform data?
Directly override platdata-ci_otg_caps in its platform driver after
ci_hdrc_add_device().
After ci_hdrc_add_device, the device may begin to enumerate, we need
to make sure otg
On Tue, 23 Jun 2015, Paul Osmialowski wrote:
+/*
+ * Clock event device set mode function
+ */
+static void kinetis_clockevent_tmr_set_mode(
+ enum clock_event_mode mode, struct clock_event_device *clk)
+{
+ struct kinetis_clock_event_ddata *pit =
+ container_of(clk,
On Wed, 2015-06-17 at 23:47 -0700, Bjorn Andersson wrote:
This series starts out by fixing various issues found in the pm8941 mpp
driver.
While doing this work, and trying to use the mpp driver from device tree it,
it
became obvious that the current binding is not fit for neither the
On 06/23/2015 08:07 PM, Dmitry Torokhov wrote:
On Tue, Jun 23, 2015 at 10:23:57AM -0700, Matt Ranostay wrote:
On Tue, Jun 23, 2015 at 1:36 AM, Jacek Anaszewski
j.anaszew...@samsung.com wrote:
On 06/22/2015 07:59 PM, Dmitry Torokhov wrote:
On Wed, Jun 17, 2015 at 08:58:16PM -0700, Matt
On 24-06-15, 16:44, Pi-Cheng Chen wrote:
One reason to put those initialization and resource allocation in probe is
that it's easier to handle the return value -PROBE_DEFER from clock
and regulator framework when trying to get clocks and regulators
consumed by cpufreq driver.
This is the
On Wed, Jun 24, 2015 at 4:56 PM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 24-06-15, 16:44, Pi-Cheng Chen wrote:
One reason to put those initialization and resource allocation in probe is
that it's easier to handle the return value -PROBE_DEFER from clock
and regulator framework when
On 06/24/2015 09:28 AM, Jacek Anaszewski wrote:
On 06/23/2015 08:07 PM, Dmitry Torokhov wrote:
On Tue, Jun 23, 2015 at 10:23:57AM -0700, Matt Ranostay wrote:
On Tue, Jun 23, 2015 at 1:36 AM, Jacek Anaszewski
j.anaszew...@samsung.com wrote:
On 06/22/2015 07:59 PM, Dmitry Torokhov wrote:
On
Hello,
This patchset adds a dt binding for specifying sample time
for the vybrid adc driver and takes this into account for
sampling frequency calculation and related configuration in
the driver.
The patchset is based on top of Stefan's patches here
Hi Simon,
On 06/23/2015 11:17 PM, Simon Guinot wrote:
On Tue, Jun 23, 2015 at 02:11:54PM +0200, Jacek Anaszewski wrote:
Hi Simon,
Hi Jacek,
Thanks again for taking care of this patch set.
On 06/18/2015 04:59 PM, Simon Guinot wrote:
This patch adds device tree support for the netxbig
On 21.06.2015 17:14, Jonathan Cameron wrote:
I'd call this a threshold detector. The device seems to have two
comparators for each channel, one for the lower threshold, one for
the upper threshold. If the voltage level goes above the upper
threshold a FF is set, if it goes below the lower
Add DT support to the 88pm800 driver, along with compatible
field for it's sub-devices (rtc, onkey and regulator)
Signed-off-by: Chao Xie chao@marvell.com
Signed-off-by: Vaibhav Hiremath vaibhav.hirem...@linaro.org
---
drivers/mfd/88pm800.c | 25 +
1 file changed, 25
With addition of DT support to 88pm800 mfd driver, this patch
adds new DT binding documentation along with respective properties.
Signed-off-by: Vaibhav Hiremath vaibhav.hirem...@linaro.org
Acked-by: Rob Herring r...@kernel.org
---
Documentation/devicetree/bindings/mfd/88pm800.txt | 60
Add NAND device nodes to BMIPS based BCM7362 platform.
Signed-off-by: Jaedon Shin jaedon.s...@gmail.com
---
arch/mips/boot/dts/brcm/bcm7362.dtsi | 22 ++
arch/mips/boot/dts/brcm/bcm97362svmb.dts | 23 +++
2 files changed, 45 insertions(+)
diff --git
Add NAND device nodes to BMIPS based BCM7360 platform.
Signed-off-by: Jaedon Shin jaedon.s...@gmail.com
---
arch/mips/boot/dts/brcm/bcm7360.dtsi | 22 ++
arch/mips/boot/dts/brcm/bcm97360svmb.dts | 23 +++
2 files changed, 45 insertions(+)
diff --git
Hi all,
This patch series contain changing device nodes of the bcm7xxx platforms.
Jaedon Shin (4):
MIPS: BMIPS: bcm7346: add nodes for NAND
MIPS: BMIPS: bcm7358: add nodes for NAND
MIPS: BMIPS: bcm7360: add nodes for NAND
MIPS: BMIPS: bcm7362: add nodes for NAND
Add NAND device nodes to BMIPS based BCM7358 platform.
Signed-off-by: Jaedon Shin jaedon.s...@gmail.com
---
arch/mips/boot/dts/brcm/bcm7358.dtsi | 22 ++
arch/mips/boot/dts/brcm/bcm97358svmb.dts | 23 +++
2 files changed, 45 insertions(+)
diff --git
Add NAND device nodes to BMIPS based BCM7346 platform.
Signed-off-by: Jaedon Shin jaedon.s...@gmail.com
---
arch/mips/boot/dts/brcm/bcm7346.dtsi | 22 ++
arch/mips/boot/dts/brcm/bcm97346dbsmb.dts | 23 +++
2 files changed, 45 insertions(+)
diff --git
Hi,
On 24-06-15 09:28, Maxime Ripard wrote:
Hi,
On Wed, Jun 24, 2015 at 09:16:54AM +0200, Hans de Goede wrote:
Maxime I think we should send the mentioned dts patch to stable for
4.1 , do you agree ?
Yep. We should definitely do that. You take care of this?
Yes I'll try to do so later
The driver currently does not take into account the minimum sample time
as per the Figure 6-8 Chapter 9.1.1 12-bit ADC electrical characteristics.
We set a static amount of cycles instead of considering the sample time
as a given value, which depends on hardware characteristics.
Determine
Add a device tree property which allows to specify the minimum sample
time which can be used to calculate the actual ADC cycles required
depending on the hardware.
Signed-off-by: Sanchayan Maity maitysancha...@gmail.com
---
arch/arm/boot/dts/vfxxx.dtsi | 2 ++
1 file changed, 2 insertions(+)
Hi Viresh,
On Wed, Jun 24, 2015 at 8:57 AM, Viresh Kumar viresh.ku...@linaro.org wrote:
On 23-06-15, 23:25, Pi-Cheng Chen wrote:
On Mon, Jun 22, 2015 at 7:45 PM, Viresh Kumar viresh.ku...@linaro.org
wrote:
+static struct mtk_cpu_dvfs_info *mtk_cpu_dvfs_info_get(int cpu)
A very bad name
This adds a power domain driver for the Mediatek SCPSYS unit.
The System Control Processor System (SCPSYS) has several power
management related tasks in the system. The tasks include thermal
measurement, dynamic voltage frequency scaling (DVFS), interrupt
filter and lowlevel sleep control. The
This adds support for some miscellaneous bits of the infracfg controller.
The mtk_infracfg_set/clear_bus_protection functions are necessary for
the scpsys power domain driver to handle the bus protection bits which
are contained in the infacfg register space.
Signed-off-by: Sascha Hauer
This adds the SCPSYS device node to the MT8173 dtsi file.
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
On Wed, Jun 24, 2015 at 11:49:23AM +0800, Peter Chen wrote:
On Wed, Jun 24, 2015 at 11:34:23AM +0800, Li Jun wrote:
On Wed, Jun 24, 2015 at 11:04:43AM +0800, Peter Chen wrote:
On Wed, Jun 17, 2015 at 07:40:15PM +0800, Li Jun wrote:
Set gadget's otg capabilities according to controller's
Hi Heiko,
On Mon, 2015-06-22 at 14:53 +0200, Heiko Stübner wrote:
Hi James,
Am Montag, 22. Juni 2015, 11:38:37 schrieb James Liao:
On Fri, 2015-06-19 at 13:36 +0200, Heiko Stuebner wrote:
Some clocks such as clkph_mck_o, we don't really care where they come
from and what frequencies
On Wed 2015-06-24 10:32:54, Laurentiu Palcu wrote:
On Sat, May 02, 2015 at 04:59:34PM +0200, Pavel Machek wrote:
Should this link
More details about the chip can be found here:
http://www.ti.com/product/bq25890
@@ -0,0 +1,998 @@
+/*
+ * TI BQ25890 charger driver
+
As per the spec, bit 1 (INT_CLEAR_MODE) of reg addr 0xe
(page 0) controls the method of clearing interrupt
status of 88pm800 family of devices;
0: clear on read
1: clear on write
This patch allows to configure this field, through DT.
Also, as suggested by Lee Jones renaming DT property and
Hi,
On 23-06-15 21:54, Dmitry Torokhov wrote:
On Tue, Jun 23, 2015 at 09:46:20PM +0200, Hans de Goede wrote:
Hi,
On 06/23/2015 05:06 PM, m.silentcr...@gmail.com wrote:
Hi Hans,
is it possible that this patch (and the parent commit Input: sun4i-ts - allow
controlling filter and sensitivity
On Sat, May 02, 2015 at 04:59:34PM +0200, Pavel Machek wrote:
Should this link
More details about the chip can be found here:
http://www.ti.com/product/bq25890
@@ -0,0 +1,998 @@
+/*
+ * TI BQ25890 charger driver
+ *
+ * Copyright (C) 2015 Intel Corporation
+ *
+ * This
On Tue, 23 Jun 2015, Paul Bolle wrote:
On Tue, 2015-06-23 at 09:28 +0100, Lee Jones wrote:
BTW, do you have a script that does this now, or are you still
hand-rolling these?
There was a script detecting Kconfig problems that is basically
retired. (The messages I sent were always manually
On Wed, Jun 24, 2015 at 3:42 AM, Chen-Yu Tsai w...@csie.org wrote:
On Tue, Jun 23, 2015 at 5:30 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sun, Jun 14, 2015 at 12:42:21PM +0200, Hans de Goede wrote:
Currently we are reporting the button state as inverted on all boards with
an
Several cap11xx variants have LEDs that be can be controlled, this
patchset implements this functionality.
Signed-off-by: Matt Ranostay mranos...@gmail.com
---
drivers/input/keyboard/cap11xx.c | 140 ++-
1 file changed, 137 insertions(+), 3 deletions(-)
diff
Signed-off-by: Matt Ranostay mranos...@gmail.com
---
Documentation/devicetree/bindings/input/cap11xx.txt | 19 +++
1 file changed, 19 insertions(+)
diff --git a/Documentation/devicetree/bindings/input/cap11xx.txt
b/Documentation/devicetree/bindings/input/cap11xx.txt
index
On 24-06-15, 16:57, Pi-Cheng Chen wrote:
Yes. So should it be:
- operating-points: Refer to
Documentation/devicetree/bindings/power/opp.txt
for details
Right.
--
viresh
--
To unsubscribe from this list: send the line unsubscribe devicetree in
the body of a message to
On Wed, Jun 24, 2015 at 10:30:58AM +0200, Pavel Machek wrote:
On Wed 2015-06-24 10:32:54, Laurentiu Palcu wrote:
On Sat, May 02, 2015 at 04:59:34PM +0200, Pavel Machek wrote:
Should this link
More details about the chip can be found here:
http://www.ti.com/product/bq25890
On 23/06/15 21:28, Stefan Wahren wrote:
@@ -26,6 +35,21 @@ void devm_nvmem_cell_put(struct device *dev, struct
nvmem_cell *cell);
void *nvmem_cell_read(struct nvmem_cell *cell, ssize_t *len);
int nvmem_cell_write(struct nvmem_cell *cell, void *buf, ssize_t len);
+/* direct nvmem device
On 23/06/15 21:35, Stefan Wahren wrote:
+Required properties:
+reg: specifies the offset in byte within that storage device, start bit
+ in the byte and the length in bits of the data we care about.
Is the second parameter really in bits, not bytes?
Thanks for spotting this, I will fix this.
On 23/06/15 21:16, Stefan Wahren wrote:
+
+struct device;
Do we need forward declaration of struct device_node too?
Yep, Will fix it in next version.
--srini
+/* consumer cookie */
[...]
--
To unsubscribe from this list: send the line unsubscribe devicetree in
the body of a message to
On Tue, 23 Jun 2015 17:28:48 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Deprecate using phy-omap-control driver to set PCS value of the PHY
and start using *syscon* framework to do the same.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
On Tue, 23 Jun 2015 17:28:50 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
The USB2 PHY2 has a different register map compared to USB2 PHY1
to power on/off the PHY. In order to handle it, add a new
compatible string.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
On 23/06/15 10:25, Rajendra Nayak wrote:
[]..
+Example:
+
+qfprom: qfprom@0070 {
+compatible = qcom,qfprom;
+reg= 0x0070 0x8000;
+...
+/* Data cells */
+tsens_calibration: calib@404 {
+reg = 0x4404 0x10;
+};
* Kishon Vijay Abraham I kis...@ti.com [150623 05:02]:
Deprecate using phy-omap-control driver to write to the mailbox register
and start using *syscon* framework to do the same.
All this stuff needs to go to some generic syscon USB phy
driver. Let's not start adding phy specific stuff to a USB
On Wed, 24 Jun 2015 14:50:17 +0300
Roger Quadros rog...@ti.com wrote:
On Tue, 23 Jun 2015 17:28:53 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Add new device tree node for the control module register space where
PCIe registers are present.
Signed-off-by: Kishon Vijay Abraham I
On 23/06/15 20:47, Stefan Wahren wrote:
0001000
i want to port OCOTP driver for MXS, which hasn't MMIO. From my understanding
That's cool.
hexdump would readout the complete register range defined in provider DT node.
How can i achieve that hexdump only reads the data area within the
On Tue, 2015-06-23 at 23:19 +0200, Paul Osmialowski wrote:
--- a/drivers/pinctrl/freescale/Kconfig
+++ b/drivers/pinctrl/freescale/Kconfig
+config PINCTRL_KINETIS
+ bool Kinetis pinctrl driver
+ depends on OF
+ depends on SOC_K70
+ select PINMUX
+ help
+ Say Y
Just cosmetic comments.
added device tree support to gpio-generic driver
- Please use the present tense in your commit subject
- Please prefix the subject with a word describing which area your
patch is related to, in this case gpio:
So, your patch subject can be improved as gpio: add
On Wed, 24 Jun 2015 03:41:16 -0700
Tony Lindgren t...@atomide.com wrote:
* Kishon Vijay Abraham I kis...@ti.com [150623 05:02]:
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -852,12 +852,6 @@
};
};
-
On Thu, Jun 4, 2015 at 8:53 PM, Geert Uytterhoeven
geert+rene...@glider.be wrote:
--- a/arch/arm/mach-shmobile/pm-rcar.c
+++ b/arch/arm/mach-shmobile/pm-rcar.c
@@ -51,11 +54,29 @@
static void __iomem *rcar_sysc_base;
static DEFINE_SPINLOCK(rcar_sysc_lock); /* SMP CPUs + I/O devices */
Hi,
On Wednesday 24 June 2015 05:03 PM, Roger Quadros wrote:
On Tue, 23 Jun 2015 17:28:51 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Deprecate using phy-omap-control driver to power on/off the PHY,
and use *syscon* framework to do the same. This handles
powering on/off the PHY for
On 23/06/15 21:44, Stefan Wahren wrote:
Srinivas Kandagatla srinivas.kandaga...@linaro.org hat am 23. Juni 2015 um
01:09 geschrieben:
From: Maxime Ripard maxime.rip...@free-electrons.com
Now that we have the nvmem framework, we can consolidate the common
driver code. Move the driver to
On Tue, 23 Jun 2015 17:28:51 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Deprecate using phy-omap-control driver to power on/off the PHY,
and use *syscon* framework to do the same. This handles
powering on/off the PHY for the USB2 PHYs used in various TI SoCs.
Signed-off-by: Kishon
On 24/06/15 01:24, Stephen Boyd wrote:
Can you assign the attributes to the device_type in the nvmem::struct
device? I don't see why these attributes need to be part of the class.
I will fix this.
+{
+return class_register(nvmem_class);
I thought class was on the way out? Aren't we
* Kishon Vijay Abraham I kis...@ti.com [150623 05:02]:
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -852,12 +852,6 @@
};
};
- omap_control_usbotg: control-phy@4a00233c {
- compatible =
On Tue, 23 Jun 2015 17:28:49 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
No functional change. Previously omap_control_phy_power() was used to power
off the PHY during probe. But once phy-omap-usb2 driver is adapted to
use syscon, omap_control_phy_power() cannot be used. Hence used
On Wed, Jun 10, 2015 at 10:42 AM, Linus Walleij
linus.wall...@linaro.org wrote:
On Fri, Jun 5, 2015 at 8:51 AM, Romain Baeriswyl
romain.baeris...@alitech.com wrote:
+Required properties:
+- compatible : basic-mmio-gpio for little endian register access or
+ basic-mmio-gpio-be
Hi Tony,
On Wednesday 24 June 2015 04:11 PM, Tony Lindgren wrote:
* Kishon Vijay Abraham I kis...@ti.com [150623 05:02]:
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -852,12 +852,6 @@
};
};
-
Add a cell for the usb power_supply part of the axp20x PMICs.
Why are you duplicating the subject line?
Note that this cell is only for the usb power_supply part and not the
ac-power / battery-charger / rtc-backup-bat-charger bits.
Depending on the board each of those must be enabled /
Hi,
On Tuesday 23 June 2015 08:23 PM, Roger Quadros wrote:
Hi Kishon,
On Tue, 23 Jun 2015 17:28:47 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Deprecate using phy-omap-control driver to power on/off the PHY and
use *syscon* framework to do the same.
Signed-off-by: Kishon Vijay Abraham
* Kishon Vijay Abraham I kis...@ti.com [150624 04:23]:
On Wednesday 24 June 2015 04:11 PM, Tony Lindgren wrote:
* Kishon Vijay Abraham I kis...@ti.com [150623 05:02]:
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -852,12 +852,6 @@
};
Hi Srinivas,
Am 24.06.2015 um 11:46 schrieb Srinivas Kandagatla:
On 23/06/15 20:47, Stefan Wahren wrote:
0001000
i want to port OCOTP driver for MXS, which hasn't MMIO. From my
understanding
That's cool.
hexdump would readout the complete register range defined in provider
DT node.
On Wed, Jun 24, 2015 at 2:17 PM, Sascha Hauer s.ha...@pengutronix.de wrote:
Just a small update to this series with a memory corruption bug fixed.
This series adds support for the MediaTek SCPSYS unit.
The SCPSYS unit handles several power management related tasks such
as thermal
On Sat, 13 Jun 2015, Hans de Goede wrote:
This adds a driver for the usb power_supply bits of the axp20x PMICs.
I initially started writing my own driver, before coming aware of
Bruno Prémont's excellent earlier RFC with a driver for this.
My driver was lacking CURRENT_MAX and VOLTAGE_MIN
On Fri, 2015-06-19 at 10:43 +0200, Michael van der Westhuizen wrote:
The commit dd11444327ce (spi: dw-spi: Convert 16bit accesses to
32bit
accesses) changed all 16bit accesses in the DW_apb_ssi driver to
32bit.
This, unfortunately, breaks data register access on picoXcell, where
the
DW
On Tue, 23 Jun 2015 17:28:56 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
The USB2 PHY2 has a different register map compared to USB2 PHY1
to power on/off the PHY. In order to handle it, use the new compatible
string ti,dra7x-usb2-phy2 for the second instance of USB2 PHY.
* Roger Quadros rog...@ti.com [150624 04:58]:
On Wed, 24 Jun 2015 14:50:17 +0300
Roger Quadros rog...@ti.com wrote:
On Tue, 23 Jun 2015 17:28:53 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Add new device tree node for the control module register space where
PCIe registers
Add optional interrupt support to the da9210 regulator driver, to handle
over-current, under- and over-voltage, and over-temperature events.
Only the interrupt sources for which we handle events are unmasked, to
avoid interrupts we cannot handle.
Signed-off-by: Geert Uytterhoeven
On 24/06/15 13:30, Stefan Wahren wrote:
If the question is just about hexdump, then hexdump itself can read
file from given offset and size.
yes, this is my question at first. Let me show the difference between
the current implementation and my expectations as a user.
$ hexdump
On 23/06/15 10:26, Pantelis Antoniou wrote:
Hi Joe,
On Jun 23, 2015, at 05:52 , Joe Perchesj...@perches.com wrote:
On Tue, 2015-06-23 at 00:08 +0100, Srinivas Kandagatla wrote:
This patch adds just providers part of the framework just to enable easy
review.
[]
Hi James,
Am Mittwoch, 24. Juni 2015, 15:54:15 schrieb James Liao:
On Mon, 2015-06-22 at 14:53 +0200, Heiko Stübner wrote:
Hi James,
Am Montag, 22. Juni 2015, 11:38:37 schrieb James Liao:
On Fri, 2015-06-19 at 13:36 +0200, Heiko Stuebner wrote:
Some clocks such as clkph_mck_o,
On Tue, 23 Jun 2015 17:28:53 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Add new device tree node for the control module register space where
PCIe registers are present.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
arch/arm/boot/dts/dra7.dtsi |5 +
1 file
On Tue, 23 Jun 2015 17:28:54 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Add syscon-phy-power property and remove the deprecated ctrl-module
property from SATA PHY node. Since omap_control_sata note is no longer
used, remove it.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
On Wed, 24 Jun 2015 05:09:39 -0700
Tony Lindgren t...@atomide.com wrote:
* Roger Quadros rog...@ti.com [150624 04:58]:
On Wed, 24 Jun 2015 14:50:17 +0300
Roger Quadros rog...@ti.com wrote:
On Tue, 23 Jun 2015 17:28:53 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Add new
* Roger Quadros rog...@ti.com [150624 05:21]:
On Wed, 24 Jun 2015 05:09:39 -0700
Tony Lindgren t...@atomide.com wrote:
My take is we should only use regmap for the scm_conf area
in general.
+1
should we get rid of dra7_ctrl_core and dra7_ctrl_general?
or move them to scm node?
Hi Matthias,
On Wed, Jun 24, 2015 at 4:04 AM, Matthias Brugger
matthias@gmail.com wrote:
On Monday, June 01, 2015 09:08:27 PM Eddie Huang wrote:
Add MT8173 I2C device nodes, include I2C controllers and pins.
MT8173 has six I2C controllers, from i2c0 to i2c6, exclude i2c5.
The 6th I2C
On Sat, 13 Jun 2015, Hans de Goede wrote:
From: Bruno Prémont bonb...@linux-vserver.org
Add an extra set of registers which is necessary tu support the PMICs
battery charger function, and mark registers which contain status bits,
gpio status, and adc readings as volatile.
Cc: Bruno
On Tue, 23 Jun 2015 17:28:52 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Deprecate using phy-omap-control driver to write to the mailbox register
and start using *syscon* framework to do the same.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
On Wed, 24 Jun 2015 15:06:02 +0300
Roger Quadros rog...@ti.com wrote:
On Tue, 23 Jun 2015 17:28:54 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Add syscon-phy-power property and remove the deprecated ctrl-module
property from SATA PHY node. Since omap_control_sata note is no longer
Hello,
On 13 June 2015 at 15:50, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
On Wed, Jun 10, 2015 at 09:57:13AM +0200, Hans de Goede wrote:
@@ -368,6 +392,12 @@ static struct mfd_cell axp20x_cells[] = {
.resources = axp20x_pek_resources,
}, {
On 06/22/2015 04:09 PM, Srinivas Kandagatla wrote:
diff --git a/drivers/nvmem/qfprom.c b/drivers/nvmem/qfprom.c
new file mode 100644
index 000..7f7a82f
--- /dev/null
+++ b/drivers/nvmem/qfprom.c
@@ -0,0 +1,89 @@
+
+#include linux/platform_device.h
+#include linux/nvmem-provider.h
On Tue, 2015-06-23 at 11:00 -0700, Moritz Fischer wrote:
+MODULE_ALIAS(platform:xilinx-mailbox);
So I think this MODULE_ALIAS() is only useful if, in short, there's a
corresponding platform_device created. Ie, a platform_device with a
name xilinx-mailbox that will fire of a
On 23 June 2015 at 16:51, Florian Fainelli f.faine...@gmail.com wrote:
Enable the use of UART0 by overriding its default status property.
Signed-off-by: Florian Fainelli f.faine...@gmail.com
Thanks Florian! I've tested this patch atop next-20150624 on the
smartrg-sr400ac, and confirmed UART0
On 24 June 2015 at 01:51, Florian Fainelli f.faine...@gmail.com wrote:
Enable the use of UART0 by overriding its default status property.
Give me 2-3 days to look at this, please.
--
To unsubscribe from this list: send the line unsubscribe devicetree in
the body of a message to
On Wed, Jun 24, 2015 at 11:19:39AM +0200, Carlo Caione wrote:
On Wed, Jun 24, 2015 at 3:42 AM, Chen-Yu Tsai w...@csie.org wrote:
On Tue, Jun 23, 2015 at 5:30 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sun, Jun 14, 2015 at 12:42:21PM +0200, Hans de Goede wrote:
Currently we
Hi,
On Wednesday 24 June 2015 05:09 PM, Roger Quadros wrote:
On Tue, 23 Jun 2015 17:28:52 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Deprecate using phy-omap-control driver to write to the mailbox register
and start using *syscon* framework to do the same.
Signed-off-by: Kishon
On Mon, 22 Jun 2015, Cyrille Pitchen wrote:
This driver supports the new Atmel Flexcom. The Flexcom is a wrapper which
integrates one SPI controller, one I2C controller and one USART. Only one
function can be enabled at a time. This driver selects the function once
for all, when the Flexcom
Hi,
On Wednesday 24 June 2015 05:37 PM, Roger Quadros wrote:
On Tue, 23 Jun 2015 17:28:56 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
The USB2 PHY2 has a different register map compared to USB2 PHY1
to power on/off the PHY. In order to handle it, use the new compatible
string
This driver reads very platform specific information in from Device Tree
and translates it into frequency tables. The generic drivers then use the
tables to conduct frequency and voltage scaling in the normal way.
There are 'ARM' patches in the set which are not necessarily related to CPUFreq,
This requires a DT Ack.
[... which would be pretty difficult, as you didn't Cc them]
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Documentation/devicetree/bindings/mfd/arizona.txt | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff
Hi,
On Wednesday 24 June 2015 04:04 PM, Roger Quadros wrote:
On Tue, 23 Jun 2015 17:28:48 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Deprecate using phy-omap-control driver to set PCS value of the PHY
and start using *syscon* framework to do the same.
Signed-off-by: Kishon Vijay
Hi,
On Wednesday 24 June 2015 05:20 PM, Roger Quadros wrote:
On Tue, 23 Jun 2015 17:28:53 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Add new device tree node for the control module register space where
PCIe registers are present.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Hi,
On Wednesday 24 June 2015 04:33 PM, Roger Quadros wrote:
On Tue, 23 Jun 2015 17:28:50 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
The USB2 PHY2 has a different register map compared to USB2 PHY1
to power on/off the PHY. In order to handle it, add a new
compatible string.
DT will not allow pseudo-devices. Only devices which represent real
hardware are permitted. So we have to register the CPUFreq driver
from platform code instead.
Rather than create a new file, we're bundling this in with the SMP
functionality and renaming it from 'smp' to the more generic
This also incorporates the STiH410.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/boot/dts/stih407-family.dtsi | 29 +
arch/arm/boot/dts/stih407.dtsi| 28
2 files changed, 29 insertions(+), 28 deletions(-)
diff --git
You'll notice that the voltage cell is populated with 0's. Voltage
information is very platform specific, even depends on 'cut' and
'substrate' versions. Thus it is left blank for a generic (safe)
implementation. If other nodes/properties are provided by the
bootloader, the ST CPUFreq driver
Hi,
On Wednesday 24 June 2015 05:26 PM, Roger Quadros wrote:
On Wed, 24 Jun 2015 14:50:17 +0300
Roger Quadros rog...@ti.com wrote:
On Tue, 23 Jun 2015 17:28:53 +0530
Kishon Vijay Abraham I kis...@ti.com wrote:
Add new device tree node for the control module register space where
PCIe
1 - 100 of 155 matches
Mail list logo
