From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>,
Sakari Ailus <sakari.ailus@iki.fi>,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
dri-devel@lists.freedesktop.org,
linux-samsung-soc@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Sakari Ailus <sakari.ailus@intel.com>,
linux-media@vger.kernel.org
Subject: Re: [RFC 0/4] Exynos DRM: add Picture Processor extension
Date: Wed, 26 Apr 2017 15:36:04 -0400 [thread overview]
Message-ID: <1493235364.29587.17.camel@ndufresne.ca> (raw)
In-Reply-To: <d9087a2a-ec14-ef93-9961-30d166d24994@math.uni-bielefeld.de>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
Le mercredi 26 avril 2017 à 21:31 +0200, Tobias Jakobi a écrit :
> I'm pretty sure you have misread Marek's description of the patchset.
> The picture processor API should replaced/deprecate the IPP API that is
> currently implemented in the Exynos DRM.
>
> In particular this affects the following files:
> - drivers/gpu/drm/exynos/exynos_drm_ipp.{c,h}
> - drivers/gpu/drm/exynos/exynos_drm_fimc.{c,h}
> - drivers/gpu/drm/exynos/exynos_drm_gsc.{c,h}
> - drivers/gpu/drm/exynos/exynos_drm_rotator.{c,h}
>
> I know only two places where the IPP API is actually used. Tizen and my
> experimental mpv backend.
Sorry for the noise then.
regards,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-04-26 19:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170420091406eucas1p24c50a0015545105081257d880727386c@eucas1p2.samsung.com>
[not found] ` <1492679620-12792-1-git-send-email-m.szyprowski@samsung.com>
[not found] ` <2541347.TzHdYYQVhG@avalon>
[not found] ` <711bf4a5-7e57-6720-d00b-66e97a81e5ec@samsung.com>
2017-04-25 22:21 ` [RFC 0/4] Exynos DRM: add Picture Processor extension Sakari Ailus
2017-04-26 14:53 ` Nicolas Dufresne
2017-04-26 15:16 ` Tobias Jakobi
2017-04-27 13:52 ` Marek Szyprowski
2017-04-26 16:52 ` Tobias Jakobi
2017-04-26 19:18 ` Nicolas Dufresne
2017-04-26 19:31 ` Tobias Jakobi
2017-04-26 19:36 ` Nicolas Dufresne [this message]
2017-04-27 13:52 ` Marek Szyprowski
2017-05-10 1:24 ` Inki Dae
2017-05-10 5:38 ` Tomasz Figa
2017-05-10 6:27 ` Inki Dae
2017-05-10 6:38 ` Tomasz Figa
2017-05-10 10:29 ` Inki Dae
2017-05-10 13:18 ` Daniel Vetter
2017-05-10 7:55 ` Daniel Vetter
2017-05-10 10:31 ` Inki Dae
2017-05-10 13:30 ` Marek Szyprowski
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=1493235364.29587.17.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@intel.com \
--cc=sw0312.kim@samsung.com \
--cc=tjakobi@math.uni-bielefeld.de \
/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