From: Daniel Scally <djrscally@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, libcamera-devel@lists.libcamera.org,
laurent.pinchart@ideasonboard.com, hanlinchen@chromium.org,
tfiga@chromium.org, hdegoede@redhat.com,
kieran.bingham@ideasonboard.com, hpa@redhat.com
Subject: Re: [PATCH 3/5] media: entity: Skip non-data links in graph iteration
Date: Tue, 14 Dec 2021 21:37:14 +0000 [thread overview]
Message-ID: <e6d79347-0fc7-9e94-f968-e630ac87d451@gmail.com> (raw)
In-Reply-To: <YbkLBobSglC1sgsF@paasikivi.fi.intel.com>
Hi Sakari
On 14/12/2021 21:22, Sakari Ailus wrote:
> Hi Daniel,
>
> On Tue, Dec 14, 2021 at 04:14:21PM +0000, Daniel Scally wrote:
>> Hi Sakari
>>
>> On 14/12/2021 15:01, Sakari Ailus wrote:
>>> Hi Daniel,
>>>
>>> On Mon, Dec 13, 2021 at 11:28:47PM +0000, Daniel Scally wrote:
>>>> When iterating over the media graph, don't follow links that are not
>>>> pad-to-pad links.
>>>>
>>>> Signed-off-by: Daniel Scally <djrscally@gmail.com>
>>>> ---
>>>> Changes since the rfc:
>>>>
>>>> - new patch
>>>>
>>>> drivers/media/mc/mc-entity.c | 8 ++++++++
>>>> 1 file changed, 8 insertions(+)
>>>>
>>>> diff --git a/drivers/media/mc/mc-entity.c b/drivers/media/mc/mc-entity.c
>>>> index d79eb88bc167..aeddc3f6310e 100644
>>>> --- a/drivers/media/mc/mc-entity.c
>>>> +++ b/drivers/media/mc/mc-entity.c
>>>> @@ -325,6 +325,14 @@ static void media_graph_walk_iter(struct media_graph *graph)
>>>>
>>>> link = list_entry(link_top(graph), typeof(*link), list);
>>>>
>>>> + /* If the link is not a pad-to-pad link, don't follow it */
>>> This comment should mention data links, not pad-to-pad links.
>>
>> I wondered about the terminology of this actually...since we create
>> those links with media_create_pad_link(), and they're called pad-to-pad
>> links in the documentation [1], but in other cases called data links. Do
>> we need to fix those other references too?
>>
>>
>>
>> [1] https://www.kernel.org/doc/html/v5.0/media/kapi/mc-core.html#links
> Good point.
>
> There were only one type of links before the interface links were
> introduced. Some of the documentation seems to discuss pad links whereas
> the corresponding macro name is MEDIA_LNK_FL_DATA_LINK. What the links
> really represent is flow of data.
>
> It would be good to align this, although that should probably be done in a
> different context from this patchset.
>
Ack; I'll fix the comment as you suggested for now
next prev parent reply other threads:[~2021-12-14 21:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 23:28 [PATCH 0/5] Introduce ancillary links Daniel Scally
2021-12-13 23:28 ` [PATCH 1/5] media: media.h: Add new media link type Daniel Scally
2021-12-14 21:50 ` Laurent Pinchart
2021-12-14 21:52 ` Daniel Scally
2021-12-13 23:28 ` [PATCH 2/5] media: entity: Add link_type() helper Daniel Scally
2021-12-14 21:54 ` Laurent Pinchart
2021-12-14 21:57 ` Daniel Scally
2021-12-13 23:28 ` [PATCH 3/5] media: entity: Skip non-data links in graph iteration Daniel Scally
2021-12-14 15:01 ` Sakari Ailus
2021-12-14 16:14 ` Daniel Scally
2021-12-14 21:22 ` Sakari Ailus
2021-12-14 21:37 ` Daniel Scally [this message]
2021-12-14 22:05 ` Laurent Pinchart
2021-12-13 23:28 ` [PATCH 4/5] media: entity: Add support for ancillary links Daniel Scally
2021-12-14 4:06 ` kernel test robot
2021-12-14 21:25 ` Sakari Ailus
2021-12-14 21:54 ` Daniel Scally
2021-12-14 22:14 ` Laurent Pinchart
2022-01-16 23:52 ` Daniel Scally
2021-12-13 23:28 ` [PATCH 5/5] media: v4l2-async: Create links during v4l2_async_match_notify() Daniel Scally
2021-12-14 22:22 ` Laurent Pinchart
2021-12-14 22:36 ` Daniel Scally
2021-12-14 23:01 ` Laurent Pinchart
2021-12-14 23:41 ` Daniel Scally
2021-12-15 9:04 ` Laurent Pinchart
2021-12-15 9:44 ` Sakari Ailus
2021-12-15 9:55 ` Laurent Pinchart
2021-12-15 23:10 ` Daniel Scally
2021-12-15 23:14 ` Laurent Pinchart
2022-01-16 0:01 ` Daniel Scally
2021-12-16 11:10 ` kernel test robot
2021-12-16 11:14 ` Daniel Scally
2021-12-15 9:25 ` [PATCH 0/5] Introduce ancillary links Mauro Carvalho Chehab
2021-12-15 9:36 ` Daniel Scally
2021-12-15 9:52 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e6d79347-0fc7-9e94-f968-e630ac87d451@gmail.com \
--to=djrscally@gmail.com \
--cc=hanlinchen@chromium.org \
--cc=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=libcamera-devel@lists.libcamera.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox