From: Michal Simek <michal.simek@xilinx.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
Michal Simek <michal.simek@xilinx.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"monstr@monstr.eu" <monstr@monstr.eu>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Paul Burton <paul.burton@imgtec.com>
Subject: Re: [PATCH 2/2] video: fbdev: Enable Xilinx FB for ZynqMP
Date: Mon, 14 Aug 2017 13:50:56 +0000 [thread overview]
Message-ID: <994f5b9f-9ba7-ad80-84c4-de1edd9e56d0@xilinx.com> (raw)
In-Reply-To: <CAKMK7uEKQMRFGdGqrPo-i0Z9ht6-zC6G8hsVW7FKr9cxbpwuPQ@mail.gmail.com>
On 14.8.2017 15:49, Daniel Vetter wrote:
> On Mon, Aug 14, 2017 at 3:46 PM, Michal Simek <michal.simek@xilinx.com> wrote:
>> On 14.8.2017 15:42, Linus Walleij wrote:
>>> On Tue, Aug 8, 2017 at 10:10 AM, Michal Simek <michal.simek@xilinx.com> wrote:
>>>
>>>> Enable this driver for Xilinx ZynqMP.
>>>>
>>>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>>>
>>> Not a comment on the patch per se, but I would advice you to look into
>>> migrating the Xilinx frame buffer to DRI/DRM/KMS.
>>>
>>> The recent CMA helpers has made it very simple and focused to write
>>> DRM drivers. See for example drivers/gpu/drm/pl111
>>
>> There is a lot of work done by xilinx in this area gpu/drm/kms. I am
>> trying to upstream what xilinx has in soc tree and this change is there.
>> Maybe in this case it is useless and none is using it but it is there
>> and I don't want to break user. There shouldn't be any technical problem
>> to run this old fb driver in pl on arm64.
>
> A proper drm kms driver gives you backwards compat for fbdev for free.
> And we're taking in patches to fill feature gaps in our fbdev
> emulation as people hit them. There no reason nowadays at all to merge
> new fbdev native drivers, your users will be taken care of by a drm
> kms driver fully.
You can look at xilinx work in this area.
https://github.com/Xilinx/linux-xlnx
Unfortunately they haven't started to upstream it.
In this particular case I am not aware about anybody who is going to
write new driver for this soft IP.
Thanks,
Michal
next prev parent reply other threads:[~2017-08-14 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170808081042epcas4p3b6787c3895bec41cb37aa4ae868adb45@epcas4p3.samsung.com>
2017-08-08 8:10 ` [PATCH 1/2] video: fbdev: Fix multiple style issues in xilinxfb Michal Simek
2017-08-08 8:10 ` [PATCH 2/2] video: fbdev: Enable Xilinx FB for ZynqMP Michal Simek
2017-08-14 13:42 ` Linus Walleij
2017-08-14 13:46 ` Michal Simek
2017-08-14 13:49 ` Daniel Vetter
2017-08-14 13:50 ` Michal Simek [this message]
2017-08-21 14:07 ` Bartlomiej Zolnierkiewicz
2017-08-21 14:04 ` [PATCH 1/2] video: fbdev: Fix multiple style issues in xilinxfb Bartlomiej Zolnierkiewicz
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=994f5b9f-9ba7-ad80-84c4-de1edd9e56d0@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=benjamin.gaignard@linaro.org \
--cc=daniel.vetter@ffwll.ch \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=paul.burton@imgtec.com \
--cc=tomi.valkeinen@ti.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).