linux-kernel - RE: [PATCH v2 06/10] Documentation: Add device tree binding for Goldfish FB driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 6 Jul 2017 13:23:10 +0000
From:   Miodrag Dinic <Miodrag.Dinic@...tec.com>
To:     Rob Herring <robh+dt@...nel.org>,
        Aleksandar Markovic <aleksandar.markovic@...rk.com>
CC:     Linux-MIPS <linux-mips@...ux-mips.org>,
        Aleksandar Markovic <Aleksandar.Markovic@...tec.com>,
        Goran Ferenc <Goran.Ferenc@...tec.com>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        Douglas Leung <Douglas.Leung@...tec.com>,
        James Hogan <James.Hogan@...tec.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Mark Rutland <mark.rutland@....com>,
        Paul Burton <Paul.Burton@...tec.com>,
        Petar Jovanovic <Petar.Jovanovic@...tec.com>,
        Raghu Gandham <Raghu.Gandham@...tec.com>,
        "jinqian@...gle.com" <jinqian@...gle.com>,
        "lfy@...gle.com" <lfy@...gle.com>, Bo Hu <bohu@...gle.com>,
        "arve@...roid.com" <arve@...roid.com>
Subject: RE: [PATCH v2 06/10] Documentation: Add device tree binding for
 Goldfish FB driver

cc-ing Arve Hjønnevåg who originally upstreamed Goldfish FB driver
cc-ing Jin Quian, Bo Hu & Lingfeng Yang from Google

Hi Rob,

Thanks for taking the time to review the patches

> I don't know that this should even go upstream. There's no upstream
> qemu support for goldfish-fb. Maybe this is a minor driver change, but
> FB drivers are being replaced with DRM drivers. And the time for AOSP
> supporting framebuffer drivers is limited I think with HWC2 and
> explicit fence support in DRM.

Goldfish FB is actively used by all supported architectures in Android (Intel/ARM/MIPS)
and is part of Android emulator project and so far, there have been no limitations in
AOSP for using it.

We have already tested this particular version of the driver for MIPS
Ranchu virtual platform (introduced in this series) which is DT based and
therefore we needed to integrate device tree support for this driver.

> bindings/display/

Did you mean to use this location instead of "bindings/goldfish/"?

Kind regards,
Miodrag
________________________________________
From: Rob Herring [robh+dt@...nel.org]
Sent: Friday, June 30, 2017 1:12 AM
To: Aleksandar Markovic
Cc: Linux-MIPS; Aleksandar Markovic; Miodrag Dinic; Goran Ferenc; devicetree@...r.kernel.org; Douglas Leung; James Hogan; linux-kernel@...r.kernel.org; Mark Rutland; Paul Burton; Petar Jovanovic; Raghu Gandham
Subject: Re: [PATCH v2 06/10] Documentation: Add device tree binding for Goldfish FB driver

On Wed, Jun 28, 2017 at 10:46 AM, Aleksandar Markovic
<aleksandar.markovic@...rk.com> wrote:
> From: Aleksandar Markovic <aleksandar.markovic@...tec.com>
>
> Add documentation for DT binding of Goldfish FB driver. The compatible
> string used by OS for binding the driver is "google,goldfish-fb".
>
> Signed-off-by: Miodrag Dinic <miodrag.dinic@...tec.com>
> Signed-off-by: Goran Ferenc <goran.ferenc@...tec.com>
> Signed-off-by: Aleksandar Markovic <aleksandar.markovic@...tec.com>
> ---
>  .../bindings/goldfish/google,goldfish-fb.txt           | 18 ++++++++++++++++++

bindings/display/

I don't know that this should even go upstream. There's no upstream
qemu support for goldfish-fb. Maybe this is a minor driver change, but
FB drivers are being replaced with DRM drivers. And the time for AOSP
supporting framebuffer drivers is limited I think with HWC2 and
explicit fence support in DRM.

Rob