Hi!
> "5. DT Bindings for flash & lens controllers
>
> There are drivers that create their MC topology using the device tree
> information,
> which works great for entities that transport data, but how to detect entities
> that don’t transport data such as flash devices, focusers, etc.? How can
Hi!
> > > This seems to be mostly in line with what has been discussed in the
> > > meeting,
> > > except that the patches add a device specific property. Please ignore the
> > > led patches in that tree for now (i.e. four patches on the top are the
> > > relevant ones here).
> > >
> >
> > I'm
On Fri, Apr 29, 2016 at 01:05:46PM +0200, Pali Rohár wrote:
> On Friday 29 April 2016 13:59:44 Sakari Ailus wrote:
> > > pavel@amd:/data/l/linux-n900$ git fetch
> > > git://git.retiisi.org.uk/~sailus/linux.git leds-as3645a:leds-as3645a
> > > fatal: unable to connect to git.retiisi.org.uk:
> > >
On Friday 29 April 2016 13:59:44 Sakari Ailus wrote:
> > pavel@amd:/data/l/linux-n900$ git fetch
> > git://git.retiisi.org.uk/~sailus/linux.git leds-as3645a:leds-as3645a
> > fatal: unable to connect to git.retiisi.org.uk:
> > git.retiisi.org.uk: Name or service not known
> >
> >
Hi Pavel,
On Fri, Apr 29, 2016 at 11:50:02AM +0200, Pavel Machek wrote:
> Hi!
>
> > > > adp1653 registers itself as a subdev, but there's no device that
> > > > register it as its part.
> > > >
> > > > (ad5820 driver seems to have the same problem).
> > > >
> > > > Is there example "dummy"
Hi!
> > Warning: I'm no DT expert, so this is just a first attempt.
> >
> > Platform drivers (omap3isp) will have to add these controller devices to
> > the list
> > of subdevs to load asynchronously.
>
> I seem to have patches I haven't had time to push back then:
>
>
Hi!
> > > adp1653 registers itself as a subdev, but there's no device that
> > > register it as its part.
> > >
> > > (ad5820 driver seems to have the same problem).
> > >
> > > Is there example "dummy" device I could use, for sole purpose of
> > > having these devices appear in /dev? They are
Hi Hans and Pavel,
On Fri, Apr 29, 2016 at 09:31:51AM +0200, Hans Verkuil wrote:
> On 04/29/2016 09:15 AM, Pavel Machek wrote:
> > Hi!
> >
> >> On n900, probe finishes ok (verified by adding printks), and the
> >> device shows up in /sys, but I don't get /dev/video* or
> >> /dev/v4l-subdev*.
>
On 04/29/2016 09:15 AM, Pavel Machek wrote:
> Hi!
>
>> On n900, probe finishes ok (verified by adding printks), and the
>> device shows up in /sys, but I don't get /dev/video* or
>> /dev/v4l-subdev*.
>>
>> Other drivers (back and front camera) load ok, and actually work. Any
>> idea what could
Hi!
> On n900, probe finishes ok (verified by adding printks), and the
> device shows up in /sys, but I don't get /dev/video* or
> /dev/v4l-subdev*.
>
> Other drivers (back and front camera) load ok, and actually work. Any
> idea what could be wrong?
Ok, so I guess I realized what is the
10 matches
Mail list logo
