Hi Jacob,
On Thu, Nov 30, 2017 at 09:37:06AM +0800, Jacob Chen wrote:
> Hi Sakari,
>
> On 2017年11月29日星期三 CST 下午2:29:03 you wrote:
> > Hi Jacob,
> >
> > On Mon, Nov 27, 2017 at 03:03:59PM +0800, Jacob Chen wrote:
> > > Hi,
> > >
> > > On 2017年11月25日星期六 CST 下午1:05:42 you wrote:
> > > > Hi,
> > >
Hi Jacob,
On Mon, Nov 27, 2017 at 03:03:59PM +0800, Jacob Chen wrote:
> Hi,
>
> On 2017年11月25日星期六 CST 下午1:05:42 you wrote:
> > Hi,
> >
> > On 2017年11月24日星期五 CST 下午6:19:36 you wrote:
> > > On Fri, Nov 24, 2017 at 6:17 PM, Sakari Ailus
> > >
> > > wrote:
> > > > Hi Tomasz,
> > > >
> > > > On Fr
On Fri, Nov 24, 2017 at 6:17 PM, Sakari Ailus
wrote:
> Hi Tomasz,
>
> On Fri, Nov 24, 2017 at 06:03:26PM +0900, Tomasz Figa wrote:
>> Hi Sakari,
>>
>> We have the following graph:
>>
>> ISP (registers notifier for v4l2_dev)
>>
>> |
>>
>> PHY (registers notifier for v4l2_subdev, just l
Hi Tomasz,
On Fri, Nov 24, 2017 at 06:03:26PM +0900, Tomasz Figa wrote:
> Hi Sakari,
>
> We have the following graph:
>
> ISP (registers notifier for v4l2_dev)
>
> |
>
> PHY (registers notifier for v4l2_subdev, just like sensors for
> flash/focuser)
>
> | \
>
> sensor0
Hi Sakari,
We have the following graph:
ISP (registers notifier for v4l2_dev)
|
PHY (registers notifier for v4l2_subdev, just like sensors for
flash/focuser)
| \
sensor0 sensor1
...
Both ISP and PHY are completely separate drivers not directly aware of
each other, sin
Hi Jacob,
On Fri, Nov 24, 2017 at 09:00:14AM +0800, Jacob Chen wrote:
> Hi Sakari,
>
> I encountered a problem when using async sub-notifiers.
>
> It's like that:
> There are two notifiers, and they are waiting for one subdev.
> When this subdev is probing, only one notifier is completed
Hi Sakari,
I encountered a problem when using async sub-notifiers.
It's like that:
There are two notifiers, and they are waiting for one subdev.
When this subdev is probing, only one notifier is completed and
the other one is skipped.
I found that in v15 of patch "v4l: async: Allow bindi