On 08/03/14 14:25, Grant Likely wrote:
> Sure. If endpoints are logical, then only create the ones actually
> hooked up. No problem there. But nor do I see any issue with having
> empty connections if the board author things it makes sense to have them
> in the dtsi.
I don't think they are usuall
On 08/03/14 14:23, Grant Likely wrote:
>>> That's fine. In that case the driver would specifically require the
>>> endpoint to be that one node although the above looks a little weird
>>
>> The driver can't require that. It's up to the board designer to decide
>> how many endpoints are used. A
On 08/03/14 17:54, Laurent Pinchart wrote:
>> Sylwester suggested as an alternative, if I understood correctly, to
>> drop the endpoint node and instead keep the port:
>>
>> device-a {
>> implicit_output_ep: port {
>> remote-endpoint = <&explicit_input_ep>;
>> };
>>
Hi Kamil,
On Fri, Mar 7, 2014 at 6:18 PM, Kamil Debski wrote:
> Hi Arun,
>
>> From: Arun Kumar K [mailto:arunkk.sams...@gmail.com]
>> Sent: Friday, March 07, 2014 12:10 PM
>>
>> Hi Sylwester,
>>
>> On Fri, Mar 7, 2014 at 2:59 PM, Sylwester Nawrocki
>> wrote:
>> > Hi,
>> >
>> > On 07/03/14 09:31,
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Mon Mar 10 04:00:29 CET 2014
git branch: test
git hash: f2d7313534072a5fe192e7cf46204b413acef479
gcc versio
Hi Mauro,
Yes, I fixed my problem, that I mentioned to you in an earlier mail,
please just pull this one patch from my tree @ linuxtv.org, assuming the
MAINTAINERS patch goes in separately:
The following changes since commit 1b0a7e3263168a06d3858798e48c5a21d1c78d3c:
Add linux-next specific f
On Fri, Mar 07, 2014 at 06:38:02PM +, Grant Likely wrote:
> On Wed, 5 Mar 2014 10:20:40 +0100, Philipp Zabel
> wrote:
> > For simple devices with only one port, it can be made implicit.
> > The endpoint node can be a direct child of the device node.
> >
> > Signed-off-by: Philipp Zabel
>
This patch is almost identical to the earlier RFC version:
https://patchwork.linuxtv.org/patch/21780/
The only changes are that it has been rebased to the latest vb2 changes so it
can take advantage of the min_buffers_needed field and it adds code to requeue
buffers in case of a failure when star
