From: Helen Koike <helen.koike@collabora.com> To: "André Almeida" <andrealmeid@collabora.com>, linux-media@vger.kernel.org Cc: mchehab@kernel.org, hverkuil@xs4all.nl, kernel@collabora.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 5/7] media: vimc: core: Add output device on the pipeline Date: Tue, 9 Jul 2019 19:20:51 -0300 [thread overview] Message-ID: <67dee9b6-cce4-0722-523c-d448913faeee@collabora.com> (raw) In-Reply-To: <20190702154752.14939-6-andrealmeid@collabora.com> On 7/2/19 12:47 PM, André Almeida wrote: > Add the output video device on the hardcoded pipeline. Change the link > to it be enabled by default. > > Signed-off-by: André Almeida <andrealmeid@collabora.com> > --- > drivers/media/platform/vimc/vimc-core.c | 7 +++---- > 1 file changed, 3 insertions(+), 4 deletions(-) > > diff --git a/drivers/media/platform/vimc/vimc-core.c b/drivers/media/platform/vimc/vimc-core.c > index 571c55aa0e16..ecdea1d631c5 100644 > --- a/drivers/media/platform/vimc/vimc-core.c > +++ b/drivers/media/platform/vimc/vimc-core.c > @@ -95,8 +95,7 @@ static const struct vimc_ent_config ent_config[] = { > }, > { > .name = "RGB/YUV Input", Could you also change the name here to Output? I think it makes more sense. Helen > - /* TODO: change this to vimc-input when it is implemented */ > - .drv = "vimc-sensor", > + .drv = "vimc-output", > }, > { > .name = "Scaler", > @@ -118,11 +117,11 @@ static const struct vimc_ent_link ent_links[] = { > /* Link: Sensor B (Pad 0)->(Pad 0) Raw Capture 1 */ > VIMC_ENT_LINK(1, 0, 5, 0, MEDIA_LNK_FL_ENABLED | MEDIA_LNK_FL_IMMUTABLE), > /* Link: Debayer A (Pad 1)->(Pad 0) Scaler */ > - VIMC_ENT_LINK(2, 1, 7, 0, MEDIA_LNK_FL_ENABLED), > + VIMC_ENT_LINK(2, 1, 7, 0, 0), > /* Link: Debayer B (Pad 1)->(Pad 0) Scaler */ > VIMC_ENT_LINK(3, 1, 7, 0, 0), > /* Link: RGB/YUV Input (Pad 0)->(Pad 0) Scaler */ > - VIMC_ENT_LINK(6, 0, 7, 0, 0), > + VIMC_ENT_LINK(6, 0, 7, 0, MEDIA_LNK_FL_ENABLED | MEDIA_LNK_FL_IMMUTABLE), > /* Link: Scaler (Pad 1)->(Pad 0) RGB/YUV Capture */ > VIMC_ENT_LINK(7, 1, 8, 0, MEDIA_LNK_FL_ENABLED | MEDIA_LNK_FL_IMMUTABLE), > }; >
next prev parent reply other threads:[~2019-07-09 22:21 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-02 15:47 [PATCH 0/7] media: vimc: Add a V4L2 output device André Almeida 2019-07-02 15:47 ` [PATCH 1/7] media: vimc: Create video module André Almeida 2019-07-02 15:47 ` [PATCH 2/7] media: vimc: video: Add write file operation André Almeida 2019-07-02 15:47 ` [PATCH 3/7] media: vimc: Create a V4L2 output device André Almeida 2019-07-09 22:20 ` Helen Koike 2019-07-02 15:47 ` [PATCH 4/7] media: vimc: Send null buffer through the pipeline André Almeida 2019-07-02 15:47 ` [PATCH 5/7] media: vimc: core: Add output device on " André Almeida 2019-07-09 22:20 ` Helen Koike [this message] 2019-07-02 15:47 ` [PATCH 6/7] media: vimc.dot: Update default topology diagram André Almeida 2019-07-02 15:47 ` [PATCH 7/7] media: vimc.rst: Add output device André Almeida 2019-07-09 22:19 ` [PATCH 0/7] media: vimc: Add a V4L2 " Helen Koike 2019-07-10 7:33 ` Hans Verkuil 2019-07-12 15:38 ` André Almeida 2019-07-13 10:03 ` Hans Verkuil 2019-07-31 3:00 ` André Almeida
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=67dee9b6-cce4-0722-523c-d448913faeee@collabora.com \ --to=helen.koike@collabora.com \ --cc=andrealmeid@collabora.com \ --cc=hverkuil@xs4all.nl \ --cc=kernel@collabora.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=mchehab@kernel.org \ --subject='Re: [PATCH 5/7] media: vimc: core: Add output device on the pipeline' \ /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
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).