From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7E0D5258ED5; Wed, 28 Jan 2026 22:57:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769641070; cv=none; b=S80ZY1Vy0Vkd4ae2flliH9yt+6OFgV+9DrlV0JD5S4Im7qzsWsLjJKRclTP6gZYHh1liX7fX60Sy48MW1xnrGFGkEXe0L7Z7MvetOq1yFdT99mtpNBj3zVtCI/cAMvY3JaLyp9+B5jciBrASJKEvhtaF+ICxJTTSpv17tCiFrDY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769641070; c=relaxed/simple; bh=zzDPxa7YTOuxLsTohGS9o5cD9aMxBThQMZVsekatb4k=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=mLV5NnK4l905NL6P21WnMO2x21r8h6jC9reiPxmgcGr5qviqZwyBUBiaDpjNPiZgPQepqUx/EYJCHyFp9Aj11B5OEaOql5dE1/Chl9AFZZLXaVWbZ74ks+J3/NgE5sOfR9j8TbqQJpFt5vJrFFyEtA4YmlbxD5y+1rm1n/lPrCY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=APE1AEwT; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="APE1AEwT" Received: by smtp.kernel.org (Postfix) with ESMTPSA id ED2BAC4CEF1; Wed, 28 Jan 2026 22:57:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1769641070; bh=zzDPxa7YTOuxLsTohGS9o5cD9aMxBThQMZVsekatb4k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=APE1AEwTUOcZZ+IQmP17cC9GRK94sU9OeZ/v7jHgkDwIOBOrZpB+vQtNnXrep80Bx 9sJacVWYQ6fmBBJQon+E4uhVlMmA4PsJDmWLnT3NmVaxKhDMcx59DvgL8JbahtGyJW tlSCEoqsoDhTsndDt3Mqe3mZzNNWhVT/bJ9V+zWwFEMjT4xIYYmOxL/VmZ6jVouwE0 hHTPw5qCftlxbvrMn/eRhsu1c8GwkR6CkPfk1LtxyJmFEU7AYKXQWBFpdirjOxx5UK vDnGnXzSxLwu5r8+nlH5COUoPzb0VzZcz4lcpKNrmrtfg/B+RkdZQleGKglPI+OANW jQUhDbQJJfntQ== Date: Wed, 28 Jan 2026 14:57:48 -0800 From: Drew Fustini To: Icenowy Zheng Cc: Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Guo Ren , Fu Wei , Philipp Zabel , Dmitry Baryshkov , Michal Wilczynski , Luca Ceresoli , Han Gao , Yao Zi , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, Icenowy Zheng Subject: Re: [PATCH v6 2/9] dt-bindings: display: add verisilicon,dc Message-ID: References: <20260123092830.4046009-1-zhengxingda@iscas.ac.cn> <20260123092830.4046009-3-zhengxingda@iscas.ac.cn> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Wed, Jan 28, 2026 at 12:34:41PM -0800, Drew Fustini wrote: > On Fri, Jan 23, 2026 at 05:28:23PM +0800, Icenowy Zheng wrote: > > From: Icenowy Zheng > > > > Verisilicon has a series of display controllers prefixed with DC and > > with self-identification facility like their GC series GPUs. > > > > Add a device tree binding for it. > > > > Depends on the specific DC model, it can have either one or two display > > outputs, and each display output could be set to DPI signal or "DP" > > signal (which seems to be some plain parallel bus to HDMI controllers). > > > > Signed-off-by: Icenowy Zheng > > Signed-off-by: Icenowy Zheng > > Reviewed-by: Rob Herring (Arm) > > --- > > Changes in v6: > > - Added Rob's R-b. > > > > Changes in v5: > > - Dropped the requirement of port@0. > > - Dropped the if clause for TH1520, which seems to be not needed because > > of implicit DT binding rules. > > > > Changes in v4: > > - Added a comment for "verisilicon,dc" that says the ID/revision is > > discoverable via registers. > > - Removed clock minItems constraint w/o specific compatible strings. > > > > Changes in v3: > > - Added SoC-specific compatible string, and arm the binding with clock / > > port checking for the specific SoC (with a 2-output DC). > > > > Changes in v2: > > - Fixed misspelt "versilicon" in title. > > - Moved minItems in clock properties to be earlier than items. > > - Re-aligned multi-line clocks and resets in example. > > > > .../bindings/display/verisilicon,dc.yaml | 122 ++++++++++++++++++ > > 1 file changed, 122 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/display/verisilicon,dc.yaml > > I've applied the bindings patches (1, 2, 4) to thead-dt-for-next as well > so that 'make W=1 dtbs_check' won't break for the next release of > linux-next. > > https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git/log/?h=thead-dt-for-next > > Please see my reply to patch 1 for the rest of my message. I've dropped the yaml patches from thead-dt-for-next based on Conor's advice. Patches 1, 2 and 4 can go through drm. Drew