On Mon, Feb 06, 2017 at 10:49:57AM +0100, Pavel Machek wrote:
> From: Sakari Ailus
>
> In the vast majority of cases the bus type is known to the driver(s)
> since a receiver or transmitter can only support a single one. There
> are cases however where different options are
Hi Pavel,
On Mon, Feb 06, 2017 at 10:49:57AM +0100, Pavel Machek wrote:
> From: Sakari Ailus
>
> In the vast majority of cases the bus type is known to the driver(s)
> since a receiver or transmitter can only support a single one. There
> are cases however where different
Hi!
> > - bus-type: data bus type. Possible values are:
> > - 0 - MIPI CSI2
> > - 1 - parallel / Bt656
> > - 2 - MIPI CSI1
> > - 3 - CCP2
> > + 0 - autodetect based on other properties (MIPI CSI2, parallel, Bt656)
>
> In the meantime, I also realised that we need to separate MIPI C-PHY and
From: Sakari Ailus
In the vast majority of cases the bus type is known to the driver(s)
since a receiver or transmitter can only support a single one. There
are cases however where different options are possible.
The existing V4L2 OF support tries to figure out the bus type
Hi Pavel,
On Fri, Feb 03, 2017 at 12:50:45PM +0100, Pavel Machek wrote:
> Hi!
>
> > > --- a/Documentation/devicetree/bindings/media/video-interfaces.txt
> > > +++ b/Documentation/devicetree/bindings/media/video-interfaces.txt
> > > @@ -76,6 +76,11 @@ Optional endpoint properties
> > >mode
Hi!
> > --- a/Documentation/devicetree/bindings/media/video-interfaces.txt
> > +++ b/Documentation/devicetree/bindings/media/video-interfaces.txt
> > @@ -76,6 +76,11 @@ Optional endpoint properties
> >mode horizontal and vertical synchronization signals are provided to the
> >slave device
Hi Ivaylo,
On Fri, Jan 20, 2017 at 09:59:13AM +0200, Ivaylo Dimitrov wrote:
> Hi,
>
> On 19.01.2017 23:49, Sakari Ailus wrote:
> >Hi Pavel,
> >
> >On Wed, Jan 11, 2017 at 11:53:35PM +0100, Pavel Machek wrote:
> >>From: Sakari Ailus
> >>
> >>In the vast majority of cases the
Hi,
On 19.01.2017 23:49, Sakari Ailus wrote:
Hi Pavel,
On Wed, Jan 11, 2017 at 11:53:35PM +0100, Pavel Machek wrote:
From: Sakari Ailus
In the vast majority of cases the bus type is known to the driver(s)
since a receiver or transmitter can only support a single one.
Hi Pavel,
On Wed, Jan 11, 2017 at 11:53:35PM +0100, Pavel Machek wrote:
> From: Sakari Ailus
>
> In the vast majority of cases the bus type is known to the driver(s)
> since a receiver or transmitter can only support a single one. There
> are cases however where different
Hi Baruch,
On Thu, Jan 12, 2017 at 02:06:03PM +0200, Baruch Siach wrote:
> Hi Pavel,
>
> On Wed, Jan 11, 2017 at 11:53:35PM +0100, Pavel Machek wrote:
> > From: Sakari Ailus
> >
> > In the vast majority of cases the bus type is known to the driver(s)
> > since a receiver
Hi Pavel,
On Wed, Jan 11, 2017 at 11:53:35PM +0100, Pavel Machek wrote:
> From: Sakari Ailus
>
> In the vast majority of cases the bus type is known to the driver(s)
> since a receiver or transmitter can only support a single one. There
> are cases however where different
Hi,
On Wed, Jan 11, 2017 at 11:53:35PM +0100, Pavel Machek wrote:
> From: Sakari Ailus
>
> In the vast majority of cases the bus type is known to the driver(s)
> since a receiver or transmitter can only support a single one. There
> are cases however where different options
From: Sakari Ailus
In the vast majority of cases the bus type is known to the driver(s)
since a receiver or transmitter can only support a single one. There
are cases however where different options are possible.
The existing V4L2 OF support tries to figure out the bus type
13 matches
Mail list logo