From: Helen Koike <helen.koike@collabora.co.uk>
To: linux-media@vger.kernel.org
Subject: [GIT PULL] two patches: pipeline validation error code
Date: Wed, 27 Apr 2016 15:01:31 -0300 [thread overview]
Message-ID: <5720FE7B.6000002@collabora.co.uk> (raw)
Hi Mauro,
Please pull the following patches correcting the returned error codes
and respective docs in the pipeline validation.
Regards,
Helen
The following changes since commit 45c175c4ae9695d6d2f30a45ab7f3866cfac184b:
[media] tw686x: avoid going past array (2016-04-26 06:38:53 -0300)
are available in the git repository at:
https://github.com/helen-fornazier/opw-staging.git media/devel
for you to fetch changes up to 957f69645eae5faae6daa205e85471ef82752abc:
[media] DocBook: update error code in videoc-streamon (2016-04-27
14:14:11 -0300)
----------------------------------------------------------------
Helen Mae Koike Fornazier (2):
[media] media: change pipeline validation return error
[media] DocBook: update error code in videoc-streamon
Documentation/DocBook/media/v4l/vidioc-streamon.xml | 8 ++++++++
drivers/media/media-entity.c | 2 +-
drivers/media/v4l2-core/v4l2-subdev.c | 4 ++--
3 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/Documentation/DocBook/media/v4l/vidioc-streamon.xml
b/Documentation/DocBook/media/v4l/vidioc-streamon.xml
index df2c63d..89fd7ce 100644
--- a/Documentation/DocBook/media/v4l/vidioc-streamon.xml
+++ b/Documentation/DocBook/media/v4l/vidioc-streamon.xml
@@ -123,6 +123,14 @@ synchronize with other events.</para>
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><errorcode>ENOLINK</errorcode></term>
+ <listitem>
+ <para>The driver implements Media Controller interface and
+ the pipeline link configuration is invalid.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
</refsect1>
</refentry>
diff --git a/drivers/media/media-entity.c b/drivers/media/media-entity.c
index c53c1d5..d8a2299 100644
--- a/drivers/media/media-entity.c
+++ b/drivers/media/media-entity.c
@@ -445,7 +445,7 @@ __must_check int
__media_entity_pipeline_start(struct media_entity *entity,
bitmap_or(active, active, has_no_links, entity->num_pads);
if (!bitmap_full(active, entity->num_pads)) {
- ret = -EPIPE;
+ ret = -ENOLINK;
dev_dbg(entity->graph_obj.mdev->dev,
"\"%s\":%u must be connected by an enabled link\n",
entity->name,
diff --git a/drivers/media/v4l2-core/v4l2-subdev.c
b/drivers/media/v4l2-core/v4l2-subdev.c
index 224ea60..953eab0 100644
--- a/drivers/media/v4l2-core/v4l2-subdev.c
+++ b/drivers/media/v4l2-core/v4l2-subdev.c
@@ -510,7 +510,7 @@ int v4l2_subdev_link_validate_default(struct
v4l2_subdev *sd,
if (source_fmt->format.width != sink_fmt->format.width
|| source_fmt->format.height != sink_fmt->format.height
|| source_fmt->format.code != sink_fmt->format.code)
- return -EINVAL;
+ return -EPIPE;
/* The field order must match, or the sink field order must be NONE
* to support interlaced hardware connected to bridges that support
@@ -518,7 +518,7 @@ int v4l2_subdev_link_validate_default(struct
v4l2_subdev *sd,
*/
if (source_fmt->format.field != sink_fmt->format.field &&
sink_fmt->format.field != V4L2_FIELD_NONE)
- return -EINVAL;
+ return -EPIPE;
return 0;
}
next reply other threads:[~2016-04-27 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 18:01 Helen Koike [this message]
2016-04-29 11:14 ` [GIT PULL] two patches: pipeline validation error code Mauro Carvalho Chehab
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=5720FE7B.6000002@collabora.co.uk \
--to=helen.koike@collabora.co.uk \
--cc=linux-media@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.