On 2015/9/11 11:53, Ganapatrao Kulkarni wrote:
> Hi Thunder,
>
>
> On Tue, Sep 8, 2015 at 9:57 PM, Ganapatrao Kulkarni
> wrote:
>> Hi Hanjun,
>>
>> On Tue, Sep 8, 2015 at 6:57 PM, Hanjun Guo wrote:
>>> Hi Ganapatrao,
>>>
>>>
>>> On 08/29/2015 10:56 PM, Ganapatrao Kulkarni wrote:
Hi
Hey chen,
On September 11, 2015 4:57:03 AM CEST, Chen-Yu Tsai wrote:
>On Fri, Sep 11, 2015 at 2:13 AM, Maxime Ripard
> wrote:
>> Hi Oliver,
>>
>> On Wed, Sep 09, 2015 at 03:26:44PM +0200, Olliver Schinagl wrote:
>>> The Olimex OLinuXino Lime2 uses the same AXP209 as was recently
>>> introduced th
Add Freescale Queue Direct Memory Access(qDMA) controller support.
This module can be found on LS-1 and LS-2 SoCs.
This add the legacy mode support for qDMA.
Signed-off-by: Yuan Yao
---
Documentation/devicetree/bindings/dma/fsl-qdma.txt | 43 ++
MAINTAINERS
Add Freescale Queue Direct Memory Access(qDMA) controller support.
This module can be found on LS-1 and LS-2 SoCs.
This add the legacy mode support for qDMA.
Signed-off-by: Yuan Yao
---
arch/arm/boot/dts/ls1021a.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/
On Tue, Sep 8, 2015 at 12:03 PM, Leif Lindholm wrote:
> On Tue, Sep 08, 2015 at 02:09:51PM +0100, Mark Rutland wrote:
>> On Tue, Sep 08, 2015 at 01:43:35PM +0100, Leif Lindholm wrote:
>> > The ACPI DBG2 table defines a debug console. Add support for parsing it
>> > and using it to select earlycon
Hi Tejun,
Could you please take the version 1 patch?
The version 2 patch can't address these warnings, and the version 1 can
definitely remove them.
In this case, that would cause any hidden bugs, so no worries.
Regards,
Yuantian
> -Original Message-
> From: Tejun Heo [mailto:hte...@gma
On 09/10/2015 02:08 AM, David Gibson wrote:
> On Fri, Aug 28, 2015 at 09:53:06AM -0500, Rob Herring wrote:
>> On Fri, Aug 28, 2015 at 12:23 AM, Matt Porter wrote:
>>> Add a skeleton DT binding document that serves as the canonical
>>> example for implementing YAML-based DT bindings documentation.
Hi Thunder,
On Tue, Sep 8, 2015 at 9:57 PM, Ganapatrao Kulkarni
wrote:
> Hi Hanjun,
>
> On Tue, Sep 8, 2015 at 6:57 PM, Hanjun Guo wrote:
>> Hi Ganapatrao,
>>
>>
>> On 08/29/2015 10:56 PM, Ganapatrao Kulkarni wrote:
>>>
>>> Hi Thunder,
>>>
>>> On Sat, Aug 29, 2015 at 3:16 PM, Leizhen (ThunderTo
On Tue, 2015-09-08 at 19:30 -0500, Rob Herring wrote:
> On 09/08/2015 01:18 AM, Chunfeng Yun wrote:
> > add a DT binding documentation of xHCI host controller for the
> > MT8173 SoC from Mediatek.
> >
> > Signed-off-by: Chunfeng Yun
> > ---
> > .../devicetree/bindings/usb/mt8173-xhci.txt
Hi,
On Tue, 2015-09-08 at 19:16 -0500, Rob Herring wrote:
> On 09/08/2015 01:17 AM, Chunfeng Yun wrote:
> > add a DT binding documentation of usb3.0 phy for MT65xx
> > SoCs from Mediatek.
> >
> > Signed-off-by: Chunfeng Yun
>
> One comment, otherwise:
>
> Acked-by: Rob Herring
>
> > ---
> >
ping
On 08/31/2015 06:25 PM, Franklin S Cooper Jr wrote:
> The current/old gpio framework used doesn't properly listen to
> ACTIVE_LOW and ACTIVE_HIGH flags. The newer gpio framework takes into
> account these flags when setting gpio values.
>
> Since the values being outputed were base on voltage
On Fri, Sep 11, 2015 at 2:13 AM, Maxime Ripard
wrote:
> Hi Oliver,
>
> On Wed, Sep 09, 2015 at 03:26:44PM +0200, Olliver Schinagl wrote:
>> The Olimex OLinuXino Lime2 uses the same AXP209 as was recently
>> introduced this driver for its power regulation.
>>
>> Signed-off-by: Olliver Schinagl
>>
On 09/10/2015 03:29 PM, Jon Masters wrote:
On 08/24/2015 01:01 PM, fu@linaro.org wrote:
+ /*
+* Get the frequency of system counter from the cp15 interface of ARM
+* Generic timer. We don't need to check it, because if it returns "0",
+* system would panic in v
On Thu, Sep 10, 2015 at 06:29:53PM -0400, Jon Masters wrote:
> On 08/24/2015 01:01 PM, fu@linaro.org wrote:
>
> > + /*
> > +* Get the frequency of system counter from the cp15 interface of ARM
> > +* Generic timer. We don't need to check it, because if it returns "0",
> > +* syst
On 11.09.2015 01:42, Andrew F. Davis wrote:
> On 09/09/2015 06:47 PM, Krzysztof Kozlowski wrote:
> +- ti,enable-user-write: boolean, if present driver will allow the
> user space
> +to control the charging current and voltage through sysfs;
This is not DT property. It does
On 11.09.2015 05:57, Andreas Dannenberg wrote:
> On Thu, Sep 10, 2015 at 09:15:09AM +0900, Krzysztof Kozlowski wrote:
(...)
>
bq2415x.txt - ti,current-limit - maximum current to be drawn in mA
New bindings:
ti,charge-current (bq24261) - default charge current in mA
ti,m
+Ian
On 09/10/2015 01:50 PM, Hans de Goede wrote:
> Hi,
>
> On 10-09-15 20:42, Dmitry Torokhov wrote:
>> On Thu, Sep 10, 2015 at 11:40 AM, Hans de Goede
>> wrote:
>>> Hi,
>>>
>>>
>>> On 10-09-15 20:34, Dmitry Torokhov wrote:
On Thu, Sep 10, 2015 at 10:25 AM, Rob Herring wrote:
>
>
On 06/03/2015 02:53 PM, Timur Tabi wrote:
> On 06/03/2015 01:25 PM, Guenter Roeck wrote:
>> In general the idea here would be to use a crashdump kernel, which,
>> when loaded, would reset the watchdog before it fires. This kernel
>> would then write a core dump to a specified location.
>
> What is
On 08/24/2015 01:01 PM, fu@linaro.org wrote:
> + /*
> + * Get the frequency of system counter from the cp15 interface of ARM
> + * Generic timer. We don't need to check it, because if it returns "0",
> + * system would panic in very early stage.
> + */
> + gwdt->clk
There are a pair of SPI masters and a mini UART that were last minute
additions. As a result, they didn't get integrated in the same way as
the other gates off of the VPU clock in CPRMAN.
Signed-off-by: Eric Anholt
---
drivers/clk/bcm/Makefile | 1 +
drivers/clk/bcm/clk-bcm2835-aux.c
These will be used for enabling UART1, SPI1, and SPI2.
Signed-off-by: Eric Anholt
---
arch/arm/boot/dts/bcm2835.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/bcm2835.dtsi b/arch/arm/boot/dts/bcm2835.dtsi
index a6a55b7..7c37956 100644
--- a/arch/arm/boot/dts/bc
This is a followup to the main audio domain clocks series I just
posted. There's a clock gate register controlling the clocks for a
few extra peripherals, and Martin Sperl has been working on the SPI
driver for 2/3 of them (the other is a simple UART). This gives those
drivers the clock gate enab
These will be used for enabling UART1, SPI1, and SPI2.
Signed-off-by: Eric Anholt
---
.../bindings/clock/brcm,bcm2835-aux-clock.txt | 30 ++
include/dt-bindings/clock/bcm2835-aux.h| 17
2 files changed, 47 insertions(+)
create mode 100644
Docum
This adds support for enabling, disabling, and setting the rate of the
audio domain clocks. It will be necessary for setting the pixel clock
for HDMI in the VC4 driver and let us write a cpufreq driver. It will
also improve compatibility with user changes to the firmware's
config.txt, since our p
Previously we've only supported a few fixed clocks based on
assumptions about how the firmware sets up the clocks, but this
binding will let us control the actual (audio power domain) clock
manager.
Signed-off-by: Eric Anholt
---
.../bindings/clock/brcm,bcm2835-cprman.txt | 45 ++
This will give us the ability to set the pixel and HDMI state machine
clocks for the VC4 KMS driver, change the CPU frequency, and
potentially gate clocks in the future (once we also write a power
domain driver). It also gives the uart an explicit clock reference,
so that we don't need to change t
clk-bcm2835.c predates the drivers under bcm/, but all the new BCM
drivers are going in there so let's follow them.
Signed-off-by: Eric Anholt
---
drivers/clk/Makefile| 1 -
drivers/clk/bcm/Makefile| 1 +
drivers/clk/{ => bcm}/clk-bcm2835.c | 0
3 files changed, 1 ins
Eric Anholt writes:
> This adds support for enabling, disabling, and setting the rate of the
> audio domain clocks. It will be necessary for setting the pixel clock
> for HDMI in the VC4 driver and let us write a cpufreq driver. It will
> also improve compatibility with user changes to the firm
On Thu, Sep 10, 2015 at 03:26:16PM +0300, Laurentiu Palcu wrote:
> On Tue, Sep 08, 2015 at 07:12:24PM -0500, Andreas Dannenberg wrote:
> > This patch series extends the driver to also support bq24250/bq24251.
> >
> > The bq24250/251/257 devices have a very similar feature set and are
> > virtually
On Thu, Sep 10, 2015 at 06:00:32PM +0300, Laurentiu Palcu wrote:
> On Thu, Sep 10, 2015 at 09:15:09AM +0900, Krzysztof Kozlowski wrote:
> > On 10.09.2015 05:15, Andreas Dannenberg wrote:
[...]
> > >> ti,current-limit (bq2425x) - maximum current to be drawn in *uA*
> > >
> > > Ok. Again here my p
On Thu, Sep 10, 2015 at 09:15:09AM +0900, Krzysztof Kozlowski wrote:
> On 10.09.2015 05:15, Andreas Dannenberg wrote:
> > On Wed, Sep 09, 2015 at 01:58:09PM +0900, Krzysztof Kozlowski wrote:
> >>
> >> So we have different bindings. Existing ones:
> >> bq2415x.txt - ti,charge-current - maximum charg
On Thu, Sep 10, 2015 at 05:40:53PM +0300, Laurentiu Palcu wrote:
> On Tue, Sep 08, 2015 at 07:12:35PM -0500, Andreas Dannenberg wrote:
> > The patch adds a way to setup and initialize the device through the use
> > of platform data with configuration options equivalent to when using
> > device firm
- Add ZERO_OFFSET_VALID flag, on imx7d mux_conf reg
offset is zero for iomuxc-lspr controller
- Do default initialization on parse group function.
Signed-off-by: Adrian Alonso
---
Changes for V2: Resend
Changes for V3: Resend
drivers/pinctrl/freescale/pinctrl-imx.c | 23 +-
From: Robin Gong
Fix system chrash caused by groups whose number is smaller than the number
of groups of the last pinctl instance which is not initialized.
iMX7D supports two iomux controllers (iomuxc-lpsr and iomuxc) on probing
the second instance (iomuxc) the chrash below occurs.
Uncompressin
Add device tree node to support iomuxc-lpsr controller, iput-sel phandle
allows to get input select register base address which is shared from
iomuxc controller.
Signed-off-by: Adrian Alonso
---
Changes for V2: Resend
Changes for V3: Add phandle to get input select register base address
arch/ar
Add iomuxc-lpsr devicetree bindings documentation
Provide documentation context as well an example on
pheriperals that could use pad from either iomuxc controller
supported by iMX7D SoC
Signed-off-by: Adrian Alonso
---
Changes for V2: New patch on imx7d iomuxc-lpsr patch series
Changes for V3: Ad
iMX7D has two iomuxc controllers, iomuxc controller similar as
previous iMX SoC generation and iomuxc-lpsr which provides low
power state rentetion capabilities on gpios that are part of
iomuxc-lpsr
- Add iomuxc-lpsr gpio group id's
- Use flag ZERO_OFFSET_VALID and SHARE_INPUT_SELECT_REG to
prop
- Add shared input select register support
- imx7d has two iomux controllers iomuxc and iomuxc-lpsr
which share select_input register for daisy chain settings
Signed-off-by: Adrian Alonso
---
Changes for V2: Resend
Changes for V3:
- Use of_parse_phandle instead of of_get_child_by_name to get in
Add imx7d-sdb iomuxc-lpsr hoggrp-2 default pads settings
Signed-off-by: Adrian Alonso
---
Changes for V2: Resend
Changes for V3: Resend
arch/arm/boot/dts/imx7d-sdb.dts | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/imx7d-sdb.dts b/arch/arm/boot/dts/imx7d-
- Add imx7 SoC GPIO1 pad iomuxc settings
- Fix UART input select daisy chain setting values
Signed-off-by: Adrian Alonso
---
Chages for V2: Fix tab+space identation
Chages for V3: Resend
arch/arm/boot/dts/imx7d-pinfunc.h | 122 +-
1 file changed, 119 inser
On 10/09/15 08:29, Jonas Gorski wrote:
> Add required binding support to probe through device tree.
>
> Use the compatible instead of the resource size for identifiying the
> block type, and allow reducing the number of cs lines through OF.
This looks good to me, since this builds on top of your
On 10/09/15 08:29, Jonas Gorski wrote:
> Add documentation for the bindings of the low speed SPI controller found
> on most bcm63xx SoCs.
>
> Signed-off-by: Jonas Gorski
> ---
> .../devicetree/bindings/spi/spi-bcm63xx.txt| 33
> ++
> 1 file changed, 33 insertions(+)
On Thu, Sep 10, 2015 at 03:00:35PM +0200, Hans de Goede wrote:
> The TZX 723Q4 PCB is a pcb used in some q8 case 7" A33 tablets.
> This PCB has an interesting issue, its micro sdcards slot will not work
> unless the drive-strength on the mmc pins is lowered from 30mA to 10mA.
>
> Therefor this com
On Thu, Sep 10, 2015 at 05:13:32PM +0300, Laurentiu Palcu wrote:
> On Tue, Sep 08, 2015 at 07:12:34PM -0500, Andreas Dannenberg wrote:
> > This patch adds support to enable/disable some device specific features
> > through device properties at boot time or sysfs properties at runtime
> > depending
On Thu, Sep 10, 2015 at 04:56:22PM +0300, Laurentiu Palcu wrote:
> On Tue, Sep 08, 2015 at 07:12:32PM -0500, Andreas Dannenberg wrote:
> > The bq2425x devices support charging with a configurable charge current
> > i_chg or a specific fixed low-current in what's called Low Charge mode.
> > This pat
Hi,
On 10-09-15 20:42, Dmitry Torokhov wrote:
On Thu, Sep 10, 2015 at 11:40 AM, Hans de Goede wrote:
Hi,
On 10-09-15 20:34, Dmitry Torokhov wrote:
On Thu, Sep 10, 2015 at 10:25 AM, Rob Herring wrote:
On 09/09/2015 04:11 AM, Hans de Goede wrote:
This header provides evdev constants for
On Thu, Sep 10, 2015 at 11:40 AM, Hans de Goede wrote:
> Hi,
>
>
> On 10-09-15 20:34, Dmitry Torokhov wrote:
>>
>> On Thu, Sep 10, 2015 at 10:25 AM, Rob Herring wrote:
>>>
>>> On 09/09/2015 04:11 AM, Hans de Goede wrote:
This header provides evdev constants for linux,code, and linux,inp
Hi,
On 10-09-15 20:34, Dmitry Torokhov wrote:
On Thu, Sep 10, 2015 at 10:25 AM, Rob Herring wrote:
On 09/09/2015 04:11 AM, Hans de Goede wrote:
This header provides evdev constants for linux,code, and linux,input-*
properties.
Signed-off-by: Hans de Goede
---
include/dt-bindings/input/evd
On Thu, Sep 10, 2015 at 10:25 AM, Rob Herring wrote:
> On 09/09/2015 04:11 AM, Hans de Goede wrote:
>> This header provides evdev constants for linux,code, and linux,input-*
>> properties.
>>
>> Signed-off-by: Hans de Goede
>> ---
>> include/dt-bindings/input/evdev.h | 76
>> +++
On Thu, Sep 10, 2015 at 10:31:16AM +0200, Olliver Schinagl wrote:
> Some of the olimex series of boards feature a permanently connected eeprom on
> i2c-1. This patch series adds them on all the boards that I personally have
> and
> where tested with.
>
> Additionally, it brings the eeprom on the
Hi Oliver,
On Wed, Sep 09, 2015 at 03:26:44PM +0200, Olliver Schinagl wrote:
> The Olimex OLinuXino Lime2 uses the same AXP209 as was recently
> introduced this driver for its power regulation.
>
> Signed-off-by: Olliver Schinagl
> ---
> arch/arm/boot/dts/sun7i-a20-olinuxino-lime2.dts | 87
> +
On 09/09/2015 04:11 AM, Hans de Goede wrote:
> The devicetree binding for gpio-keys-polled already allows specifying
> what type of events (key / rel / abs) a button generates when pressed.
>
> But for rel / abs axis we also need to specify which value this specific
> gpio represents.
>
> One use
On 09/09/2015 04:11 AM, Hans de Goede wrote:
> This header provides evdev constants for linux,code, and linux,input-*
> properties.
>
> Signed-off-by: Hans de Goede
> ---
> include/dt-bindings/input/evdev.h | 76
> +++
This looks fine, but please just add to
[ Sending again in plain text ]
Noralf pointed me at fixed-factor-clock, and that works in our
(downstream) environment:
soc: soc {
...
uart1: uart@7e215040 {
compatible = "brcm,bcm2835-aux-uart", "ns16550";
reg = <0x7e215040 0x40>;
interrupt
On Thu, Sep 10, 2015 at 04:43:10PM +0300, Laurentiu Palcu wrote:
> On Tue, Sep 08, 2015 at 07:12:31PM -0500, Andreas Dannenberg wrote:
> > This commit extends the use of the existing mutex to pave the way for
> > using direct device access inside sysfs getter/setter routines in a
> > way that the a
On Wed, 2015-09-09 at 21:03 -0500, Wang Dongsheng-B40534 wrote:
> Hi Scott,
>
> Thanks for your review.
>
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Thursday, September 10, 2015 3:57 AM
> > To: Wang Dongsheng-B40534
> > Cc: devicetree@vger.kernel.org; linuxppc-...@lists.
On Wed, Sep 09, 2015 at 10:23:24AM +0200, Hans de Goede wrote:
> The iNet-tek iNet-1 PCB is a PCB found in various generic 10.1" 1024x600
> A10 based tablets such as the Point of View Protab2 XXL and the
> Cherry M1007.
>
> This patch has been tested on both rev2 and rev5 of this board / these
> t
On 09/09/2015 06:47 PM, Krzysztof Kozlowski wrote:
+- ti,enable-user-write: boolean, if present driver will allow the user space
+to control the charging current and voltage through sysfs;
This is not DT property. It does not describe hardware.
We needed a mechanism to enable the sysfs wri
On Wed, Sep 09, 2015 at 10:23:23AM +0200, Hans de Goede wrote:
> The inet9f-rev03 pcb is specially designed for gaming tablets, such as
> the qware tb-g100 tablet.
>
> These 7" tablets feature a dpad, firebuttons and 2 joysticks on the sides
> of the screen.
>
> Besides this they have the usual c
2015-09-10 18:35 GMT+02:00 Enric Balletbo i Serra :
> The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
> designed for portable devices.
>
> You can add support to your board with current binding.
>
> Example:
>
> anx7814: anx7814@38 {
> compatible = "
Analogix Semiconductor develops analog and mixed-signal devices for digital
media and communications interconnect applications.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
At the moment it only supports ANX7814.
The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
designed for portable devices.
This driver adds initial support and supports HDMI to DP pass-through mode.
Signed-off-by: Enric Balletbo i Serra
---
drivers/gpu/drm/bridge/Kconfig
The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
designed for portable devices.
You can add support to your board with current binding.
Example:
anx7814: anx7814@38 {
compatible = "analogix,anx7814";
reg = <0x38>;
pd
Hi all,
This is the third version with more changes requested by Dan.
The following series add initial support for the Slimport ANX7814 transmitter, a
ultra-low power Full-HD (1080p60) transmitter designed for portable device.
The driver was originally created and based from the work of Junhua X
> > C) When you could go:
> >
> >DT -> Discover Xen -> Xen-specific stuff -> Xen-specific EFI/ACPI
> > discovery
>
> I take you mean discovering Xen with the usual Xen hypervisor node on
> device tree. I think that C) is a good option actually. I like it. Not
> sure why we didn't think about
On Thu, Sep 10, 2015 at 03:42:11PM +0300, Laurentiu Palcu wrote:
> On Tue, Sep 08, 2015 at 07:12:26PM -0500, Andreas Dannenberg wrote:
> [...]
> >
> > #include
> > @@ -41,6 +45,18 @@
> >
> > #define BQ24257_ILIM_SET_DELAY 1000/* msec */
> >
> > +enum bq2425x_chip {
> > +
On Thu, 10 Sep 2015, Mark Rutland wrote:
> On Thu, Sep 10, 2015 at 02:52:25PM +0100, Stefano Stabellini wrote:
> > On Thu, 10 Sep 2015, Mark Rutland wrote:
> > > On Thu, Sep 10, 2015 at 12:37:57PM +0100, Stefano Stabellini wrote:
> > > > On Thu, 10 Sep 2015, Mark Rutland wrote:
> > > > > > > Does X
> On 10.09.2015, at 17:48, Noralf Trønnes wrote:
>
> This looks interesting.
> But there's a challenge with the uart1 and the 8250 driver.
>
> Phil Elwell has this to say:
> This means that that UART1 isn't an exact clone of a 8250 UART.
> In a particular, the clock divisor is calculated differ
Hi,
On Wed, Sep 09, 2015 at 10:23:22AM +0200, Hans de Goede wrote:
> Tell make to build a dtb, rather then the already existing dts.
>
> Signed-off-by: Hans de Goede
A patch to fix that have been sent already:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-September/367989.html
It
Den 09.09.2015 03:48, skrev Eric Anholt:
ker...@martin.sperl.org writes:
From: Martin Sperl
The BCM2835 contains 3 auxiliar devices:
* spi1
* spi2
* uart1
All of those 3 devices are enabled/disabled via a shared register,
which is set by default to be disabled.
Access to this register need
Hi Enric,
On Thursday 10 September 2015 16:11:03 Enric Balletbo Serra wrote:
> 2015-09-09 2:40 GMT+02:00 Rob Herring :
> > On 09/08/2015 02:25 AM, Enric Balletbo i Serra wrote:
> >> The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
> >> designed for portable devices.
> >>
>
Add support for probing spi-bcm63xx through device tree.
Depends on "spi/bcm63xx: cleanup and decouple from arch code".
Jonas Gorski (2):
spi/bcm63xx: document device tree bindings
spi/bcm63xx: add support for probing through devicetree
.../devicetree/bindings/spi/spi-bcm63xx.txt| 3
Add required binding support to probe through device tree.
Use the compatible instead of the resource size for identifiying the
block type, and allow reducing the number of cs lines through OF.
Signed-off-by: Jonas Gorski
---
drivers/spi/spi-bcm63xx.c | 56 +++---
On Tue, 2015-09-08 at 13:43 +0100, Leif Lindholm wrote:
> From: Torez Smith
>
> If console= is not added to the kernel command line, the console
> is not registered until much further into the booting process. This patch
> adds support to parse the SPCR ACPI table to pull console support out,
> t
Add documentation for the bindings of the low speed SPI controller found
on most bcm63xx SoCs.
Signed-off-by: Jonas Gorski
---
.../devicetree/bindings/spi/spi-bcm63xx.txt| 33 ++
1 file changed, 33 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sp
>>> On 10.09.15 at 16:53, wrote:
> On Thu, Sep 10, 2015 at 01:55:25PM +0100, Jan Beulich wrote:
>> >>> On 10.09.15 at 13:37, wrote:
>> > On Thu, 10 Sep 2015, Mark Rutland wrote:
>> >> Why can't Xen give a virtual EFI interface to Dom0 / guests? e.g.
>> >> create pages of RuntimeServicesCode that
Hi,
On 09-09-15 16:01, Maxime Ripard wrote:
On Tue, Sep 08, 2015 at 11:26:51PM +0200, Hans de Goede wrote:
Hi,
On 09/08/2015 04:33 PM, Maxime Ripard wrote:
On Sat, Sep 05, 2015 at 04:55:52PM +0200, Hans de Goede wrote:
This is the sun5i / a13 version of sun8i-q8-common.dtsi for use in dts
fi
On Thu, Sep 10, 2015 at 09:15:09AM +0900, Krzysztof Kozlowski wrote:
> On 10.09.2015 05:15, Andreas Dannenberg wrote:
> > On Wed, Sep 09, 2015 at 01:58:09PM +0900, Krzysztof Kozlowski wrote:
> >>
> >> So we have different bindings. Existing ones:
> >> bq2415x.txt - ti,charge-current - maximum charg
On Thu, Sep 10, 2015 at 01:55:25PM +0100, Jan Beulich wrote:
> >>> On 10.09.15 at 13:37, wrote:
> > On Thu, 10 Sep 2015, Mark Rutland wrote:
> >> Why can't Xen give a virtual EFI interface to Dom0 / guests? e.g.
> >> create pages of RuntimeServicesCode that are trivial assembly shims
> >> doing hy
On 9 September 2015 at 03:29, Rob Herring wrote:
> On 09/07/2015 07:23 AM, Tomeu Vizoso wrote:
>> Walks the OF tree up and finds the closest ancestor that has a struct
>> device associated with it, probing it if isn't bound to a driver yet.
>>
>> The above should ensure that the dependency represe
On Thu, Sep 10, 2015 at 08:49:26AM +0900, Krzysztof Kozlowski wrote:
> On 10.09.2015 02:31, Andreas Dannenberg wrote:
> > On Wed, Sep 09, 2015 at 01:17:11PM +0900, Krzysztof Kozlowski wrote:
> >> On 09.09.2015 11:26, Andreas Dannenberg wrote:
> >>> Krzysztof, good observation! In bq2425x_charger.c
On Thu, Sep 10, 2015 at 02:52:25PM +0100, Stefano Stabellini wrote:
> On Thu, 10 Sep 2015, Mark Rutland wrote:
> > On Thu, Sep 10, 2015 at 12:37:57PM +0100, Stefano Stabellini wrote:
> > > On Thu, 10 Sep 2015, Mark Rutland wrote:
> > > > > > Does Xen not talk to EFI itself and/or give the kernel a
On Tue, Sep 08, 2015 at 07:12:36PM -0500, Andreas Dannenberg wrote:
> Rename files and refactor definitions, function names, etc as well as
> the driver name itself to reflect that this driver supports multiple
> devices and not just the bq24257.
>
> Signed-off-by: Andreas Dannenberg
Reviewed-by:
On Tue, Sep 08, 2015 at 07:12:35PM -0500, Andreas Dannenberg wrote:
> The patch adds a way to setup and initialize the device through the use
> of platform data with configuration options equivalent to when using
> device firmware (DT or ACPI) for systems where this is not available.
>
> Signed-of
On Tue, 8 Sep 2015 12:46:08 -0400
"Kevin O'Connor" wrote:
> On Mon, Sep 07, 2015 at 01:08:29PM +0200, Gerd Hoffmann wrote:
> > > It's just simplicity. If you want to read a few times from the
> > > same field (like in ACPI tables, read the data size and then the
> > > data), you need a way to ena
Hi,
On Mon, 07 Sep 2015, Daniel Thompson wrote:
> On 07/09/15 13:33, Arnd Bergmann wrote:
> >On Monday 07 September 2015 11:30:11 Daniel Thompson wrote:
>
> I would suggest "firmware-names" to be consistent with other naming
> convention and because their can be more than one (either
On Tue, Sep 08, 2015 at 07:12:34PM -0500, Andreas Dannenberg wrote:
> This patch adds support to enable/disable some device specific features
> through device properties at boot time or sysfs properties at runtime
> depending on whether they should be accessible during runtime or not.
> The use of
On Thu, Sep 10, 2015 at 02:52:25PM +0100, Stefano Stabellini wrote:
> > > In any case this should be separate from the shim ABI discussion.
> >
> > I disagree; I think this is very much relevant to the ABI discussion.
> > That's not to say that I insist on a particular approach, but I think
> > th
Hi Rob,
2015-09-09 2:40 GMT+02:00 Rob Herring :
> On 09/08/2015 02:25 AM, Enric Balletbo i Serra wrote:
>> The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
>> designed for portable devices.
>>
>> You can add support to your board with current binding.
>>
>> Example:
>>
>>
On Tue, Sep 08, 2015 at 07:12:33PM -0500, Andreas Dannenberg wrote:
> This patch allows reading (and writing, if the D+/D- USB signal-based
> charger type detection is disabled) of the input current limit through
> the POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT sysfs property. This allows
> userspace to
> -Original Message-
> From: Bastien Nocera [mailto:had...@hadess.net]
> Sent: 09 September, 2015 20:03
> To: Tirdea, Irina; linux-in...@vger.kernel.org
> Cc: linux-ker...@vger.kernel.org; Rob Herring; Pawel Moll; Ian Campbell;
> Kumar Gala; Purdila, Octavian; Dmitry Torokhov; Mark
> Rut
On Tue, Sep 08, 2015 at 09:48:48AM +0200, Hans de Goede wrote:
> Hi,
>
> On 07-09-15 22:52, Maxime Ripard wrote:
> >Hi,
> >
> >On Mon, Sep 07, 2015 at 11:30:03AM +0200, Hans de Goede wrote:
> >bma250 already has devicetree support. It is used in Gemei G9
> >tablet (sun4i-gemei-g9.dts).
> >
On Tue, Sep 08, 2015 at 07:12:32PM -0500, Andreas Dannenberg wrote:
> The bq2425x devices support charging with a configurable charge current
> i_chg or a specific fixed low-current in what's called Low Charge mode.
> This patch exposes access to the Low Charge mode through a POWER_
> SUPPLY_PROP_C
On Thu, 10 Sep 2015, Mark Rutland wrote:
> On Thu, Sep 10, 2015 at 12:37:57PM +0100, Stefano Stabellini wrote:
> > On Thu, 10 Sep 2015, Mark Rutland wrote:
> > > > > Does Xen not talk to EFI itself and/or give the kernel a virtual EFI
> > > > > interface?
> > > >
> > > > Xen talks to EFI itself bu
On Tue, Sep 08, 2015 at 07:12:31PM -0500, Andreas Dannenberg wrote:
> This commit extends the use of the existing mutex to pave the way for
> using direct device access inside sysfs getter/setter routines in a
> way that the access during interrupts and timer routines does not
> interfere with devi
On Thu, 2015-09-10 at 07:08 -0600, Jan Beulich wrote:
> > > > On 10.09.15 at 14:58, wrote:
> > On Thu, 2015-09-10 at 13:15 +0100, Mark Rutland wrote:
> >
> > > > In any case this should be separate from the shim ABI discussion.
> > >
> > > I disagree; I think this is very much relevant to the AB
On 14 August 2015 at 18:55, Hongtao Wu wrote:
> the Spreadtrum MMC host driver is used to supply EMMC, SD, and
> SDIO types of memory cards
Perhaps some more information about the controller. Are there any
specific features it support or doesn't support!?
Moreover it would be nice to know a bit
On Tue, Sep 08, 2015 at 07:12:30PM -0500, Andreas Dannenberg wrote:
> A new optional device property called "ti,in-dpm-voltage" is introduced
> to allow configuring the input voltage threshold for the devices'
> dynamic power path management (DPM) feature. In short, it can be used to
> prevent the
>>> On 10.09.15 at 13:37, wrote:
> On Thu, 10 Sep 2015, Mark Rutland wrote:
>> Why can't Xen give a virtual EFI interface to Dom0 / guests? e.g.
>> create pages of RuntimeServicesCode that are trivial assembly shims
>> doing hypercalls, and plumb these into the virtual EFI memory map and
>> tables
On Tue, Sep 08, 2015 at 07:12:29PM -0500, Andreas Dannenberg wrote:
> A new optional device property called "ti,ovp-voltage" is introduced to
> allow configuring the input over voltage protection setting.
>
> This commit also adds the basic sysfs support for custom properties
> which is being used
1 - 100 of 151 matches
Mail list logo