From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-media <linux-media@vger.kernel.org>,
Andrzej Hajda <a.hajda@samsung.com>
Subject: Re: Samsung i2c subdev drivers that set sd->name
Date: Thu, 11 Jul 2013 01:28:47 +0200 [thread overview]
Message-ID: <1480951.mKR9bzbARV@avalon> (raw)
In-Reply-To: <51DDDDF7.1010005@iki.fi>
Hi Sakari,
On Thursday 11 July 2013 01:19:35 Sakari Ailus wrote:
> Hi Sylwester and Laurent,
>
> Sylwester Nawrocki wrote:
> > Hi Laurent,
>
> ...
>
> >> We need an ioctl to report additional information about media entities
> >> (it's been on my to-do list for wayyyyyyyyy too long). It could be used
> >> to report bus information as well.
> >
> > Yes, that sounds much more interesting than using just subdev name to
> > sqeeze all the information in. Why we don't have such an ioctl yet anyway
> > ? Were there some arguments against it, or its been just a low priority
> > issue ?
>
> I think it's just been left unaddressed until now since there have been
> even more important things to work on. :-) I'm all for that, btw.;
> associating bus information to the media device instead of entities was
> always a little odd (feel free to blame me, too...).
>
> Perhaps we could steal some bytes from the union in struct
> media_entity_desc? :-)
I've thought about that as well, but we will eventually need to pass more
entity information to userspace, so a new ioctl would in my opinion be better,
given the potentially large size of the bus information string.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-07-10 23:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 8:54 Samsung i2c subdev drivers that set sd->name Hans Verkuil
2013-06-25 16:55 ` Sylwester Nawrocki
2013-06-26 9:00 ` Sakari Ailus
2013-06-27 6:43 ` Hans Verkuil
2013-06-27 9:53 ` Sylwester Nawrocki
2013-07-03 22:49 ` Laurent Pinchart
2013-07-04 11:13 ` Hans Verkuil
2013-07-04 20:19 ` Sylwester Nawrocki
2013-07-05 11:30 ` Laurent Pinchart
2013-07-06 20:50 ` Sylwester Nawrocki
2013-07-10 22:19 ` Sakari Ailus
2013-07-10 23:28 ` Laurent Pinchart [this message]
2013-07-10 23:27 ` Laurent Pinchart
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=1480951.mKR9bzbARV@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
--cc=sylvester.nawrocki@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