From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] media: davinci: vpif: display: separate out subdev from output
Date: Tue, 2 Oct 2012 14:18:59 +0530 [thread overview]
Message-ID: <506AAA7B.1020308@ti.com> (raw)
In-Reply-To: <1348571509-4131-1-git-send-email-prabhakar.lad@ti.com>
On 9/25/2012 4:41 PM, Prabhakar wrote:
> From: Lad, Prabhakar <prabhakar.lad@ti.com>
>
> vpif_display relied on a 1-1 mapping of output and subdev. This is not
> necessarily the case. Separate the two. So there is a list of subdevs
> and a list of outputs. Each output refers to a subdev and has routing
> information. An output does not have to have a subdev.
>
> The initial output for each channel is set to the fist output.
>
> Currently missing is support for associating multiple subdevs with
> an output.
>
> Signed-off-by: Lad, Prabhakar <prabhakar.lad@ti.com>
> Signed-off-by: Manjunath Hadli <manjunath.hadli@ti.com>
> Cc: Hans Verkuil <hans.verkuil@cisco.com>
> Cc: Sekhar Nori <nsekhar@ti.com>
For the DaVinci platform changes:
Acked-by: Sekhar Nori <nsekhar@ti.com>
Thanks,
Sekhar
WARNING: multiple messages have this Message-ID (diff)
From: Sekhar Nori <nsekhar@ti.com>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: LMML <linux-media@vger.kernel.org>,
DLOS <davinci-linux-open-source@linux.davincidsp.com>,
LAK <linux-arm-kernel@lists.infradead.org>,
Manjunath Hadli <manjunath.hadli@ti.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
VGER <linux-kernel@vger.kernel.org>,
"Lad, Prabhakar" <prabhakar.lad@ti.com>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH v3] media: davinci: vpif: display: separate out subdev from output
Date: Tue, 2 Oct 2012 14:18:59 +0530 [thread overview]
Message-ID: <506AAA7B.1020308@ti.com> (raw)
In-Reply-To: <1348571509-4131-1-git-send-email-prabhakar.lad@ti.com>
On 9/25/2012 4:41 PM, Prabhakar wrote:
> From: Lad, Prabhakar <prabhakar.lad@ti.com>
>
> vpif_display relied on a 1-1 mapping of output and subdev. This is not
> necessarily the case. Separate the two. So there is a list of subdevs
> and a list of outputs. Each output refers to a subdev and has routing
> information. An output does not have to have a subdev.
>
> The initial output for each channel is set to the fist output.
>
> Currently missing is support for associating multiple subdevs with
> an output.
>
> Signed-off-by: Lad, Prabhakar <prabhakar.lad@ti.com>
> Signed-off-by: Manjunath Hadli <manjunath.hadli@ti.com>
> Cc: Hans Verkuil <hans.verkuil@cisco.com>
> Cc: Sekhar Nori <nsekhar@ti.com>
For the DaVinci platform changes:
Acked-by: Sekhar Nori <nsekhar@ti.com>
Thanks,
Sekhar
next prev parent reply other threads:[~2012-10-02 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 11:11 [PATCH v3] media: davinci: vpif: display: separate out subdev from output Prabhakar
2012-09-25 11:11 ` Prabhakar
2012-09-25 11:39 ` Hans Verkuil
2012-09-25 11:39 ` Hans Verkuil
2012-10-02 8:48 ` Sekhar Nori [this message]
2012-10-02 8:48 ` Sekhar Nori
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=506AAA7B.1020308@ti.com \
--to=nsekhar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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.