On Sun, 05 Jul 2015, Jingoo Han wrote:
> On Tuesday, June 30, 2015 3:16 PM, Milo Kim wrote:
> >
> > LP855x backlight device can be enabled by external VDD input.
> > The 'supply' data is used for this purpose.
> > It's kind of private data which runs internally, so there is no reason to
> > expos
* Vaibhav Hiremath [150702 09:58]:
> --- a/drivers/pinctrl/pinctrl-single.c
> +++ b/drivers/pinctrl/pinctrl-single.c
>
> -static unsigned __maybe_unused pcs_readb(void __iomem *reg)
> +static unsigned pcs_read(struct regmap *map, unsigned int reg)
> {
> - return readb(reg);
> -}
> + uns
On Wednesday 03 June 2015 05:21 PM, Vignesh R wrote:
>
> Hi,
>
> This patch series adds support for PWMSS on DRA7. The IP is same as that
> present in AM33XX and AM43XX.
> The first patch changes clock domain in which PWMSS is present
> (l4per2_7xx_clkdm) to SW_WKUP. This is because legacy IPs
The basic support for UniPhier SoC family (arch/arm/mach-uniphier)
was mainlined at Linux 4.1-rc1.
I am now tackling some drivers to support them in the mainline.
I've got UART and EHCI done, so I'd like to enable them from
the ARM-SOC subsystem.
Masahiro Yamada (3):
ARM: multi_v7_defconfig:
The UniPhier on-chip UART driver was merged into the mainline by
commit 1a8d2903cb6a (serial: 8250_uniphier: add UniPhier serial
driver).
Add device nodes to make it really available.
We no longer have to depend on the on-board UART device (16550A),
so let's change the chosen and aliases to point
Get USB 2.0 host controllers available with generic-ehci bindings.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ph1-ld4-ref.dts | 8
arch/arm/boot/dts/uniphier-ph1-ld4.dtsi | 21 +
arch/arm/boot/dts/uniphier-ph1-pro4-ref.dts | 8
arc
From: Sanchayan Maity Sent: Wednesday, June 24, 2015
4:34 PM
> To: ji...@kernel.org
> Cc: shawn@linaro.org; ker...@pengutronix.de; robh...@kernel.org;
> pawel.m...@arm.com; mark.rutl...@arm.com; ijc+devicet...@hellion.org.uk;
> ga...@codeaurora.org; Duan Fugang-B38611; devicetree@vger.kernel.
Was there any more input or changes needed for this patchset?
Thanks,
Matt
On Tue, Jun 23, 2015 at 11:50 PM, Matt Ranostay wrote:
> changes from v5:
> * Dropped linux,led-brightness DT property
> * Removed several ifdefs to LED CLASS
> * Added cap11xx_init_leds stub
>
> Matt Ranostay (2):
> d
On UML builds, of_address.c fails to compile:
../drivers/of/address.c:873:2: error: implicit declaration of function
‘ioremap’ [-Werror=implicit-function-declaration]
This is due to CONFIG_OF now being user selectable. Add a dependency on
HAS_IOMEM to OF_ADDRESS in order to fix this.
Signed-off
Hi,
On Mon, Jun 29, 2015 at 3:04 PM, Leilk Liu wrote:
> Signed-off-by: Leilk Liu
> ---
> .../devicetree/bindings/spi/spi-mt65xx.txt | 32
> ++
> 1 file changed, 32 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/spi/spi-mt65xx.txt
>
> diff --gi
On Tue, Jun 30, 2015 at 3:43 PM, Arnd Bergmann wrote:
> On Tuesday 30 June 2015 14:27:25 Paul Osmialowski wrote:
>
>> / {
>> + aliases {
>> + pit0 = &pit0;
>> + pit1 = &pit1;
>> + pit2 = &pit2;
>> + pit3 = &pit3;
>> + };
>> +
>> soc {
On 02/07/15 23:27, Andreas Dannenberg wrote:
> Signed-off-by: Andreas Dannenberg
Utterly standard binding so unless someone shouts, I'll pick this
up with the driver.
Thanks,
Jonathan
> ---
> .../devicetree/bindings/iio/light/opt3001.txt | 18
> ++
> 1 file changed, 18
On 02/07/15 23:27, Andreas Dannenberg wrote:
> TI's opt3001 light sensor is a simple and yet powerful
> little device. The device provides 99% IR rejection,
> automatic full-scale, very low power consumption and
> measurements from 0.01 to 83k lux.
>
> This patch adds support for that device using
On 24/06/15 09:33, Sanchayan Maity wrote:
> 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 depend
> On 05.07.2015, at 20:37, Noralf Trønnes wrote:
>
> I have looked closer at the 8250 serial driver, and in fact it has a
> framework for writing 8250 like drivers. This makes it easy to extend
> it to include support for the mini uart.
> drivers/tty/serial/8250/8250_dw.c is an example of a driv
On Tuesday, June 30, 2015 3:16 PM, Milo Kim wrote:
>
> LP855x backlight device can be enabled by external VDD input.
> The 'supply' data is used for this purpose.
> It's kind of private data which runs internally, so there is no reason to
> expose to the platform data.
>
> And LP855x DT property,
On 05/07/15 12:50, Martin Kepplinger wrote:
> Am 2015-07-05 um 13:48 schrieb Jonathan Cameron:
>> On 04/07/15 14:55, Martin Kepplinger wrote:
>>> Signed-off-by: Martin Kepplinger
>>> Signed-off-by: Christoph Muellner
>> This is trivial enough I'll take it without a device tree ack (after a few
>
Am 2015-07-05 um 13:48 schrieb Jonathan Cameron:
> On 04/07/15 14:55, Martin Kepplinger wrote:
>> Signed-off-by: Martin Kepplinger
>> Signed-off-by: Christoph Muellner
> This is trivial enough I'll take it without a device tree ack (after a few
> days)
> but convention is to CC all device tree p
On 04/07/15 14:55, Martin Kepplinger wrote:
> For the devices supported by the mma8452 driver, two interrupt pins are
> available to route the interrupt signals to. By default INT1 is assumed.
>
> This adds a simple boolean DT property, for users to configure it for
> INT2, if that is the wired in
On 04/07/15 14:55, Martin Kepplinger wrote:
> IIO_EV_TYPE_THRESH in rising direction describes an event where the
> threshold is crossed in rising direction, positive or negative values
> being possible. This is not the case here.
>
> Since the threshold is no signed value and only the magnitude i
On 04/07/15 14:55, Martin Kepplinger wrote:
> Signed-off-by: Martin Kepplinger
> Signed-off-by: Christoph Muellner
This is trivial enough I'll take it without a device tree ack (after a few days)
but convention is to CC all device tree patches to the maintainers of devicetree
bindings as well as
On 04/07/15 14:55, Martin Kepplinger wrote:
> MMA8652FC and MMA8653FC don't provide the transient interrupt source, so
> the motion interrupt source is used by providing a new iio_chan_spec
> definition, so that other supported devices are not affected by this.
>
> Datasheets for the newly support
On 04/07/15 14:55, Martin Kepplinger wrote:
> This adds the freefall / motion interrupt source definitions to the driver.
> It is not in use now, but mma_chip_info and iio_chan_spec can easily be
> adapted to use it instead of the transient interrupt source.
So some support is added, but nothing do
On 05/07/15 12:44, Jonathan Cameron wrote:
> On 04/07/15 14:55, Martin Kepplinger wrote:
>> This adds the freefall / motion interrupt source definitions to the driver.
>> It is not in use now, but mma_chip_info and iio_chan_spec can easily be
>> adapted to use it instead of the transient interrupt
On 04/07/15 14:55, Martin Kepplinger wrote:
> This adds support for the 10 bit version if Freescale's accelerometers
> of this series. The datasheet is available at Freescale's website:
>
> http://cache.freescale.com/files/sensors/doc/data_sheet/MMA8453Q.pdf
>
> Signed-off-by: Martin Kepplinger
On 04/07/15 14:55, Martin Kepplinger wrote:
> This adds a struct mma_chip_info to hold data that will remain specific to
> the chip in use. It is provided during probe() and linked in
> struct of_device_id.
>
> Also this suggests that the driver is called "mma8452" and now handles the
> MMA8452Q d
On Friday 03 July 2015 00:08:27 Thomas Gleixner wrote:
> On Thu, 2 Jul 2015, Paul Osmialowski wrote:
> > On Thu, 2 Jul 2015, Arnd Bergmann wrote:
> >
> > > I wonder if you could move out the fixed rate clocks into their own
> > > nodes. Are they actually controlled by the same block? If they are
>
Den 05.07.2015 03:14, skrev Martin Sperl:
On 02.07.2015, at 06:57, Noralf Trønnes wrote:
Den 01.07.2015 21:39, skrev Martin Sperl:
On 30.06.2015, at 19:42, Mark Brown wrote:
This looks relevant:
On 22.06.2015, at 16:55, Jakub Kiciński wrote:
As mentioned by Noralf UART1 is quite commonly
Hi Vinod,
You're right, this should be separate patchset. Having patchset too big
leads to huge list of maintainers and lack of focusing on details
(on-error return values are total mess now!).
I plan to split it into three: 1) initial support (so the proof that
platform is living could be read
On Friday 03 July 2015 16:17:16 Ludovic Desroches wrote:
> Introduce driver for he Atmel SDMMC available on sama5d2. It is a sdhci
> compliant controller.
>
> Signed-off-by: Ludovic Desroches
> ---
> .../devicetree/bindings/mmc/sdhci-atmel.txt| 21 +++
> drivers/mmc/host/Kconfig
> On 02.07.2015, at 06:57, Noralf Trønnes wrote:
>
>
> Den 01.07.2015 21:39, skrev Martin Sperl:
>>> On 30.06.2015, at 19:42, Mark Brown wrote:
>>>
>>> This looks relevant:
>>>
>> On 22.06.2015, at 16:55, Jakub Kiciński wrote:
>> As mentioned by Noralf UART1 is quite commonly used o
On Tue, Jun 30, 2015 at 02:27:27PM +0200, Paul Osmialowski wrote:
The patch title is not per subsystem semantics, pls fix that
> Surprisingly small amount of work was required in order to extend already
> existing eDMA driver with the support for Kinetis SoC architecture.
And this doesn't tell me
i8042_of.h should be included when CONFIG_ARCH_MIGHT_HAVE_PC_SERIO and
CONFIG_USE_OF are selected. Kconfig is not modified.
Signed-off-by: Roman Volkov
---
drivers/input/serio/i8042.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/input/serio/i8042.h b/drivers/input/serio/i8042.h
Original driver should be modified to support OF/FDT bindings. The
platform_create_bundle() function should be removed when compiled for
OF-capable machines, since the device tree is already created by the
platform code. The driver should also contain the OF match table and
call platform-specific p
Add a documentation file for the new OF/FDT binding for the i8042 interface.
Signed-off-by: Roman Volkov
---
.../devicetree/bindings/serio/intel,8042.txt | 82 ++
1 file changed, 82 insertions(+)
create mode 100644 Documentation/devicetree/bindings/serio/intel,8042.txt
This file contains OF/FDT parsing code, based on older implementations
for SPARC and PowerPC. Currently it can be used to support the i8042
interface on the vt8500 boards. This code can be reused with some
workarounds to support the older SPARC machines. For example, older
machines do not have the
The i8042 interface is used not only on the x86 architecture. Some of
non-x86 architectures are using Open Firmware device tree, like SPARC
and PowerPC. There is also non-x86 platforms with the FDT support, such
as ARM SoCs. There is no code in Linux to support i8042-capable input
devices on these
Add the devicetree binding for the cru on the rk3368 which quite similar
structured as previous clock controllers.
Signed-off-by: Heiko Stuebner
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Cc: devicetree@vger.kernel.org
---
.../bindings/clock/rockchip,rk3
A nit only: a license mismatch.
On vr, 2015-07-03 at 16:17 +0200, Ludovic Desroches wrote:
> --- /dev/null
> +++ b/drivers/mmc/host/sdhci-of-at91.c
>
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published
This adds the freefall / motion interrupt source definitions to the driver.
It is not in use now, but mma_chip_info and iio_chan_spec can easily be
adapted to use it instead of the transient interrupt source.
Signed-off-by: Martin Kepplinger
Signed-off-by: Christoph Muellner
---
drivers/iio/acc
This is version 3 of the mma8452 driver improvements. Version 3 adds one
patch to allow all possible pin wirings for users and adds more relevant
people to the discussion, I forgot about before. I'm sorry.
These changes add support for motion interrupts and 3 more accelerometer
chips, two of which
Signed-off-by: Martin Kepplinger
Signed-off-by: Christoph Muellner
---
drivers/iio/accel/mma8452.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/iio/accel/mma8452.c b/drivers/iio/accel/mma8452.c
index ccce925..7f6e3b4 100644
--- a/drivers/iio/accel/mma8452.c
+++ b/drivers/iio/accel
Signed-off-by: Martin Kepplinger
Signed-off-by: Christoph Muellner
---
.../devicetree/bindings/iio/accel/mma8452.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/accel/mma8452.txt
diff --git a/Documentation/devicetr
MMA8652FC and MMA8653FC don't provide the transient interrupt source, so
the motion interrupt source is used by providing a new iio_chan_spec
definition, so that other supported devices are not affected by this.
Datasheets for the newly supported devices are available at Freescale's
website:
http
This adds support for the 10 bit version if Freescale's accelerometers
of this series. The datasheet is available at Freescale's website:
http://cache.freescale.com/files/sensors/doc/data_sheet/MMA8453Q.pdf
Signed-off-by: Martin Kepplinger
Signed-off-by: Christoph Muellner
---
drivers/iio/acce
This doesn't actually change anything since the core names the sysfs folder
for the iio event attributes "events" anyways. It only leaves the job to the
core.
Signed-off-by: Martin Kepplinger
Signed-off-by: Christoph Muellner
---
drivers/iio/accel/mma8452.c | 1 -
1 file changed, 1 deletion(-)
This adds a struct mma_chip_info to hold data that will remain specific to
the chip in use. It is provided during probe() and linked in
struct of_device_id.
Also this suggests that the driver is called "mma8452" and now handles the
MMA8452Q device, but is not limited to it.
Signed-off-by: Martin
For the devices supported by the mma8452 driver, two interrupt pins are
available to route the interrupt signals to. By default INT1 is assumed.
This adds a simple boolean DT property, for users to configure it for
INT2, if that is the wired interrupt pin for them.
This is important for everyone
IIO_EV_TYPE_THRESH in rising direction describes an event where the
threshold is crossed in rising direction, positive or negative values
being possible. This is not the case here.
Since the threshold is no signed value and only the magnitude is compared,
IIO_EV_TYPE_MAG is what describes the beha
Robert Jarzmik writes:
Applied to pxa/dt, thanks.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
50 matches
Mail list logo
