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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 04C5DC3DA41 for ; Wed, 10 Jul 2024 23:21:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Date:To:Cc:From:Subject: References:In-Reply-To:Content-Transfer-Encoding:MIME-Version:Content-Type: Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=eCaFT3/kRTqxtksiSHjtW7/iheSU9qRWbGpJZIcucMY=; b=CZiwRrQ9K6p2bibgEFDwOVBmSV r3zOMbxj8kuCa96QA8fZdnaFAGHha91Ikh8N/TizgqL7G7BmE+uhyZCS7iXSgx15NkY0dJqt7BUr1 LEvmpKwn6W4oJUZWK2sPQ2ejR6RLKIpn2LBwKwrf95NfIZnb7fwj0LZ4wbo+xdLYZ/vVcYjbPJCfE AEGEeZ4WnSQkO5tE4BPAZPun6dZHJMg5gdgkxt6azgG8alRWX9/o6KzCY7QrqecRXnX694BEidHwc W1ZJnhUdbEjhyf5SkwcPa7kGpRyhE5byjtr/buyUxLh5HMNJ7pgwM3PI5C/v42lbVZf6w8OSpHuI5 hP5R1xtg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sRgcy-0000000C4IR-2Cx0; Wed, 10 Jul 2024 23:21:36 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sRgch-0000000C4EX-2WAE; Wed, 10 Jul 2024 23:21:20 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 75A00619F9; Wed, 10 Jul 2024 23:21:18 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1BCC8C32781; Wed, 10 Jul 2024 23:21:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1720653678; bh=eCaFT3/kRTqxtksiSHjtW7/iheSU9qRWbGpJZIcucMY=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=hwyqFvL3uSKjrmCdyQQa4cq13kGOEJSEy2fkv2CKEDlZ5UMFNwKLgGMVZsgYHeYu9 bBi8O03DbNfXd5Xid+5FjPy7cdpiYU2WKD1qoumUyhQTkMuIXMeb3nj0lK6aihOE5z 2uZhahCucrQX9GuuXBymgbs5n7Gri8ly1kAIES4843NAlsfrFFvBtdJxOS1gLCl4iL oNcYTZtywrjftE5tJlqNIPWIOPHic2VmbhVgb4d7j728FUWe7fJnbokE3l3JEu1OVP 99JoOsaBQoWiQsZlGA2nGl72MvoscnAHqoaikGe8rVqKF4t871gCC1ukaPGn/yJuIf 0tFBwbzjAvA8w== Message-ID: <68f6dc44a8202fd83792e58aea137632.sboyd@kernel.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <21244242.0c2gjJ1VT2@diego> References: <20240709123121.1452394-1-heiko@sntech.de> <20240709123121.1452394-2-heiko@sntech.de> <12478313.O9o76ZdvQC@steina-w> <21244242.0c2gjJ1VT2@diego> Subject: Re: Re: [PATCH 1/6] dt-bindings: clocks: add binding for generic clock-generators From: Stephen Boyd Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, quentin.schulz@cherry.de, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org To: Alexander Stein , Heiko =?utf-8?q?St=C3=BCbner?= , mturquette@baylibre.com Date: Wed, 10 Jul 2024 16:21:15 -0700 User-Agent: alot/0.10 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240710_162119_724204_8D0A08EE X-CRM114-Status: GOOD ( 13.74 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Quoting Heiko St=C3=BCbner (2024-07-10 00:45:17) > Am Mittwoch, 10. Juli 2024, 09:02:34 CEST schrieb Alexander Stein: > >=20 > > So essentially only enable-gpios and vdd-supply is added in comparison = to > > fixed-clock. Does it make sense to add that to the fixed-clocks instead? > > Similar to fixed-regulator. >=20 > I wasn't that sure which way to go in the first place. > The deciding point was reading that line about the fixed clock not > being gateable, so I opted to not touch the fixed-clock. >=20 > But you're definitly right, this _could_ live inside the fixed-clock > as well, if we decide to get rid of the not-gateable thing above. It's probably more complicated to combine it with the fixed-clock binding after making properties required like vdd-supply. I'd just make a new binding and look at combining later.