linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Longerbeam <steve_longerbeam@mentor.com>
To: Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>,
	Steve Longerbeam <slongerbeam@gmail.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
	Tim Harvey <tharvey@gateworks.com>,
	Robert Schwebel <r.schwebel@pengutronix.de>,
	<linux-media@vger.kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: i.MX6 status for IPU/VPU/GPU
Date: Sun, 5 Oct 2014 18:03:03 -0700	[thread overview]
Message-ID: <5431EA47.4050507@mentor.com> (raw)
In-Reply-To: <CAL8zT=g6CXmLiW6VZwMFVDjKC8FtoPMPDPg7S37Czev+8YO+PA@mail.gmail.com>

On 10/02/2014 07:50 AM, Jean-Michel Hautbois wrote:
> Hi Steve,
> 
> 2014-09-09 18:28 GMT+02:00 Steve Longerbeam <slongerbeam@gmail.com>:
>> On 09/09/2014 12:49 AM, Jean-Michel Hautbois wrote:
>>> 2014-08-27 16:23 GMT+02:00 Steve Longerbeam <steve_longerbeam@mentor.com>:
>>>
>>>> The complete driver I posted to the list does have some minor issues
>>>> mostly suggested by Hans Verkuil (switch to new selection API instead
>>>> of cropping API for example). It is a full featured driver but it does not
>>>> implement the media device framework, i.e. user does not have direct
>>>> control of the video pipeline, rather the driver chooses the pipeline based
>>>> on the traditional inputs from user (video format and controls).
> 
> Here is my first step toward MC support from your work :
> https://github.com/Vodalys/linux-2.6-imx/commit/8f0318f53c48a9638a1963b395bc79fbd7ba4c07
> 
> This is a WIP, so some parts of code are commented out awaiting a
> nicer solution.
> I also keep using your eplist array for the moment, and open will
> obviously fail when trying to power sensor.
> But what I wanted was a complete MC support with parsing links from DT
> and I used Laurent's work intensively :).

Hi Jean-Michel,

Ok thanks for the work, I will try to find time to study it.


> 
>>>> I've also worked out what I think is a workable video pipeline graph for i.MX,
>>>> suitable for defining the entities, pads, and links. Unfortunately I haven't
>>>> been able to spend as much time as I'd like on it.
> 
> Did you find some time to write the pdf you mentioned ?

Finally did. I will send it directly to you, as I'm sure it will get
stripped here.

Steve

      parent reply	other threads:[~2014-10-06  1:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28 16:24 i.MX6 status for IPU/VPU/GPU Jean-Michel Hautbois
2014-07-28 18:59 ` Robert Schwebel
2014-07-28 21:15   ` Steve Longerbeam
2014-08-04  6:14     ` Tim Harvey
2014-08-04 11:54       ` Philipp Zabel
2014-08-05  8:07         ` Jean-Michel Hautbois
2014-08-27  7:13         ` Jean-Michel Hautbois
2014-08-27 14:23           ` Steve Longerbeam
2014-09-09  7:49             ` Jean-Michel Hautbois
2014-09-09  7:52               ` Hans Verkuil
2014-09-09 16:06                 ` Steve Longerbeam
2014-09-09 16:12               ` Steve Longerbeam
2014-09-09 17:40                 ` Philipp Zabel
2014-09-11  1:17                   ` Steve Longerbeam
2014-09-11 13:26                     ` Philipp Zabel
2014-09-15 14:13                       ` Jean-Michel Hautbois
2014-10-24 13:42                         ` Jean-Michel Hautbois
2015-01-27 15:00                           ` Carlos Sanmartín Bustos
2014-09-09 16:28               ` Steve Longerbeam
2014-09-10 16:08                 ` Jean-Michel Hautbois
2014-09-10 16:25                   ` Steve Longerbeam
2014-09-11  0:37                     ` Steve Longerbeam
2014-10-02 14:50                 ` Jean-Michel Hautbois
2014-10-03 10:25                   ` Carlos Sanmartín Bustos
     [not found]                   ` <CAPW4HR0BJ7X0sMy78keEFtS6WXpbJjYCo75utKqWBtsDvrbUeg@mail.gmail.com>
2014-10-03 10:27                     ` Jean-Michel Hautbois
2014-10-06  1:03                   ` Steve Longerbeam [this message]

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=5431EA47.4050507@mentor.com \
    --to=steve_longerbeam@mentor.com \
    --cc=jean-michel.hautbois@vodalys.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=r.schwebel@pengutronix.de \
    --cc=slongerbeam@gmail.com \
    --cc=tharvey@gateworks.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).