linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-media@vger.kernel.org, kyungmin.park@samsung.com,
	s.nawrocki@samsung.com,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH/RFC 1/1] Add a libv4l plugin for Exynos4 camera
Date: Fri, 10 Oct 2014 10:07:21 +0200	[thread overview]
Message-ID: <543793B9.4020100@samsung.com> (raw)
In-Reply-To: <54364566.9030102@redhat.com>

Hi,

On 10/09/2014 10:20 AM, Hans de Goede wrote:
> Hi,
>
> On 10/08/2014 03:22 PM, Jacek Anaszewski wrote:
>> Hi Hans,
>>
>> On 10/08/2014 02:42 PM, Hans de Goede wrote:
>
> <snip>
>
>>>> +    }
>>>> +
>>>> +    /* refresh device topology data after linking */
>>>> +    release_entities(mdev);
>>>> +
>>>> +    ret = get_device_topology(mdev);
>>>> +
>>>> +    /* close media device fd as it won't be longer required */
>>>> +    close(mdev->media_fd);
>>>> +
>>>> +    if (ret < 0)
>>>> +        goto err_get_dev_topology;
>>>> +
>>>> +    /* discover a pipeline for the capture device */
>>>> +    ret = discover_pipeline_by_fd(mdev, fd);
>>>> +    if (ret < 0)
>>>> +        goto err_discover_pipeline;
>>>
>>> There does not seem to be any code here to ensure that this plugin does
>>> not bind to non exonys4 fimc devices. Please fix that.
>>
>> There is. Please look above at the
>>
>> "if (!capture_entity(media_entity_name))" condition above.
>
> I already checked that, that just checks for the string "capture", which is
> way too generic, please add a more narrow guard.

While making cleanup I mistakenly removed checking for the driver name
after QUERYCAP in the beginning of plugin_init. Will fix it in the next
version.

Regards,
Jacek

  reply	other threads:[~2014-10-10  8:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08  8:46 [PATCH/RFC 0/1] Libv4l: Add a plugin for the Exynos4 camera Jacek Anaszewski
2014-10-08  8:46 ` [PATCH/RFC 1/1] Add a libv4l plugin for " Jacek Anaszewski
2014-10-08 12:42   ` Hans de Goede
2014-10-08 13:22     ` Jacek Anaszewski
2014-10-08 15:49       ` Antonio Ospite
2014-10-09  7:51         ` Jacek Anaszewski
2014-10-09  8:20       ` Hans de Goede
2014-10-10  8:07         ` Jacek Anaszewski [this message]
2014-10-10  8:54   ` Hans Verkuil
2014-10-10 15:10     ` Jacek Anaszewski
2014-10-09 17:46 ` [PATCH/RFC 0/1] Libv4l: Add a plugin for the " Gregor Jasny
2014-10-10  8:14   ` Jacek Anaszewski

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=543793B9.4020100@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=hans.verkuil@cisco.com \
    --cc=hdegoede@redhat.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=s.nawrocki@samsung.com \
    /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;
as well as URLs for NNTP newsgroup(s).