On Sat, Dec 15, 2012 at 08:02:39PM +0100, Guennadi Liakhovetski wrote:
> Hi Simon
>
> Thanks for your comments. I'll reply to other your reviews later, I think,
> let me just briefly clarify this one.
>
> On Sat, 15 Dec 2012, Simon Horman wrote:
>
> > On Fri, Dec 14, 2012 at 05:45:30PM +0100, G
From: Guennadi Liakhovetski
This patch adds a document describing common OF bindings for video
capture, output and video processing devices. It is currently mainly
focused on video capture devices, with data interfaces defined in
standards like ITU-R BT.656 or MIPI CSI-2.
It also documents a meth
Hi Simon
Thanks for your comments. I'll reply to other your reviews later, I think,
let me just briefly clarify this one.
On Sat, 15 Dec 2012, Simon Horman wrote:
> On Fri, Dec 14, 2012 at 05:45:30PM +0100, Guennadi Liakhovetski wrote:
> > This patch adds dynamic switching to booting either wit
On Sat, Dec 15, 2012 at 12:32:24AM +, Grant Likely wrote:
> On Wed, 12 Dec 2012 10:46:00 +0200, Felipe Balbi wrote:
> > there are a few spi master drivers which make
> > use of that flag but there is no way to pass it
> > through devicetree.
> >
> > This patch just creates a way to pass SPI_L
On Fri, Dec 14, 2012 at 09:06:49AM -0700, Stephen Warren wrote:
> On 12/13/2012 10:50 PM, Naveen Krishna Chatradhi wrote:
> > +The first should be an output, and is used to claim the I2C bus,
> > +the second should be an input, and signals that the other side (Client)
> > +wants to claim the bus.
Fixes the following warning:
include/linux/of_platform.h:106:13: warning: 'struct device' declared inside
parameter list [enabled by default]
include/linux/of_platform.h:106:13: warning: its scope is only this definition
or declaration, which is probably not what you want [enabled by default]
S
On Fri, Dec 14, 2012 at 05:45:25PM +0100, Guennadi Liakhovetski wrote:
> Two of four interrupt controllers in sh7372.dtsi are missing the compulsory
> "#interrupt-cells" properties. Fix this.
Thanks.
I think that is fixed in the latest INTC DT series that I posted just
a few moments ago "[RFC v7
On Fri, Dec 14, 2012 at 05:45:26PM +0100, Guennadi Liakhovetski wrote:
> Mackerel's .dts Device Tree description file should derive from the SoC's
> .dtsi, not from skeleton.dtsi directly.
>
> Signed-off-by: Guennadi Liakhovetski
Thanks applied.
I have applied this to a temporary 'boards4' bran
On Fri, Dec 14, 2012 at 05:45:28PM +0100, Guennadi Liakhovetski wrote:
> When booting with DT, devices are named differently. To get their clocks
> additional entries have to be added to the lookup table.
Thanks applied.
I have applied this to a temporary 'soc5' branch which is based on 3.7-rc1.
On Fri, Dec 14, 2012 at 05:45:30PM +0100, Guennadi Liakhovetski wrote:
> This patch adds dynamic switching to booting either with or without DT.
> So far only a part of the board initialisation can be done via DT. Devices,
> that still need platform data are kept that way. Devices, that can be
> in
On Fri, Dec 14, 2012 at 05:45:27PM +0100, Guennadi Liakhovetski wrote:
> Extend DT interrupt controller initialisation to automatically fall back to
> platform data based configuration, if booting without DT. This simplifies
> implementing boards, capable of booting in either mode with a single ker
On Fri, Dec 14, 2012 at 05:45:29PM +0100, Guennadi Liakhovetski wrote:
> For boards booting without DT no changes should be caused by this patch.
> When booting with DT, devices, whose drivers support DT probing, will not
> be registered.
This relates in part to my comment on "ARM: sh7372: support
12 matches
Mail list logo
