Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4515843imm; Tue, 7 Aug 2018 02:54:51 -0700 (PDT) X-Google-Smtp-Source: AAOMgpc2adgLzOxoXN0VwHuw6c0KdBz1XBEYXJJ+vWL+gNTVcW3cYZ+tvgLgb06pFnDgYNB9s9M0 X-Received: by 2002:a63:e355:: with SMTP id o21-v6mr18074080pgj.251.1533635691224; Tue, 07 Aug 2018 02:54:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533635691; cv=none; d=google.com; s=arc-20160816; b=Q0wHUwOVDrDc9Lva9yyFdraj4sh43x7IEl5cKT+uIhMIgcHLvcsrDkz+5XbbDYQFx9 W8uJJ+tvykuaLQH87hdolw6j9oGzhiCrlSst18Dda/LhjI09I933WAUsNMc5/Busua7w /OHVpkjqKXLfd1GX3DtNRWggAsg9+4qWQPPLfLK00sgG+Iuddl6+ddTj6LL3l+SZq4RZ HC0akvXWOpNWcza3WKmxQl/4y2LT/aIEQ3iOvu1QEo1i3N2zW9/NnGUpXJ+6BlcTjFJr bzLpTySGT+Z5wwSJRVnwLSj4GYfFCV/LT9FNzkOzy5WuBC2iuHVHd/6S3wQNVDanhyj5 s8oA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=h5som3Vf+Pb5a3DiEipa7vFITBTctN+KVNCehDYdkXo=; b=PybOYRgvqN/PBfIAcbzlacUVC+dLplc4zDu04MmBioZ8KGdrTe55EvelE/cuOoABzZ 16A7CuMBPmZRFhWSpyF8V0pGIc/5Ui1DwbWCUlk+r+hXwop9mvwzXocN+n5clia/RthQ uCbJ/kuldDaN9udAzhYTWnvAZLFu5f/KwVV2rWYVn3aEdO9b6Z2092FrTEjXoOR/RyXN WTWkrzACOPB9lEFgPayMQQU6YhvgOnkgW7HbfwwLdNWqm6XjDpF0+mquxbmCnxHvw5+H 66ynFXCWyzZygOzq3Ba4L/7lkxQwAoGwA9FSs8z31TUxgq6RS5KPDE7GmdzSCR6i/sml qbsw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y18-v6si773473pll.82.2018.08.07.02.54.36; Tue, 07 Aug 2018 02:54:51 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732639AbeHGMEh (ORCPT + 99 others); Tue, 7 Aug 2018 08:04:37 -0400 Received: from mailgw02.mediatek.com ([210.61.82.184]:18386 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726419AbeHGMEh (ORCPT ); Tue, 7 Aug 2018 08:04:37 -0400 X-UUID: 776f79efd57c4ae2b17f1a75725766d4-20180807 Received: from mtkcas07.mediatek.inc [(172.21.101.84)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 784866162; Tue, 07 Aug 2018 17:51:00 +0800 Received: from mtkcas07.mediatek.inc (172.21.101.84) by mtkmbs03n1.mediatek.inc (172.21.101.181) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 7 Aug 2018 17:50:59 +0800 Received: from [172.21.84.99] (172.21.84.99) by mtkcas07.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1210.3 via Frontend Transport; Tue, 7 Aug 2018 17:50:59 +0800 Message-ID: <1533635459.11190.75.camel@mtksdccf07> Subject: Re: [PATCH v3 06/13] drm/mediatek: add RGB color format support for RDMA From: Stu Hsieh To: CK Hu CC: Philipp Zabel , David Airlie , Matthias Brugger , , , , , Date: Tue, 7 Aug 2018 17:50:59 +0800 In-Reply-To: <1533610892.10818.10.camel@mtksdaap41> References: <1533556700-26525-1-git-send-email-stu.hsieh@mediatek.com> <1533556700-26525-7-git-send-email-stu.hsieh@mediatek.com> <1533610892.10818.10.camel@mtksdaap41> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, CK: On Tue, 2018-08-07 at 11:01 +0800, CK Hu wrote: > Hi, Stu: > > On Mon, 2018-08-06 at 19:58 +0800, Stu Hsieh wrote: > > This patch add RGB color format support for RDMA, > > including RGB565, RGB888, RGBA8888 and ARGB8888. > > > > Signed-off-by: Stu Hsieh > > --- > > drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 41 ++++++++++++++++++++++++++++++++ > > 1 file changed, 41 insertions(+) > > > > diff --git a/drivers/gpu/drm/mediatek/mtk_disp_rdma.c b/drivers/gpu/drm/mediatek/mtk_disp_rdma.c > > index 08866550740f..ba72d392dc27 100644 > > --- a/drivers/gpu/drm/mediatek/mtk_disp_rdma.c > > +++ b/drivers/gpu/drm/mediatek/mtk_disp_rdma.c > > @@ -35,6 +35,8 @@ > > #define DISP_REG_RDMA_SIZE_CON_0 0x0014 > > #define DISP_REG_RDMA_SIZE_CON_1 0x0018 > > #define DISP_REG_RDMA_TARGET_LINE 0x001c > > +#define DISP_RDMA_MEM_CON 0x0024 > > +#define MEM_MODE_INPUT_SWAP BIT(8) > > #define DISP_RDMA_MEM_SRC_PITCH 0x002c > > #define DISP_RDMA_MEM_GMC_SETTING_0 0x0030 > > #define DISP_REG_RDMA_FIFO_CON 0x0040 > > @@ -46,6 +48,11 @@ > > > > #define RDMA_MEM_GMC 0x40402020 > > > > +#define MEM_MODE_INPUT_FORMAT_RGB565 0x0 > > +#define MEM_MODE_INPUT_FORMAT_RGB888 (0x001 << 4) > > +#define MEM_MODE_INPUT_FORMAT_RGBA8888 (0x002 << 4) > > +#define MEM_MODE_INPUT_FORMAT_ARGB8888 (0x003 << 4) > > + > > struct mtk_disp_rdma_data { > > unsigned int fifo_size; > > }; > > @@ -144,12 +151,46 @@ static void mtk_rdma_config(struct mtk_ddp_comp *comp, unsigned int width, > > writel(reg, comp->regs + DISP_REG_RDMA_FIFO_CON); > > } > > > > +static unsigned int rdma_fmt_convert(struct mtk_disp_rdma *rdma, > > + unsigned int fmt) > > +{ > > + switch (fmt) { > > + default: > > + case DRM_FORMAT_RGB565: > > + return MEM_MODE_INPUT_FORMAT_RGB565; > > + case DRM_FORMAT_BGR565: > > + return MEM_MODE_INPUT_FORMAT_RGB565 | MEM_MODE_INPUT_SWAP; > > + case DRM_FORMAT_RGB888: > > + return MEM_MODE_INPUT_FORMAT_RGB888; > > + case DRM_FORMAT_BGR888: > > + return MEM_MODE_INPUT_FORMAT_RGB888 | MEM_MODE_INPUT_SWAP; > > + case DRM_FORMAT_RGBX8888: > > + case DRM_FORMAT_RGBA8888: > > + return MEM_MODE_INPUT_FORMAT_ARGB8888; > > I think the alphabet order of the naming reflect the dram order for each > color. Of course, big-endian and little-endian would result in reversed > naming order. I could not understand why RDMA use ARGB8888 naming for > DRM RGBA8888. If the typo is from data sheet, I could just accept this > typo and give an explain in driver because I want to align driver with > data sheet. > > Regards, > CK > OK, I would add the comment about this naming in driver rdma.c and ovl.c Regard, Stu > > + case DRM_FORMAT_BGRX8888: > > + case DRM_FORMAT_BGRA8888: > > + return MEM_MODE_INPUT_FORMAT_ARGB8888 | MEM_MODE_INPUT_SWAP; > > + case DRM_FORMAT_XRGB8888: > > + case DRM_FORMAT_ARGB8888: > > + return MEM_MODE_INPUT_FORMAT_RGBA8888; > > + case DRM_FORMAT_XBGR8888: > > + case DRM_FORMAT_ABGR8888: > > + return MEM_MODE_INPUT_FORMAT_RGBA8888 | MEM_MODE_INPUT_SWAP; > > + } > > +} > > + > > static void mtk_rdma_layer_config(struct mtk_ddp_comp *comp, unsigned int idx, > > struct mtk_plane_state *state) > > { > > + struct mtk_disp_rdma *rdma = comp_to_rdma(comp); > > struct mtk_plane_pending_state *pending = &state->pending; > > unsigned int addr = pending->addr; > > unsigned int pitch = pending->pitch & 0xffff; > > + unsigned int fmt = pending->format; > > + unsigned int con; > > + > > + con = rdma_fmt_convert(rdma, fmt); > > + writel_relaxed(con, comp->regs + DISP_RDMA_MEM_CON); > > > > writel_relaxed(addr, comp->regs + DISP_RDMA_MEM_START_ADDR); > > writel_relaxed(pitch, comp->regs + DISP_RDMA_MEM_SRC_PITCH); > >