From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, UNPARSEABLE_RELAY,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BB5B2C43387 for ; Fri, 11 Jan 2019 09:49:45 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 7A4E52177B for ; Fri, 11 Jan 2019 09:49:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="r89csVeW" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7A4E52177B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=mediatek.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Date:To:From:Subject:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=ByM6WTiajaTyaQL7fTt9Dz1IU/FWShfejsXK/dFmumQ=; b=r89csVeW1jcY+D LUOfmuPN2v8JVe0OXutg6idiOEa9Ny2F+EWSqvxJXjPomCmVTzWHDKu7IM13DY1TI1a8dIRt0o5Kd nkVj9n/IPuF4sUH1pqDVQfUTGVuiHH9oVN8M6rzYsaqTqQKTNMHPtGwBzVtzEjTbMyla/Uv22uiaf OytnHxWF2MX3X1F4DM/J4ywxI1RxcLj8yQY+ad+xrMPOb4UcyX3ZYNPovfNTMGJRg2KP995X1lEuG 6xfiDpLNZusUulZOR4YAB7kLR1gSJRwWFxeIvVWyIac7Omgd7Bd+zKAMdBkN357737cuxlYIwwQg6 EWWeNoMMaxjtKv1a+CXA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1ghtRd-0006oX-Aw; Fri, 11 Jan 2019 09:49:41 +0000 Received: from mailgw01.mediatek.com ([216.200.240.184]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1ghtRZ-0006nC-ET; Fri, 11 Jan 2019 09:49:39 +0000 X-UUID: e628fc54b4c74df0a0ebf7632edbd02a-20190111 X-UUID: e628fc54b4c74df0a0ebf7632edbd02a-20190111 Received: from mtkcas67.mediatek.inc [(172.29.193.45)] by mailgw01.mediatek.com (envelope-from ) (musrelay.mediatek.com ESMTP with TLS) with ESMTP id 373257772; Fri, 11 Jan 2019 01:49:18 -0800 Received: from MTKMBS06N1.mediatek.inc (172.21.101.129) by MTKMBS62DR.mediatek.inc (172.29.94.18) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 11 Jan 2019 01:49:17 -0800 Received: from mtkcas09.mediatek.inc (172.21.101.178) by mtkmbs06n1.mediatek.inc (172.21.101.129) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 11 Jan 2019 17:49:15 +0800 Received: from [172.21.77.4] (172.21.77.4) by mtkcas09.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Fri, 11 Jan 2019 17:49:15 +0800 Message-ID: <1547200155.4209.4.camel@mtksdaap41> Subject: Re: Re: [PATCH] drm/mediatek: Add MTK Framebuffer-Device (mt7623) From: CK Hu To: Daniel Vetter Date: Fri, 11 Jan 2019 17:49:15 +0800 In-Reply-To: <20190111092042.GP21184@phenom.ffwll.local> References: <20190102084917.4049-1-frank-w@public-files.de> <20190107103640.GH21184@phenom.ffwll.local> <20190110200225.GN21184@phenom.ffwll.local> <1547176809.12054.11.camel@mtksdaap41> <20190111092042.GP21184@phenom.ffwll.local> X-Mailer: Evolution 3.10.4-0ubuntu2 MIME-Version: 1.0 X-MTK: N X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190111_014937_488056_0C92CE44 X-CRM114-Status: GOOD ( 29.14 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Frank Wunderlich , David Airlie , Alexander Ryabchenko , Linux Kernel Mailing List , dri-devel , Noralf =?ISO-8859-1?Q?Tr=F8nnes?= , "moderated list:ARM/Mediatek SoC support" , Philipp Zabel , Matthias Brugger , Linux ARM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi, Daniel: On Fri, 2019-01-11 at 10:20 +0100, Daniel Vetter wrote: > On Fri, Jan 11, 2019 at 11:20:09AM +0800, CK Hu wrote: > > Hi, Daniel: > > > > On Thu, 2019-01-10 at 21:02 +0100, Daniel Vetter wrote: > > > On Thu, Jan 10, 2019 at 08:01:37PM +0100, Frank Wunderlich wrote: > > > > Hi Daniel, > > > > > > > > > > Would be good to use the new generic fbdev emulation code here, for even > > > > > > less code. Or at least know why this isn't possible to use for mtk (and > > > > > > maybe address that in the core code). Hand-rolling fbdev code shouldn't be > > > > > > needed anymore. > > > > > > > > > > Back on the mailing list, no private replies please: > > > > > > > > i don't wanted to spam all people with dumb questions ;) > > > > > > There's no dumb questions, only insufficient documentation :-) > > > > > > > > For examples please grep for drm_fbdev_generic_setup(). There's also a > > > > > still in-flight series from Gerd Hoffmann to convert over bochs. That, > > > > > plus all the kerneldoc linked from there should get you started. > > > > > -Daniel > > > > > > > > this is one of google best founds if i search for drm_fbdev_generic_setup: > > > > > > > > https://lkml.org/lkml/2018/12/19/305 > > > > > > > > not very helpful... > > > > > > > > so i tried kernel-doc > > > > > > > > https://www.kernel.org/doc/html/latest/gpu/drm-kms-helpers.html?highlight=drm_fbdev_generic_setup#c.drm_fbdev_generic_setup > > > > > > > > which is nice function-reference but i've found no generic workflow > > > > > > > > as the posted driver is "only" a driver ported from kernel 4.4 by Alexander, i don't know if this new framework can be used and which parts need to be changed. I only try to bring his code Mainline.... > > > > Maybe CK Hu can help here because driver is originally from him and he knows internals. Or maybe you can help here? > > > > > > > > i personally make my first steps as spare-time kernel-developer :) > > > > > > There's a ton of in-kernel users of that function already, I meant you can > > > use those to serve as examples ... If those + the kerneldoc aren't > > > good enough, then we need to improve them. > > > -Daniel > > > > I've tried with drm_fbdev_generic_setup() and it works fine with simple > > modification. The patch is > > > > --- a/drivers/gpu/drm/mediatek/mtk_drm_drv.c > > +++ b/drivers/gpu/drm/mediatek/mtk_drm_drv.c > > @@ -16,6 +16,7 @@ > > #include > > #include > > #include > > +#include > > #include > > #include > > #include > > @@ -379,6 +380,7 @@ static void mtk_drm_kms_deinit(struct drm_device > > *drm) > > .gem_prime_get_sg_table = mtk_gem_prime_get_sg_table, > > .gem_prime_import_sg_table = mtk_gem_prime_import_sg_table, > > .gem_prime_mmap = mtk_drm_gem_mmap_buf, > > + .gem_prime_vmap = mtk_drm_gem_prime_vmap, > > .ioctls = mtk_ioctls, > > .num_ioctls = ARRAY_SIZE(mtk_ioctls), > > .fops = &mtk_drm_fops, > > @@ -416,6 +418,8 @@ static int mtk_drm_bind(struct device *dev) > > if (ret < 0) > > goto err_deinit; > > > > + drm_fbdev_generic_setup(drm, 32); > > + > > return 0; > > > > > > But I implement .gem_prime_vmap with a workaround, > > > > > > --- a/drivers/gpu/drm/mediatek/mtk_drm_gem.c > > +++ b/drivers/gpu/drm/mediatek/mtk_drm_gem.c > > @@ -280,3 +280,8 @@ int mtk_gem_create_ioctl(struct drm_device *dev, > > void *data, > > mtk_drm_gem_free_object(&mtk_gem->base); > > return ret; > > } > > + > > +void *mtk_drm_gem_prime_vmap(struct drm_gem_object *obj) > > +{ > > + return (void *)1; > > +} > > > > Current drm_fb_helper depends on drm_client to create fbdev. When > > drm_client create drm_client_buffer, it need to vmap to get kernel > > vaddr. But I think for fbdev, the vaddr is useless. Do you agree that I > > temporarily implement .gem_prime_vmap in such way? > > The vmap is used by fbcon, without that fbdev won't really work I think. > So I'm rather confused on what you tested ... > > Adding Noralf, he's the expert here. > -Daniel I test with fb_test [1], it is a user space program just open /dev/fb0 and mmap it to user space. I does not turn on fbcon so everything looks well. If support fbcon is essential, I would implement vmap correctly. If it's not essential, I think I could return 0 when CONFIG_FRAMBUFFER_CONSOLE is defined. Regards, CK [1] https://android.googlesource.com/platform/system/extras/+/master/tests/framebuffer/fb_test.c _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel