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 A823A1DE8BF; Mon, 8 Jun 2026 07:49:17 +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=1780904958; cv=none; b=u+C1BjaVITCamkyz6nJVDD41EWbhNstHDxsn7ekw03RL3geTlSSQZC4TwM/NK6T4r/Ci4/nJKmI670oZCfHI5YfF+YbqoxqQneti5Rtg+/GtdYnMQRgyyDZOR/8VHErYhdNNTy4kjBQK5USQFHIol3wdT5XJRoX/YTuKOAfWmhI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780904958; c=relaxed/simple; bh=DDYs9Hc7KYGqeC+T3KFmi4YWfs7isV3FO0fydCX98Qo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=A0sKEMruYACKIetL8F4SQ5Ylrbxnkyz2Q8OARzHynpSEtVvm3vOQ1i+eeFLoV+xIlNjnohlJUyoEvFKviBfzu3joJFbWY14kP4uuMjlalmqbi3rno79hCy15iw+WblshIJdSeVtTKvYqEjz8n8I9ox6i9cQf6zj3ITfVcllMdLo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=D+merpwy; 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="D+merpwy" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 400EF1F00893; Mon, 8 Jun 2026 07:49:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1780904957; bh=kxTaNcAY9RKQ6zenFAqGz5cN6oBxyIOCDQqq8HMgsQw=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=D+merpwyG1yN/U9rXyWBu/DYhV+l6wOrMyo2gvHuC9PCLEzWXN+dl44+iDmje1qzu OUwYA26UCxiRfpEbbCPNwJlP2cY9dIqCbjrlTtT6GZYjIkT9w+DR0QPxni1pHiwuFd hbvnxkb3i63JDi8Hfws0bx4BrH3JUPfS7UIE0so9KIsp/xbqNm/EJKpULO2xlBIjUN I/cpbwVFiAaiRbnR2lBn5YIqoBzkiRzJ6RQP7D1hayIQiAU3aTFrG9mIVRG4QAY644 xxhIyMKcmPrYi7QInIAXdDfI0yO7qj17uj3ZlGP6sCZQ8WhPgykWJxWH4+yv+rRYgf JMhw7HKc+U87g== Date: Mon, 8 Jun 2026 09:49:13 +0200 From: Krzysztof Kozlowski To: Christian Marangi Cc: Michael Turquette , Stephen Boyd , Brian Masney , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Philipp Zabel , Felix Fietkau , linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 1/3] dt-bindings: clock: airoha: Document support for AN7583 clock Message-ID: <20260608-feathered-sincere-petrel-1e88fa@quoll> References: <20260528190000.9164-1-ansuelsmth@gmail.com> <20260528190000.9164-2-ansuelsmth@gmail.com> Precedence: bulk X-Mailing-List: linux-clk@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: <20260528190000.9164-2-ansuelsmth@gmail.com> On Thu, May 28, 2026 at 08:59:54PM +0200, Christian Marangi wrote: > Document support for Airoha AN7583 clock. This is based on the EN7523 > clock schema with the new requirement of the "airoha,chip-scu". > > Add additional binding for additional clock and reset lines. > > Signed-off-by: Christian Marangi > --- > .../bindings/clock/airoha,en7523-scu.yaml | 18 ++++++ > include/dt-bindings/clock/en7523-clk.h | 3 + > .../dt-bindings/reset/airoha,an7583-reset.h | 62 +++++++++++++++++++ > 3 files changed, 83 insertions(+) > create mode 100644 include/dt-bindings/reset/airoha,an7583-reset.h > > diff --git a/Documentation/devicetree/bindings/clock/airoha,en7523-scu.yaml b/Documentation/devicetree/bindings/clock/airoha,en7523-scu.yaml > index eb24a5687639..6c3c88798515 100644 > --- a/Documentation/devicetree/bindings/clock/airoha,en7523-scu.yaml > +++ b/Documentation/devicetree/bindings/clock/airoha,en7523-scu.yaml > @@ -30,6 +30,7 @@ properties: > compatible: > items: > - enum: > + - airoha,an7583-scu > - airoha,en7523-scu > - airoha,en7581-scu > - econet,en751221-scu > @@ -50,12 +51,29 @@ properties: > description: ID of the controller reset line > const: 1 > > + airoha,chip-scu: > + $ref: /schemas/types.yaml#/definitions/phandle > + description: phandle to Chip SCU Here you explain for what purpose this device needs to reference SCU. This is SCU, so I don't understand why SCU needs phandle to Chip SCU... Best regards, Krzysztof