linux-kernel - Re: [PATCH v2 07/16] drm/imx: Add i.MX8qxp Display Controller pixel engine

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]

Message-ID: <887b1baa-6a71-4a1b-85c1-7b3b0abbccff@nxp.com>
Date: Wed, 31 Jul 2024 13:53:52 +0800
From: Liu Ying <victor.liu@....com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
 Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
 imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, linux-phy@...ts.infradead.org,
 p.zabel@...gutronix.de, airlied@...il.com, daniel@...ll.ch,
 maarten.lankhorst@...ux.intel.com, mripard@...nel.org, tzimmermann@...e.de,
 robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de,
 festevam@...il.com, tglx@...utronix.de, vkoul@...nel.org, kishon@...nel.org,
 aisheng.dong@....com, agx@...xcpu.org, francesco@...cini.it, frank.li@....com
Subject: Re: [PATCH v2 07/16] drm/imx: Add i.MX8qxp Display Controller pixel
 engine

On 07/30/2024, Krzysztof Kozlowski wrote:
> On 30/07/2024 11:42, Liu Ying wrote:
>> On 07/30/2024, Krzysztof Kozlowski wrote:
>>> On 30/07/2024 08:55, Liu Ying wrote:
>>>> On 07/28/2024, Dmitry Baryshkov wrote:
>>>>> On Fri, Jul 12, 2024 at 05:32:34PM GMT, Liu Ying wrote:
>>>>>> i.MX8qxp Display Controller pixel engine consists of all processing
>>>>>> units that operate in the AXI bus clock domain.  Add drivers for
>>>>>> ConstFrame, ExtDst, FetchLayer, FetchWarp and LayerBlend units, as
>>>>>> well as a pixel engine driver, so that two displays with primary
>>>>>> planes can be supported.  The pixel engine driver as a master binds
>>>>>> those unit drivers as components.  While at it, the pixel engine
>>>>>> driver is a component to be bound with the upcoming DRM driver.
>>>>>
>>>>> Same question / comment: create subnodes directly, without going
>>>>> through the subdevices. A lot of small functions that would benefit
>>>>> being inlined.
>>>>
>>>> Like I replied in patch 06/16, I can't create sub devices directly.
>>>>
>>>> Can you please point out typical ones for those small functions if
>>>> the comment still stands?
>>>>
>>>>>
>>>>>> +static int dc_cf_bind(struct device *dev, struct device *master, void *data)
>>>>>> +{
>>>>>> +	struct platform_device *pdev = to_platform_device(dev);
>>>>>> +	struct dc_drm_device *dc_drm = data;
>>>>>> +	struct dc_pe *pe = dc_drm->pe;
>>>>>> +	struct dc_cf_priv *priv;
>>>>>> +	int id;
>>>>>> +
>>>>>> +	priv = drmm_kzalloc(&dc_drm->base, sizeof(*priv), GFP_KERNEL);
>>>>>> +	if (!priv)
>>>>>> +		return -ENOMEM;
>>>>>> +
>>>>>> +	priv->reg_cfg = devm_platform_ioremap_resource_byname(pdev, "cfg");
>>>>>> +	if (IS_ERR(priv->reg_cfg))
>>>>>> +		return PTR_ERR(priv->reg_cfg);
>>>>>> +
>>>>>> +	id = of_alias_get_id(dev->of_node, "dc0-constframe");
>>>>>
>>>>> Is it documented? Acked?
>>>>
>>>> Like I replied in patch 06/16, I can add aliases nodes to examples,
>>>> if needed.
>>>>
>>>> No Nak from DT maintainers I'd say, but I hope there will be direct
>>>> Ack(s).
>>>>
>>>
>>> It was not Acked, because there was no documentation added for it.
>>
>> I may add aliases nodes in examples in next version, if no objections.
> 
> Example is just example. It is not a documentation. You must explain it
> in the binding, e.g. description.

Ok, I'll explain it in the dt-binding description in next version.

-- 
Regards,
Liu Ying