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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E20E9CDB483 for ; Thu, 12 Oct 2023 10:33:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377775AbjJLKda (ORCPT ); Thu, 12 Oct 2023 06:33:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34856 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234170AbjJLKd0 (ORCPT ); Thu, 12 Oct 2023 06:33:26 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e5ab]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1B72290; Thu, 12 Oct 2023 03:33:25 -0700 (PDT) Received: from [192.168.1.100] (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id F243E660733F; Thu, 12 Oct 2023 11:33:22 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1697106803; bh=00AF0ZzRGxYkozvqS7tP70zcKb+I/COOXlccZYk/8bg=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=LMNU9QqICRKVi5V1+62Z9wy0+S9uRYM/HPL7fMGlmJ+QSN8/ueXOrPuJUExo7h94p 3STQ7GpZaK35JRBEcPQDrBPWgSOg/gaBksKBiiGie6OFVwgqbt+9eFus+0U4zUajm2 EIJL2hCv07hDMWXuMPHP4auyj6SaYMXjdoPjkD5Ds4Y/BRmHrVV+lJs6nSliddwnWh V4nAd/JabPblCdWTEzbLxxqVrT+pcbYdztJ34uh1LXVnq0bg1orcdiS7Gb4FKNMdwU oVwyXrel3Qc98LGWb8H7lH8myYoB/SZxR2h7mxh/l54RrR67mE1AEmWwYgkHNVqYkA +cffWlzKUUKIw== Message-ID: <83545460-deac-2793-ad97-3957b09e4aaa@collabora.com> Date: Thu, 12 Oct 2023 12:33:20 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0 Subject: Re: [PATCH v7 02/16] dt-bindings: media: mediatek: mdp3: merge the indentical RDMA under display Content-Language: en-US To: Moudy Ho , Chun-Kuang Hu , Philipp Zabel , David Airlie , Daniel Vetter , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Mauro Carvalho Chehab , Matthias Brugger , Hans Verkuil Cc: dri-devel@lists.freedesktop.org, linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, linux-arm-kernel@lists.infradead.org References: <20231012084037.19376-1-moudy.ho@mediatek.com> <20231012084037.19376-3-moudy.ho@mediatek.com> From: AngeloGioacchino Del Regno In-Reply-To: <20231012084037.19376-3-moudy.ho@mediatek.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 12/10/23 10:40, Moudy Ho ha scritto: > To simplify maintenance and avoid branches, the identical component > should be merged and placed in the path belonging to the MDP > (from display/* to media/*). > > In addition, currently only MDP utilizes RDMA through CMDQ, and the > necessary properties for "mediatek,gce-events", and "mboxes" have been > set up for this purpose. > Within DISP, it directly receives component interrupt signals. > > Signed-off-by: Moudy Ho I agree in that this belongs to bindings/media and not bindings/display, as the display-specific RDMA component is display/mediatek/mediatek,rdma.yaml. The merge looks good to me, so... Reviewed-by: AngeloGioacchino Del Regno