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 F40FE33FE1F; Wed, 11 Feb 2026 20:54:00 +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=1770843241; cv=none; b=jKqmeZ+nKKU3ncw3GwXqYtPi6xFuAGffNYyiZ31/wZwP7vppvGFbRLhMUMH6679nPs4s7KZz2TQ6kQZV1fu0Xxs0WdeDkgwbY8spneuzmAkUJ02JTxgWPY+RVmK8+dmawi8UaopX0XUqmAGzaCdNXMea6Skeu4i0QqQQNjHMCfM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770843241; c=relaxed/simple; bh=C4fSmQS1/v4DY2auUQM0mERpX0iAPLQEIrmOl7DFfdE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=lP5vuTZGcTn1Z4ORZK0/nO6kf73ifKUCXw89SCFXk5ZNoUFHKHyxIBbTDq+MRSdBOWutIYuHw656nvkiV/5h66tFxcHsrCHwdjZiTT1LKkd4ta9aDs970THnbi+GyBpp3IkIHsZynEL/WqU9vCiQPnQOUWDCkq6SsXL5dRdieLI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=jVRXV0Ug; 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="jVRXV0Ug" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 85DCDC4CEF7; Wed, 11 Feb 2026 20:54:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1770843240; bh=C4fSmQS1/v4DY2auUQM0mERpX0iAPLQEIrmOl7DFfdE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jVRXV0Ug9R/cLEODGVGo4nB6dunr0Yn0nzsRZgG0XJ2omurxmlKFzRm7KpEajUB3h dTDUSSBUYQJhA6aEs2UJ24MbO+4kx5LUTyzcuz/NhRbIR+jl5XAa8mOW6Okb0wrS+0 CYhpx19GyRhtprbEo/OY0Cyz3UGhQUHyBQ29VmMqSsxMJce7qHpQoBZP5UTQibBP1p uifAqfE5eOFdz0XVpwgU61Mqhk2PNuuL9c03IZthg5xyAZbFAR6MLb7CrqNCsWsfyu V2Cn1OEVmzRTc+WTzPRF0v287JIe0zqE5XRz7WtOWv9qGSz9WWqglCwSyYvrAZpVZm j0VW0ujuvCtBA== Date: Wed, 11 Feb 2026 14:53:59 -0600 From: Rob Herring To: Shenwei Wang Cc: Bartosz Golaszewski , dl-linux-imx , "devicetree@vger.kernel.org" , Linus Walleij , "arnaud.pouliquen@foss.st.com" , Krzysztof Kozlowski , Sascha Hauer , Shawn Guo , "linux-gpio@vger.kernel.org" , Bjorn Andersson , Pengutronix Kernel Team , "linux-arm-kernel@lists.infradead.org" , "linux-remoteproc@vger.kernel.org" , Peng Fan , Conor Dooley , "imx@lists.linux.dev" , Jonathan Corbet , Mathieu Poirier , Fabio Estevam , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v7 1/4] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support Message-ID: <20260211205359.GA3857648-robh@kernel.org> References: <20260210170814.406883-1-shenwei.wang@nxp.com> <20260210170814.406883-2-shenwei.wang@nxp.com> <177075649333.2817738.5507371747833844104.robh@kernel.org> Precedence: bulk X-Mailing-List: linux-gpio@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, Feb 11, 2026 at 05:26:06PM +0000, Shenwei Wang wrote: > > > > -----Original Message----- > > From: Rob Herring (Arm) > > Sent: Tuesday, February 10, 2026 2:48 PM > > To: Shenwei Wang > > Cc: Bartosz Golaszewski ; dl-linux-imx ; > > devicetree@vger.kernel.org; Linus Walleij ; > > arnaud.pouliquen@foss.st.com; Krzysztof Kozlowski ; > > Sascha Hauer ; Shawn Guo ; > > linux-gpio@vger.kernel.org; Bjorn Andersson ; > > Pengutronix Kernel Team ; linux-arm- > > kernel@lists.infradead.org; linux-remoteproc@vger.kernel.org; Peng Fan > > ; Conor Dooley ; > > imx@lists.linux.dev; Jonathan Corbet ; Mathieu Poirier > > ; Fabio Estevam ; linux- > > doc@vger.kernel.org; linux-kernel@vger.kernel.org > > Subject: [EXT] Re: [PATCH v7 1/4] dt-bindings: remoteproc: imx_rproc: Add > > "rpmsg" subnode support > > > > On Tue, 10 Feb 2026 11:08:11 -0600, Shenwei Wang wrote: > > > Remote processors may announce multiple GPIO controllers over an RPMSG > > > channel. These GPIO controllers may require corresponding device tree > > > nodes, especially when acting as providers, to supply phandles for > > > their consumers. > > > > > > Define an RPMSG node to work as a container for a group of RPMSG > > > channels under the imx_rproc node. Each subnode within "rpmsg" > > > represents an individual RPMSG channel. The name of each subnode > > > corresponds to the channel name as defined by the remote processor. > > > > > > All remote devices associated with a given channel are defined as > > > child nodes under the corresponding channel node. > > > > > > Signed-off-by: Shenwei Wang > > > --- > > > .../devicetree/bindings/gpio/gpio-rpmsg.yaml | 55 +++++++++++++++++++ > > > .../bindings/remoteproc/fsl,imx-rproc.yaml | 53 ++++++++++++++++++ > > > 2 files changed, 108 insertions(+) > > > create mode 100644 > > > Documentation/devicetree/bindings/gpio/gpio-rpmsg.yaml > > > > > > > My bot found errors running 'make dt_binding_check' on your patch: > > > > yamllint warnings/errors: > > > > dtschema/dtc warnings/errors: > > > > > > doc reference errors (make refcheckdocs): > > Warning: Documentation/devicetree/bindings/gpio/gpio-rpmsg.yaml references > > a file that doesn't exist: Documentation/driver-api/gpio/gpio-rpmsg.rst > > Documentation/devicetree/bindings/gpio/gpio-rpmsg.yaml: > > Documentation/driver-api/gpio/gpio-rpmsg.rst > > > > The .rst file mentioned in the description is included in this same patch set. Then can't the .rst doc come first? Really, bindings should not reference kernel docs as they are used outside the kernel. However, since there is no other definition of the protocol, I think it is fine here. Rob