Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752710AbdGFNXT convert rfc822-to-8bit (ORCPT ); Thu, 6 Jul 2017 09:23:19 -0400 Received: from mailapp01.imgtec.com ([195.59.15.196]:27521 "EHLO mailapp01.imgtec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751952AbdGFNXR (ORCPT ); Thu, 6 Jul 2017 09:23:17 -0400 From: Miodrag Dinic To: Rob Herring , Aleksandar Markovic CC: Linux-MIPS , Aleksandar Markovic , Goran Ferenc , "devicetree@vger.kernel.org" , Douglas Leung , James Hogan , "linux-kernel@vger.kernel.org" , Mark Rutland , Paul Burton , Petar Jovanovic , Raghu Gandham , "jinqian@google.com" , "lfy@google.com" , Bo Hu , "arve@android.com" Subject: RE: [PATCH v2 06/10] Documentation: Add device tree binding for Goldfish FB driver Thread-Topic: [PATCH v2 06/10] Documentation: Add device tree binding for Goldfish FB driver Thread-Index: AQHS8CaWT/npMCJNDUyBQ7ycfQt1mqI873QAgAC3epg= Date: Thu, 6 Jul 2017 13:23:10 +0000 Message-ID: <232DDC0A2B605E4F9E85F6904417885F015D929D32@BADAG02.ba.imgtec.org> References: <1498664922-28493-1-git-send-email-aleksandar.markovic@rt-rk.com> <1498664922-28493-7-git-send-email-aleksandar.markovic@rt-rk.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [82.117.201.26] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2357 Lines: 56 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@kernel.org] Sent: Friday, June 30, 2017 1:12 AM To: Aleksandar Markovic Cc: Linux-MIPS; Aleksandar Markovic; Miodrag Dinic; Goran Ferenc; devicetree@vger.kernel.org; Douglas Leung; James Hogan; linux-kernel@vger.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 wrote: > From: Aleksandar Markovic > > 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 > Signed-off-by: Goran Ferenc > Signed-off-by: Aleksandar Markovic > --- > .../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