[PATCH v2 2/5] gpu: ipu-v3: Add mem2mem image conversion support to IC
On Thu, May 28, 2015 at 07:38:20PM +0200, Enrico Weigelt, metux IT consult wrote: > Thx. already integrated it into my tree - works fine :) > > By the way: i still have some your older patches (2012) in my tree, > eg. some mediabus, camara, display timing stuff, etc ... not sure > whether I really need them for my device. > > Should I post them to linux-media list for review? No. That's all old stuff and has developed quite a lot since then. We'll post new series here on the lists when they are ready for mainline. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
[PATCH RFC 26/46] drivers/base: provide an infrastructure for componentised subsystems
On Fri, Jan 10, 2014 at 11:23:37PM +, Russell King - ARM Linux wrote:
> We do this in DT by providing a "superdevice" node which specifies
> the components, eg:
>
> imx-drm {
> compatible = "fsl,drm";
> crtcs = <&ipu1>;
> connectors = <&hdmi>;
> };
Saschas comment from 20140109074030.GN6750 at pengutronix.de isn't
addressed yet:
Sascha Hauer wrote:
> Can we have an example with a different number of
> encoders/connectors/crtcs, like:
>
> exynos-drm {
> compatible = "exynos,drm";
> crtcs = <&fimd1>;
> encoders = <&dp1>, <&hdmi1>, <&lvds1>;
> connectors = <&ptn3460>, <&hdmi1>;
> };
>
> Otherwise I get the impression that there is some topology of the
> components or at least relationship between the components encoded
> into the binding.
If I remember correctly, Sascha+Philipp+Lucas still had issues with the
bindings, but I'm not sure if they have been already addressed.
It's no good timing to finalize this during the weekend, where most
people are not in the office :)
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0|
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
[PATCH RFC 26/46] drivers/base: provide an infrastructure for componentised subsystems
On Fri, Jan 10, 2014 at 07:35:30AM -0800, Greg Kroah-Hartman wrote: > > I'll sort out a new set of patches today, along with a branch to pull if > > you wish to take them that way. > > It's too late for 3.14, as my tree is now closed for that because 3.13 > should be out this weekend. But I'll be glad to queue them up after > 3.14-rc1 is out. Didnt' Linus say there would be an -rc8? However - there is a devicetree issue to be discussed anyway (see Sascha's comment). Although we'd personally like to see this series being merged sooner than later, it should be sorted out first. Devicetree issues are ugly to change once they are in mainline. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
CDF discussions at FOSDEM
On Fri, Jan 11, 2013 at 09:27:03PM +0100, Laurent Pinchart wrote: > Would anyone be interested in meeting at the FOSDEM to discuss the Common > Display Framework ? There will be a CDF meeting at the ELC at the end of > February, the FOSDEM would be a good venue for European developers. We are interested as well (Philipp, Michael, Sascha, me, maybe also some of the others from the Pengutronix crew...). rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
Re: CDF discussions at FOSDEM
On Fri, Jan 11, 2013 at 09:27:03PM +0100, Laurent Pinchart wrote: > Would anyone be interested in meeting at the FOSDEM to discuss the Common > Display Framework ? There will be a CDF meeting at the ELC at the end of > February, the FOSDEM would be a good venue for European developers. We are interested as well (Philipp, Michael, Sascha, me, maybe also some of the others from the Pengutronix crew...). rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH v12 0/6] of: add display helper
On Tue, Nov 20, 2012 at 05:13:19PM +0100, Laurent Pinchart wrote: > On Tuesday 20 November 2012 16:54:50 Steffen Trumtrar wrote: > > Hi! > > > > Changes since v11: > > - make pointers const where applicable > > - add reviewed-by Laurent Pinchart > > Looks good to me. > > Acked-by: Laurent Pinchart > > Through which tree do you plan to push this ? We have no idea yet, and none of the people on Cc: have volunteered so far... what do you think? rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
Re: [PATCH v12 0/6] of: add display helper
On Tue, Nov 20, 2012 at 05:13:19PM +0100, Laurent Pinchart wrote: > On Tuesday 20 November 2012 16:54:50 Steffen Trumtrar wrote: > > Hi! > > > > Changes since v11: > > - make pointers const where applicable > > - add reviewed-by Laurent Pinchart > > Looks good to me. > > Acked-by: Laurent Pinchart > > Through which tree do you plan to push this ? We have no idea yet, and none of the people on Cc: have volunteered so far... what do you think? rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH 1/2 v6] of: add helper to parse display timings
On Thu, Oct 04, 2012 at 11:35:35PM +0200, Guennadi Liakhovetski wrote: > > +optional properties: > > + - hsync-active-high (bool): Hsync pulse is active high > > + - vsync-active-high (bool): Vsync pulse is active high > > For the above two we also considered using bool properties but eventually > settled down with integer ones: > > - hsync-active = <1> > > for active-high and 0 for active low. This has the added advantage of > being able to omit this property in the .dts, which then doesn't mean, > that the polarity is active low, but rather, that the hsync line is not > used on this hardware. So, maybe it would be good to use the same binding > here too? Philipp, this is the same argumentation as we discussed yesterday for the dual-link LVDS option, so that one could be modelled in a similar way. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
No subject
, pza Bcc: Subject: Re: [PATCH 1/2 v6] of: add helper to parse display timings Reply-To: In-Reply-To: X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-IRC: #ptxdist @freenode X-Accept-Language: de,en X-Accept-Content-Type: text/plain X-Uptime: 09:13:09 up 103 days, 22:24, 36 users, load average: 0,57, 0,60, 0,61 On Thu, Oct 04, 2012 at 11:35:35PM +0200, Guennadi Liakhovetski wrote: > > +optional properties: > > + - hsync-active-high (bool): Hsync pulse is active high > > + - vsync-active-high (bool): Vsync pulse is active high > > For the above two we also considered using bool properties but eventually > settled down with integer ones: > > - hsync-active = <1> > > for active-high and 0 for active low. This has the added advantage of > being able to omit this property in the .dts, which then doesn't mean, > that the polarity is active low, but rather, that the hsync line is not > used on this hardware. So, maybe it would be good to use the same binding > here too? Philipp, this is the same argumentation as we discussed yesterday for the dual-link LVDS option, so that one could be modelled in a similar way. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
Re: [PATCH 1/2 v6] of: add helper to parse display timings
On Thu, Oct 04, 2012 at 11:35:35PM +0200, Guennadi Liakhovetski wrote: > > +optional properties: > > + - hsync-active-high (bool): Hsync pulse is active high > > + - vsync-active-high (bool): Vsync pulse is active high > > For the above two we also considered using bool properties but eventually > settled down with integer ones: > > - hsync-active = <1> > > for active-high and 0 for active low. This has the added advantage of > being able to omit this property in the .dts, which then doesn't mean, > that the polarity is active low, but rather, that the hsync line is not > used on this hardware. So, maybe it would be good to use the same binding > here too? Philipp, this is the same argumentation as we discussed yesterday for the dual-link LVDS option, so that one could be modelled in a similar way. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[no subject]
, pza Bcc: Subject: Re: [PATCH 1/2 v6] of: add helper to parse display timings Reply-To: In-Reply-To: X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-IRC: #ptxdist @freenode X-Accept-Language: de,en X-Accept-Content-Type: text/plain X-Uptime: 09:13:09 up 103 days, 22:24, 36 users, load average: 0,57, 0,60, 0,61 On Thu, Oct 04, 2012 at 11:35:35PM +0200, Guennadi Liakhovetski wrote: > > +optional properties: > > + - hsync-active-high (bool): Hsync pulse is active high > > + - vsync-active-high (bool): Vsync pulse is active high > > For the above two we also considered using bool properties but eventually > settled down with integer ones: > > - hsync-active = <1> > > for active-high and 0 for active low. This has the added advantage of > being able to omit this property in the .dts, which then doesn't mean, > that the polarity is active low, but rather, that the hsync line is not > used on this hardware. So, maybe it would be good to use the same binding > here too? Philipp, this is the same argumentation as we discussed yesterday for the dual-link LVDS option, so that one could be modelled in a similar way. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[RFC 1/5] video: Add generic display panel core
On Thu, Sep 13, 2012 at 01:29:54PM +0200, Sascha Hauer wrote: > > > You have seen my of videomode helper proposal. One result there > > > was that we want to have ranges for the margin/synclen fields. > > > Does it make sense to base this new panel framework on a more > > > sophisticated internal reprentation of the panel parameters? > > > > I think it does, yes. We need a common video mode structure, and the > > panel framework should use it. I'll try to rebase my patches on top > > of your proposal. Have you posted the latest version ? > > V2 is the newest version. I'd like to implement ranges for the display > timings which then makes for a new common video mode structure, which > then could be used by drm and fbdev, probably with helper functions to > convert from common videomode to drm/fbdev specific variants. Steffen has a reworked series with the latest changes and will post them soon. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- |
Re: [RFC 1/5] video: Add generic display panel core
On Thu, Sep 13, 2012 at 01:29:54PM +0200, Sascha Hauer wrote: > > > You have seen my of videomode helper proposal. One result there > > > was that we want to have ranges for the margin/synclen fields. > > > Does it make sense to base this new panel framework on a more > > > sophisticated internal reprentation of the panel parameters? > > > > I think it does, yes. We need a common video mode structure, and the > > panel framework should use it. I'll try to rebase my patches on top > > of your proposal. Have you posted the latest version ? > > V2 is the newest version. I'd like to implement ranges for the display > timings which then makes for a new common video mode structure, which > then could be used by drm and fbdev, probably with helper functions to > convert from common videomode to drm/fbdev specific variants. Steffen has a reworked series with the latest changes and will post them soon. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
