From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 269713B19D4; Wed, 1 Jul 2026 07:28:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782890926; cv=none; b=cDClJVmWVyRkfUIBXMcf2ILoMHt55DGAo0+yQaFHoABU3fzqSMTsN7wfZ1nHn83wEaRI/uDDFyJ8DS5/RvlIzwB1lhXZtmM9lc4few+63YX/ibsMcpJ5xD7UpDBmXgSEbr8ojkKanRnHBJQToKJnVtEAms9eQad6cFdL+iZ6Wpc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782890926; c=relaxed/simple; bh=0BzXNpslteJF7n07zyNOZSjQMdWKS6UF7cfrWNw9A8I=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=i+ARwFFkl4kLZjjjGeuig/aI9CMdiqtA1PnwwrY9QaM3M0J9V02bEHD4tZRk3ai44nIXoTEc/xm+r8ktQfYqw91LiPY9eiyw3aMqVPIg1rEGXnH82+4xSvj5mg237bF4XFuPVdhUODwzpl9lkPWwkQjqSN9CGpUHqsSVbdmRBbk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=l4Nb0psk; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="l4Nb0psk" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CC6941F000E9; Wed, 1 Jul 2026 07:28:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782890925; bh=IYCgu7OSC8Dx4AUeKgdsj096nEM4dOcEI9jfOmqbbpw=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=l4Nb0pskMZfOonRgM9axK0Z5KkrY7e97XHMgQr9jZJ106VvFK3vobt6HRclk+arCu PF+rFpyseWHD1JkY4TMcTYWAfSdf5A75zn2A06b1gRhoS6b2M9oUKrAKC+YmDQsQEq zkOTTxdq4wGZMN7TRRy0cNAb4g+tRutSX84abOFUGyFMls5Cpx6qh8PxIPFS9iNrAR xJ991vlSe5yP3YQMZRA3ZeesnxNwEygYm/hpHvnq35w69xt4cULlcpfB3bYdMIXZod QCWJgmenlg7J/W8bsTlByHhavq4qJNoDwc/pD7coBnOIRK9hnGtPlURiNtEcXjFoBt 7RigQt66auBBg== Date: Wed, 1 Jul 2026 09:28:41 +0200 From: Krzysztof Kozlowski To: Yuanjie Yang Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, tingwei.zhang@oss.qualcomm.com Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom: Document HAMOA-IOT-COME board Message-ID: <20260701-rigorous-analytic-mackerel-449703@quoll> References: <20260630071022.3256-1-yuanjie.yang@oss.qualcomm.com> <20260630071022.3256-2-yuanjie.yang@oss.qualcomm.com> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20260630071022.3256-2-yuanjie.yang@oss.qualcomm.com> On Tue, Jun 30, 2026 at 03:10:11PM +0800, Yuanjie Yang wrote: > Document the device tree binding for the HAMOA-IOT-COME board, which uses > the Qualcomm X1E80100 SoC. > > The system consists of a SoM mounted on a carrier board. The HAMOA-IOT-COME > SoM integrates the core system, including a SiP that contains the SoC and This is contradictory to the code. Your binding said you are using IOT SoM, not IoT COME SoM. > related components. > > Hierarchy: > > Carrier Board > -> SoM > -> SiP > -> SoC Drop. Compatibles define that. > > The SiP on the HAMOA-IOT-COME SoM is equivalent to the HAMOA-IOT-EVK SoM. I don't even know what does it mean. How two different hardware can be equivalent? Are they the same? Are you creating duplicated compatibles for same hardware? Best regards, Krzysztof