On Saturday 09 February 2013 04:31 AM, Grant Likely wrote:
> On Fri, 11 Jan 2013 11:50:23 +0530, Vineet Gupta
> wrote:
>> +- clock-frequency : the input clock frequency for the UART
>> +- baud : baud rate for UART
> change 'baud' to 'current-speed'. There is already precede
This implements a very basic I2C host driver for the BCM2835 SoC. Missing
features so far are:
* 10-bit addressing.
* DMA.
Reviewed-by: Grant Likely
Signed-off-by: Stephen Warren
---
v3:
* Return i2c_add_numbered_adapter() from probe() directly.
v2:
* Implemented clock divider configuration bas
On 02/09/2013 01:03 AM, Mauro Carvalho Chehab wrote:
Em Fri, 8 Feb 2013 21:38:07 +0100
Sebastian Hesselbarth escreveu:
This patch adds device tree parsing for gpio_ir_recv platform_data and
the mandatory binding documentation. It basically follows what we already
have for e.g. gpio_keys. All
On 02/08/2013 05:05 PM, Sylwester Nawrocki wrote:
> On 02/09/2013 12:21 AM, Stephen Warren wrote:
>> On 02/08/2013 04:16 PM, Sylwester Nawrocki wrote:
>>> On 02/07/2013 12:40 AM, Stephen Warren wrote:
> diff --git
> a/Documentation/devicetree/bindings/media/soc/samsung-fimc.txt
> b/Docu
On 02/09/2013 12:27 AM, Stephen Warren wrote:
On 02/08/2013 03:29 PM, Sylwester Nawrocki wrote:
On 02/07/2013 12:36 AM, Stephen Warren wrote:
On 02/01/2013 12:09 PM, Sylwester Nawrocki wrote:
s5p-csis is platform device driver for MIPI-CSI frontend to the FIMC
device. This patch support for bi
On 02/09/2013 12:21 AM, Stephen Warren wrote:
On 02/08/2013 04:16 PM, Sylwester Nawrocki wrote:
On 02/07/2013 12:40 AM, Stephen Warren wrote:
diff --git
a/Documentation/devicetree/bindings/media/soc/samsung-fimc.txt
b/Documentation/devicetree/bindings/media/soc/samsung-fimc.txt
+Samsung S5P/
On 02/07/2013 12:44 AM, Stephen Warren wrote:
On 02/01/2013 12:09 PM, Sylwester Nawrocki wrote:
Before the camera ports can be used the pinmux needs to be configured
properly. This patch adds a function to set the camera ports pinctrl
to a default state within the media driver's probe().
The cam
On 02/08/2013 03:29 PM, Sylwester Nawrocki wrote:
> On 02/07/2013 12:36 AM, Stephen Warren wrote:
>> On 02/01/2013 12:09 PM, Sylwester Nawrocki wrote:
>>> s5p-csis is platform device driver for MIPI-CSI frontend to the FIMC
>>> device. This patch support for binding the driver to the MIPI-CSIS
>>>
On 02/07/2013 12:42 AM, Stephen Warren wrote:
On 02/01/2013 12:09 PM, Sylwester Nawrocki wrote:
The sensor (I2C and/or SPI client) devices are instantiated by their
corresponding control bus drivers. Since the I2C client's master clock
is often provided by a video bus receiver (host interface) o
On 02/08/2013 04:16 PM, Sylwester Nawrocki wrote:
> On 02/07/2013 12:40 AM, Stephen Warren wrote:
>>> diff --git
>>> a/Documentation/devicetree/bindings/media/soc/samsung-fimc.txt
>>> b/Documentation/devicetree/bindings/media/soc/samsung-fimc.txt
>>
>>> +Samsung S5P/EXYNOS SoC Camera Subsystem (FIM
On 02/07/2013 12:40 AM, Stephen Warren wrote:
diff --git a/Documentation/devicetree/bindings/media/soc/samsung-fimc.txt
b/Documentation/devicetree/bindings/media/soc/samsung-fimc.txt
+Samsung S5P/EXYNOS SoC Camera Subsystem (FIMC)
+--
+
+The Exynos
On 02/07/2013 05:44 AM, Sachin Kamat wrote:
> Fixed a typo in referenced file name.
>
> Cc: Thomas Abraham
> Cc: Grant Likely
> Signed-off-by: Sachin Kamat
> ---
> .../devicetree/bindings/mmc/exynos-dw-mshc.txt |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Applied.
Rob
>
On 02/06/2013 02:30 PM, Paul Gortmaker wrote:
> From: Thomas Gleixner
>
> With the locking cleanup in place (from "OF: Fixup resursive
> locking code paths"), we can now do the conversion from the
> rw_lock to a raw spinlock as required for preempt-rt.
>
> The previous cleanup and this conversio
On Mon, 21 Jan 2013 19:02:29 +0800, Shawn Guo wrote:
> None of mmc drivers implements bus-width as a required device tree
> property. Instead, some drivers like atmel-mci, dw_mmc, sdhci-s3c
> implement it as an optional one, and will force bus width to be 1
> when the property is absent. Let's c
On Fri, 11 Jan 2013 11:50:23 +0530, Vineet Gupta
wrote:
> * DT binding for arc-uart
> * With alll the bits in place we can now use DT probing.
>
> Note that there's a bit of kludge right now because earlyprintk portion
> of driver can't use the DT infrastrcuture to get resoures/plat_data.
> This
On Thu, 10 Jan 2013 12:42:53 +0100, Linus Walleij
wrote:
> On Tue, Jan 8, 2013 at 12:14 PM, Viresh Kumar wrote:
> > On 8 January 2013 16:41, Lee Jones wrote:
> >>> Hmm.. I tried a bit, but couldn't find any such call :(
> >>> Probably an assumption is taken here. GPIO pins which are going to be
On Thu, 10 Jan 2013 16:40:09 +0100, Michal Simek wrote:
> Hi guys,
>
> we want to add static memory controller driver for xilinx zynq to the
> linux kernel. (It will go to drivers/memory/ folder)
> Just need to clear dts fragment which describe it.
>
> It is compatible with pl353 with 2 interfac
This patch adds device tree parsing for gpio_ir_recv platform_data and
the mandatory binding documentation. It basically follows what we already
have for e.g. gpio_keys. All required device tree properties are OS
independent but an optional property allows linux specific support for rc
maps.
Signe
From: Joe Perches
Date: Thu, 07 Feb 2013 13:46:27 -0800
> alloc failures already get standardized OOM
> messages and a dump_stack.
>
> For the affected mallocs around these OOM messages:
>
> Converted kmallocs with multiplies to kmalloc_array.
> Converted a kmalloc/memcpy to kmemdup.
> Removed
On 02/08/2013 03:04 PM, Grant Likely wrote:
> On Fri, 08 Feb 2013 15:24:25 -0600, Rob Herring wrote:
>> On 02/08/2013 08:45 AM, Grant Likely wrote:
>>> On Tue, 5 Feb 2013 12:06:28 -0700, Stephen Warren
>>> wrote:
From: Stephen Warren
Create cmd_dtc_cpp to run the C pre-processor
On Mon, 7 Jan 2013 17:42:08 +0100, Thomas Petazzoni
wrote:
> Now that we have a 7-segment display driver in the kernel, use it on
> the Marvell Armada XP DB evaluation board.
>
> Signed-off-by: Thomas Petazzoni
> ---
> arch/arm/boot/dts/armada-xp-db.dts |5 +
> 1 file changed, 5 inser
On Mon, 7 Jan 2013 21:41:48 +, Arnd Bergmann wrote:
> On Monday 07 January 2013, Thomas Petazzoni wrote:
> > Dear Arnd Bergmann,
> >
> > On Mon, 7 Jan 2013 19:43:39 +, Arnd Bergmann wrote:
> >
> > > > .../devicetree/bindings/misc/gpio-7seg.txt | 18 +++
> > > > drivers/misc/Kc
On Mon, 7 Jan 2013 17:42:06 +0100, Thomas Petazzoni
wrote:
> This patch adds a driver to control 7-segment displays connected over
> GPIOs through a BCD encoder. Typically, up to four GPIOs go into a BCD
> encoder, that drives the 7-segment display to display a numeric value
> between 0 and 2^ng
Vivek Gautam wrote:
>
> Adding EHCI device tree node for Exynos5250 along with
> the device base adress and gpio line for vbus.
>
> Signed-off-by: Vivek Gautam
> Acked-by: Jingoo Han
> Acked-by: Grant Likely
> ---
>
> Changes from v4:
> - Added gpio line for VBUS of USB2.0 on snow board.
>
On 02/07/2013 12:36 AM, Stephen Warren wrote:
On 02/01/2013 12:09 PM, Sylwester Nawrocki wrote:
s5p-csis is platform device driver for MIPI-CSI frontend to the FIMC
device. This patch support for binding the driver to the MIPI-CSIS
devices instantiated from device tree and for parsing all SoC an
On Fri, Feb 8, 2013 at 5:28 PM, Arnd Bergmann wrote:
> On Friday 08 February 2013 16:22:48 Russell King - ARM Linux wrote:
>> If it's DMA _to_ a device, then we will only ever clean the lines prior to
>> a transfer, never invalidate them. So that's not really a concern. (There
>> better not be a
On Thu, 7 Feb 2013 08:21:18 -0500, Jason Cooper wrote:
> On Thu, Feb 07, 2013 at 12:22:56PM +, Grant Likely wrote:
> > leds-ns2.txt is a binding for LEDs, not GPIOs. Move the documentation in
> > with the rest of the LEDs bindings.
> >
> > Cc: Andrew Lunn
> > Cc: Simon Guinot
> > Cc: Jason
On Fri, 08 Feb 2013 15:24:25 -0600, Rob Herring wrote:
> On 02/08/2013 08:45 AM, Grant Likely wrote:
> > On Tue, 5 Feb 2013 12:06:28 -0700, Stephen Warren
> > wrote:
> >> From: Stephen Warren
> >>
> >> Create cmd_dtc_cpp to run the C pre-processor on *.dts file before
> >> passing them to dtc
On 02/08/2013 10:50 PM, Grant Likely wrote:
On Thu, 03 Jan 2013 08:03:34 -0500, Ajay Kumar wrote:
Add documentation for the DT bindings in exynos G2D driver.
Signed-off-by: Ajay Kumar
Applied, thanks.
Hi Grant,
I believe this patch should not be applied. The compatible property has
change
On 02/08/2013 10:36 PM, Sebastian Hesselbarth wrote:
You could also make it:
#define gpio_ir_recv_get_devtree_pdata (-ENOSYS)
Hmm, does that also play with parameter passing of the
CONFIG_OF gpio_ir_recv_get_devtree_pdata() ?
Oops, should have been:
#define gpio_ir_recv_get_devtree_pdata(de
On Thu, 03 Jan 2013 08:03:34 -0500, Ajay Kumar wrote:
> Add documentation for the DT bindings in exynos G2D driver.
>
> Signed-off-by: Ajay Kumar
Applied, thanks.
g.
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://list
On Wed, 2 Jan 2013 22:46:18 -0700, Stephen Warren
wrote:
> This implements a very basic I2C host driver for the BCM2835 SoC. Missing
> features so far are:
>
> * Clock rate adjustment.
> * 10-bit addressing.
> * DMA.
>
> Signed-off-by: Stephen Warren
> ---
> .../devicetree/bindings/i2c/brcm,
On Fri, 21 Dec 2012 10:13:50 -0800, Doug Anderson wrote:
> Vivek,
>
>
> On Fri, Dec 21, 2012 at 12:16 AM, Vivek Gautam
> wrote:
> > Hi all,
> >
> >
> > On Wed, Dec 19, 2012 at 7:20 PM, Vivek Gautam
> > wrote:
> >> CC: Doug Anderson
> >>
> >>
> >> On Sat, Dec 15, 2012 at 12:53 PM, Grant Likely
On Wed, 2 Jan 2013 10:13:03 -0800, Peng Wu wrote:
> On 12/28/2012 08:43 PM, Olof Johansson wrote:
> > On Fri, Dec 28, 2012 at 3:54 PM, Stephen Warren wrote:
> >> On 12/28/2012 09:22 AM, Rob Herring wrote:
> >>> On 12/20/2012 01:41 PM, Bryan Wu wrote:
> This patch adds support for Tegra30 Bea
On 02/08/2013 10:26 PM, Sylwester Nawrocki wrote:
On 02/08/2013 09:38 PM, Sebastian Hesselbarth wrote:
This patch adds device tree parsing for gpio_ir_recv platform_data and
the mandatory binding documentation. It basically follows what we already
have for e.g. gpio_keys. All required device tre
On Fri, 28 Dec 2012 13:47:24 +0100, Andrew Lunn wrote:
> Move the Kirkwood cpuidle driver out of arch/arm/mach-kirkwood and
> into drivers/cpuidle. Convert the driver into a platform driver and
> add a device tree binding. Add a DT node to instantiate the driver for
> boards converted to DT, and a
On 02/08/2013 09:38 PM, Sebastian Hesselbarth wrote:
This patch adds device tree parsing for gpio_ir_recv platform_data and
the mandatory binding documentation. It basically follows what we already
have for e.g. gpio_keys. All required device tree properties are OS
independent but an optional pro
On 02/08/2013 08:45 AM, Grant Likely wrote:
> On Tue, 5 Feb 2013 12:06:28 -0700, Stephen Warren
> wrote:
>> From: Stephen Warren
>>
>> Create cmd_dtc_cpp to run the C pre-processor on *.dts file before
>> passing them to dtc for final compilation. This allows the use of #define
>> and #include
On Fri, Feb 8, 2013 at 5:18 PM, Stephen Warren wrote:
> On 02/08/2013 07:45 AM, Grant Likely wrote:
>> On Tue, 5 Feb 2013 12:06:28 -0700, Stephen Warren
>> wrote:
>>> From: Stephen Warren
>>>
>>> Create cmd_dtc_cpp to run the C pre-processor on *.dts file before
>>> passing them to dtc for fin
This patch adds device tree parsing for gpio_ir_recv platform_data and
the mandatory binding documentation. It basically follows what we already
have for e.g. gpio_keys. All required device tree properties are OS
independent but an optional property allow linux specific support for rc
maps.
There
On Mon, 4 Feb 2013 12:32:16 +0100, Philipp Zabel
wrote:
> This driver requests and remaps a memory region as configured in the
> device tree. It serves memory from this region via the genalloc API.
> It optionally enables the SRAM clock.
>
> Other drivers can retrieve the genalloc pool from a p
On 02/06/2013 06:18 PM, Sebastian Hesselbarth wrote:
>>> +Optional properties:
>>> +- linux,allowed-rc-protocols: Linux specific u64 bitmask of allowed
>>> +rc protocols.
>>
>> You likely need to specify in these bindings documentation which bit
>> corresponds to which RC protocol.
>>
>
On 02/07/2013 07:44 PM, Tony Lindgren wrote:
> * Jon Hunter [130207 16:55]:
>>
>> Ugh, looks like linux-next is broken for omap2+ boards at the moment
>> and is panic'ing in the twl i2c code ... some else to look into ...
>>
>> Peter have you seen this on linux-next? I am seeing this on omap2-4 b
On Fri, Feb 8, 2013 at 6:57 PM, Mauro Carvalho Chehab
wrote:
> Em Wed, 06 Feb 2013 18:18:22 +0100
> Sebastian Hesselbarth escreveu:
>> On 02/06/2013 02:48 PM, Sylwester Nawrocki wrote:
>> > On 02/06/2013 09:03 AM, Sebastian Hesselbarth wrote:
>> >> This patch adds device tree parsing for gpio_ir_
On 02/08/2013 07:45 AM, Grant Likely wrote:
> On Tue, 5 Feb 2013 12:06:28 -0700, Stephen Warren
> wrote:
>> From: Stephen Warren
>>
>> Create cmd_dtc_cpp to run the C pre-processor on *.dts file before
>> passing them to dtc for final compilation. This allows the use of #define
>> and #include
On Friday 08 February 2013 16:22:48 Russell King - ARM Linux wrote:
> If it's DMA _to_ a device, then we will only ever clean the lines prior to
> a transfer, never invalidate them. So that's not really a concern. (There
> better not be any dirty cache lines associated with the empty zero page
>
On Thu, Feb 07, 2013 at 10:15:48PM +0100, Arnd Bergmann wrote:
> On Thursday 07 February 2013 21:19:04 Linus Walleij wrote:
> > On Thu, Feb 7, 2013 at 8:42 PM, Arnd Bergmann wrote:
> > > On Thursday 07 February 2013, Linus Walleij wrote:
> >
> > >> Actually I once read about a feature where the k
On Thu, Feb 07, 2013 at 07:29:17PM +0100, Linus Walleij wrote:
> Actually I once read about a feature where the kernel provides
> a static page full of zeroes or something like this, that would be
> ideal to use in cases like this, then all of this dummy page
> allocation and freeing can be deleted
On 02/07/2013 08:39 AM, Arnd Bergmann wrote:
> On Wednesday 06 February 2013, Jon Hunter wrote:
>> +static struct of_dma_filter_info info;
>
> Both members of this structure are constant, so you can just initialize it
> here,
> and it would be nice to give it a more descriptive name, such as
>
On 02/08/2013 01:55 AM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Feb 07, 2013 at 07:05:06PM -0600, Jon Hunter wrote:
>> If the device-tree blob is present during boot, then register the SDMA
>> controller with the device-tree DMA driver so that we can use device-tree
>> to look-up DMA client informa
On Tue, 5 Feb 2013 12:06:28 -0700, Stephen Warren
wrote:
> From: Stephen Warren
>
> Create cmd_dtc_cpp to run the C pre-processor on *.dts file before
> passing them to dtc for final compilation. This allows the use of #define
> and #include within the .dts file.
>
> Acked-by: Simon Glass
>
The device tree binding models Tegra114 CAR (Clock And Reset) as a single
monolithic clock provider.
Signed-off-by: Peter De Schrijver
---
.../bindings/clock/nvidia,tegra114-car.txt | 316
1 files changed, 316 insertions(+), 0 deletions(-)
create mode 100644
Docum
On Fri, 01 Feb 2013 21:24:44 +0530, Naveen Krishna Chatradhi
wrote:
> Adds support for High Speed I2C driver found in Exynos5 and later
> SoCs from Samsung. This driver currently supports Auto mode.
>
> Driver only supports Device Tree method.
> Note: Added debugfs support for registers view, no
On Thu, 20 Dec 2012 23:12:12 +0100, Andreas Fenkart
wrote:
> Without functional clock the omap_hsmmc module can't forward
> SDIO IRQs to the system. This patch reconfigures dat1 line
> as a gpio while the fclk is off. And uses SDIO IRQ detection of
> the module, while fclk is present.
>
> Signed
On 02/07/2013 10:20 PM, Padma Venkat wrote:
> Hi Rob,
>
> On Wed, Feb 6, 2013 at 8:54 PM, Rob Herring wrote:
>> On 02/06/2013 12:18 AM, Padmavathi Venna wrote:
>>> This patch adds #dma-cells property to PL330 DMA controller
>>> nodes for supporting generic dma dt bindings on samsung
>>> exynos525
On Fri, 11 Jan 2013 10:09:19 -0700, Stephen Warren
wrote:
> On 01/10/2013 06:41 PM, Simon Glass wrote:
> > Some matrix keypad drivers can support different numbers of rows and
> > columns. Add a generic binding for these.
> >
> > Implementation note:
> >
> > In order to implement this binding i
Hi,
On Fri, Feb 08, 2013 at 15:07:54, Mark Rutland wrote:
> Hi,
>
> [...]
>
> > > > diff --git a/Documentation/devicetree/bindings/mmc/davinci_mmc.txt
> > > > b/Documentation/devicetree/bindings/mmc/davinci_mmc.txt
> > > > new file mode 100644
> > > > index 000..6717ab1
> > > > --- /dev/nul
Hi,
[...]
> > > diff --git a/Documentation/devicetree/bindings/mmc/davinci_mmc.txt
> > > b/Documentation/devicetree/bindings/mmc/davinci_mmc.txt
> > > new file mode 100644
> > > index 000..6717ab1
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/mmc/davinci_mmc.txt
> > > @@
On Friday 08 February 2013 06:35 AM, Jon Hunter wrote:
Adds device-tree bindings from SDMA on OMAP2+ devices. DMA client
bindings are also added for devices that have SPI and MMC bindings
populated. Client binding data is based upon existing HWMOD data for
OMAP and has been checked against OMAP d
The DTC labels feature allows a dts file to reference a node without
having to reproduce the entire node hierarchy above it. We can use this
to simplify the MPC5200 board dts files by referencing the gpt nodes by
label.
Cc: Anatolij Gustschin
Signed-off-by: Grant Likely
---
arch/powerpc/boot/dt
The Lite5200 evaluation board has a number of debug LEDs that Linux
doesn't know about yet. This change adds a gpio-leds stanza to the
lite5200 device tree so that the correct driver can get hooked up.
Also, make use of the dtc labels feature to reduce the number of source
lines required to add th
61 matches
Mail list logo
