From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: KS2012 <ksummit-2012-discuss@lists.linux-foundation.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Media system Summit
Date: Thu, 12 Jul 2012 10:08:04 +0200 [thread overview]
Message-ID: <4FFE85E4.7030609@gmail.com> (raw)
In-Reply-To: <4FFE41F0.4010602@redhat.com>
Hi Mauro,
On 07/12/2012 05:18 AM, Mauro Carvalho Chehab wrote:
> Em 11-07-2012 05:09, James Bottomley escreveu:
>> Hi All,
>>
>> We have set aside the second day of the kernel summit (Tuesday 28
>> August) as mini-summit day. So far we have only the PCI mini summit on
>> this day
>
> Not sure what happened (or maybe my proposal were not clear enough), but
> I've submitted a proposal to have a media system summit on KS/2011.
> Last year was very productive for media developers, so we'd like to do
> it again ;)
>
>
> Message-ID:<4FEC74AB.6070501@redhat.com>
> Date: Thu, 28 Jun 2012 12:13:47 -0300
> From: Mauro Carvalho Chehab<mchehab@redhat.com>
>
> [Ksummit-2012-discuss] [ATTEND] media subsystem
>
> I'd like to have media subsystem discussions this year's at kernel summit.
> The media subsystem is one of the most active driver subsystem, and there are lots of
> things there that require face-to-face discussions, not only between subsystem developers,
> but also with other maintainers. In special, during KS/2011, it was identified the need
> of interacting with video and audio system people, in order to solve some common issues,
> like HDMI CEC and audio/video synchronization.
>
> The increasing complexity of SoC designs used by media devices requires API
> extensions at the media APIs in order to proper expose and control all hardware
> functionality on a standard way. A new API to better allow negotiating userspace
> and Kernelspace capabilities seem to be required.
>
> More discussions with regards to shared resources locking is needed, on devices that
> implement multiple API's, but not a the same time.
>
> The incompatibility between udev-182 and the existing drivers will also require lots
> of discussions, as that affects 64 media drivers, and changing them to comply with
> the current requirement of using request_firmware_nowait() won't work on several
> drivers. So, a solution (or a set of solutions) needs to be found, in order to fix
> such incompatibility.
I'd like to add a "Common device tree bindings for media devices" topic to
the agenda for consideration.
There were some activities on creating device tree bindings for Samsung and
SH Mobile SoCs but this didn't really kick off yet and a face to face discussions
could help to bring device tree support in media subsystem to the level many
other subsystems already have.
--
Thanks,
Sylwester
next prev parent reply other threads:[~2012-07-12 8:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1341994155.3522.16.camel@dabdike.int.hansenpartnership.com>
2012-07-12 3:18 ` Media system Summit Mauro Carvalho Chehab
2012-07-12 8:08 ` Sylwester Nawrocki [this message]
2012-07-12 16:18 ` [Ksummit-2012-discuss] " Mark Brown
2012-07-12 16:48 ` Olof Johansson
2012-07-12 17:09 ` Mark Brown
2012-07-12 19:03 ` Hans Verkuil
2012-07-12 21:05 ` Guennadi Liakhovetski
2012-07-13 1:28 ` Olof Johansson
2012-07-21 8:50 ` Rémi Denis-Courmont
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=4FFE85E4.7030609@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=ksummit-2012-discuss@lists.linux-foundation.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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).