From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAPDSS: VENC: allow switching venc type at runtime
Date: Fri, 20 Apr 2012 08:38:57 +0000 [thread overview]
Message-ID: <1334911137.2058.8.camel@deskari> (raw)
In-Reply-To: <1332978312-11959-1-git-send-email-notasas@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
On Thu, 2012-03-29 at 02:45 +0300, Grazvydas Ignotas wrote:
> VENC type (composite/svideo) doesn't have to be fixed by board wiring,
> it is possible to provide both connectors, which is what pandora does.
> Having to recompile the kernel for users who have TV connector types
> that's don't match default board setting is very inconvenient, especially
You don't have to recompile the kernel, you could just set the venc type
in the board file depending on a boot parameter.
> for users of a consumer device, so add support for switching VENC type
> at runtime over a new sysfs file venc_type.
I really dislike adding new custom sysfs entries for omapdss, and I'd
like to avoid them if at all possible. Do you need to change the venc
type during runtime, or is it enough that it can be set during boot?
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-20 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 23:45 [PATCH] OMAPDSS: VENC: allow switching venc type at runtime Grazvydas Ignotas
2012-04-20 8:38 ` Tomi Valkeinen [this message]
2012-04-20 10:49 ` Grazvydas Ignotas
2012-04-20 11:34 ` Tomi Valkeinen
2012-04-23 12:23 ` Tomi Valkeinen
2012-04-23 15:32 ` Grazvydas Ignotas
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=1334911137.2058.8.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.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).