Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <313827c0-3b7a-e70a-b281-cbb5f68e6fd2@xs4all.nl>
Date:   Tue, 13 Jun 2023 14:26:34 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.11.0
Subject: Re: [RESEND PATCH v6 1/1] Added Digiteq Automotive MGB4 driver
Content-Language: en-US
To:     =?UTF-8?Q?Martin_T=c5=afma?= <tumic@gpxsee.org>,
        Mauro Carvalho Chehab <mchehab@kernel.org>
Cc:     linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
        =?UTF-8?Q?Martin_T=c5=afma?= <martin.tuma@digiteqautomotive.com>
References: <20230524112126.2242-1-tumic@gpxsee.org>
 <20230524112126.2242-2-tumic@gpxsee.org>
 <3a7da3cd-8d03-a2c4-0534-a75565aefc13@xs4all.nl>
 <c544814a-7d99-add9-0397-d56776f911dd@gpxsee.org>
 <0cec2b34-01bb-ec0e-f215-9e6ed3f44e73@xs4all.nl>
 <5021c762-3435-719b-18a3-def7888fb5f6@gpxsee.org>
From:   Hans Verkuil <hverkuil-cisco@xs4all.nl>
In-Reply-To: <5021c762-3435-719b-18a3-def7888fb5f6@gpxsee.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: bulk

On 12/06/2023 16:36, Martin Tůma wrote:
> On 12. 06. 23 10:42, Hans Verkuil wrote:
>> On 08/06/2023 13:16, Martin Tůma wrote:
>>> Hi,
>>> This is the "technical" part of my response, comments bellow:
>>>
>>> On 07. 06. 23 10:41, Hans Verkuil wrote:
>>>> Hi Martin,
>>>>
>>>> Some comments below:
>>>>
>>>> On 24/05/2023 13:21, tumic@gpxsee.org wrote:
>>>>> From: Martin Tůma <martin.tuma@digiteqautomotive.com>
>>>
>>>>> diff --git a/Documentation/admin-guide/media/mgb4.rst b/Documentation/admin-guide/media/mgb4.rst
>>>>> new file mode 100644
>>>>> index 000000000000..77db2fa64ab4
>>>>> --- /dev/null
>>>>> +++ b/Documentation/admin-guide/media/mgb4.rst
>>>>> @@ -0,0 +1,352 @@
>>>>> +.. SPDX-License-Identifier: GPL-2.0
>>>>> +
>>>>
>>>> Perhaps it is a good idea to start with a high level overview of the
>>>> hardware blocks. That might help understand how the various parts are
>>>> connected.
>>>>
>>>
>>> This is the "admin-guide" documentation and I'm not sure if the admins (= the card users) are interested in some hardware blocks description. I can for sure ad some basic info like that the card (with
>>> the given module) has two inputs and two outputs, but if you hold the card in your hands while installing it into the PCIe slot you definitely notice that ;-)
>>
>> True, but I don't have that module :-).
>>
>> I assume the inputs (and also outputs) are mutually exclusive? I.e., only one at a time can be active?
>>
>> But it is also possible to switch between the inputs/outputs dynamically if you want?
>>
>> Right now it is hard coded through this property, but I assume there is a reason these
>> modules have two inputs and two outputs, so it is odd that it is not possible use
>> VIDIOC_S_INPUT/S_OUTPUT to toggle between them.
>>
> 
> With the current modules, you can not even theoretically (after changing the FPGA bitstream) change the outputs to inputs or vice versa as the the serializers/deserializers are hardcoded on the modules.

I think you misunderstand me.

Let's keep it simple: a source is connected to input 0 and you capture from it with V4L2.

Can I dynamically switch to input 1 and capture from that? I.e., each input has a
different source connected to it, so userspace can select from which input to capture.

Right now it appears that V4L2 just advertises a single input. And the input_id
property is read-only. So that means that input 1 is effectively unusable with
the current driver, or am I missing something?

> 
> I can post here some photo of the card, if it is ok to send image attachement to the mailing list so you have some image of what we are talking about. Or I can even show you the card live when you are
> in Prague in few days.

Actually, I'd like that! We'll meet there anyway, so that's a good opportunity to
see the real deal :-)

Regards,

	Hans