[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1577091576.20525.4.camel@mtksdaap41>
Date: Mon, 23 Dec 2019 16:59:36 +0800
From: CK Hu <ck.hu@...iatek.com>
To: Hsin-Yi Wang <hsinyi@...omium.org>
CC: Bibby Hsieh <bibby.hsieh@...iatek.com>,
David Airlie <airlied@...ux.ie>,
Matthias Brugger <matthias.bgg@...il.com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
dri-devel <dri-devel@...ts.freedesktop.org>,
<linux-mediatek@...ts.infradead.org>,
Nicolas Boichat <drinkcat@...omium.org>,
<srv_heupstream@...iatek.com>,
Yongqiang Niu <yongqiang.niu@...iatek.com>,
lkml <linux-kernel@...r.kernel.org>,
"Tomasz Figa" <tfiga@...omium.org>,
Thierry Reding <thierry.reding@...il.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v5 6/7] drm/mediatek: support CMDQ interface in ddp
component
Hi, Hsin-yi:
On Fri, 2019-12-20 at 21:27 +0800, Hsin-Yi Wang wrote:
> On Tue, Dec 10, 2019 at 5:05 AM Bibby Hsieh <bibby.hsieh@...iatek.com> wrote:
>
> >
> > +void mtk_ddp_write(struct cmdq_pkt *cmdq_pkt, unsigned int value,
> > + struct mtk_ddp_comp *comp, unsigned int offset)
> > +{
> > +#if IS_ENABLED(CONFIG_MTK_CMDQ)
> Should we use #ifdef like in v4? https://patchwork.kernel.org/patch/11274439/
>
> We got warnings while compiling kernels if CONFIG_MTK_CMDQ is not set,
> since cmdq_pkt_write() would still be compiled.
> Similar in other #if IS_ENABLED(CONFIG_MTK_CMDQ) (also in 7/7
> https://patchwork.kernel.org/patch/11281349/)
>
I've changed IS_ENABLED() to IS_REACHABLE()in mediatek-drm-next-5.6 [1]
for the correct relationship between MTK_DRM and MTK_CMDQ.
[1]
https://github.com/ckhu-mediatek/linux.git-tags/commits/mediatek-drm-next-5.6
Regards,
CK
>
> > + if (cmdq_pkt)
> > + cmdq_pkt_write(cmdq_pkt, comp->subsys,
> > + comp->regs_pa + offset, value);
> > + else
> > +#endif
> > + writel(value, comp->regs + offset);
> > +}
> > +
Powered by blists - more mailing lists