On Mon, 31 Aug 2009, Hans Verkuil wrote:
> The image format is something that should be setup by a separate API. Guennadi
> has a proposal for that which is being discussed. Although I wonder whether
> these two APIs should perhaps be combined into one. Don't know yet.
>
> In particular I wonder
On Monday 31 August 2009 17:54:18 Sakari Ailus wrote:
> Hans Verkuil wrote:
> > Hi all,
> >
> > This is an updated RFC on how to setup the bus for sub-devices.
> >
> > It is based on work from Guennadi and Muralidharan.
> >
> > The problem is that both sub-devices and bridge devices have to conf
Sakari,
>
>The bus type should be definitely included. If a bridge has several
>different receivers, say parallel, CSI1 and CSI2, which of them should
>be configured to receive data unless that's part of the bus configuration?
I agree and I have responded to have it included in the RFC.
>
>> This
On Mon, 31 Aug 2009, Hans Verkuil wrote:
> That's correct: the master provides the pixel clock signal. I'm not sure
> if it also means that the syncs are provided by the master. Do you know?
In all docs I've seen so far "master mode" means "sensor generates pixel
clock," nothing changes for othe
On Mon, 31 Aug 2009, Sakari Ailus wrote:
> How would the image format be defined then...? The ISP in this case can mangle
> the image format the way it wants so what's coming from the sensor can be
> quite different from what's coming out of the ISP. Say, sensor produces raw
> bayer and ISP writes
Hans Verkuil wrote:
Hi all,
This is an updated RFC on how to setup the bus for sub-devices.
It is based on work from Guennadi and Muralidharan.
The problem is that both sub-devices and bridge devices have to configure
their bus correctly so that they can talk to one another. We need a
standard
>>
>> Master/Slave is always confusing to me. In VPFE, it can act as master
>> (when it output sync signal and pixel clock) and slave (when it get sync
>> signal from sensor/decoder). We use VPFE as slave and sensor/decoder will
>> provide the pixel clock and sync signal. Please confirm if this is
>>>
>>> Up to now I usually saw the master-slave relationship defined as per
>>> whether the protocol is "master" or "slave," which always was used from
>>> the PoV of the bridge. I.e., even in a camera datasheet a phrase like
>>> "supports master-parallel mode" means supports a mode in which the
>>
>> Up to now I usually saw the master-slave relationship defined as per
>> whether the protocol is "master" or "slave," which always was used from
>> the PoV of the bridge. I.e., even in a camera datasheet a phrase like
>> "supports master-parallel mode" means supports a mode in which the bridge
On Monday 31 August 2009 00:31:01 Laurent Pinchart wrote:
> Hi Hans,
>
> thanks for putting this all together.
>
> On Saturday 29 August 2009 16:31:13 Hans Verkuil wrote:
> > Hi all,
> >
> > This is an updated RFC on how to setup the bus for sub-devices.
> >
> > It is based on work from Guennadi
On Monday 31 August 2009 00:19:38 Guennadi Liakhovetski wrote:
> On Sat, 29 Aug 2009, Hans Verkuil wrote:
>
> > Hi all,
> >
> > This is an updated RFC on how to setup the bus for sub-devices.
> >
> > It is based on work from Guennadi and Muralidharan.
> >
> > The problem is that both sub-device
Hi Hans,
thanks for putting this all together.
On Saturday 29 August 2009 16:31:13 Hans Verkuil wrote:
> Hi all,
>
> This is an updated RFC on how to setup the bus for sub-devices.
>
> It is based on work from Guennadi and Muralidharan.
>
> The problem is that both sub-devices and bridge devices
On Sat, 29 Aug 2009, Hans Verkuil wrote:
> Hi all,
>
> This is an updated RFC on how to setup the bus for sub-devices.
>
> It is based on work from Guennadi and Muralidharan.
>
> The problem is that both sub-devices and bridge devices have to configure
> their bus correctly so that they can tal
Hi all,
This is an updated RFC on how to setup the bus for sub-devices.
It is based on work from Guennadi and Muralidharan.
The problem is that both sub-devices and bridge devices have to configure
their bus correctly so that they can talk to one another. We need a
standard way of configuring su
14 matches
Mail list logo