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 X-Spam-Level: X-Spam-Status: No, score=-4.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 187F9C282E2 for ; Fri, 19 Apr 2019 22:13:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C914121736 for ; Fri, 19 Apr 2019 22:13:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1555711990; bh=+8a0vu7tBDyFO1+w5wX00D2H23CwoNmd50qBZt4K3js=; h=In-Reply-To:References:Cc:From:Subject:To:Date:List-ID:From; b=OhNPrIx8X7vCGo3EgdWAJy+ksCI3OS8iUQ/6r9L3mzQ3QgUimHXfUlUEAeqSIuEFt jbbkGwt+4uIS4e10wxTy8RTG6KQmEYOqq3Tby4p69+iPhq5775dKKVeBaBuU5vDzFp gVCP6fLfrwBzT0TV2XMlUFAhbUqKStiyKa64iC+o= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727790AbfDSWNJ (ORCPT ); Fri, 19 Apr 2019 18:13:09 -0400 Received: from mail.kernel.org ([198.145.29.99]:45460 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725820AbfDSWNJ (ORCPT ); Fri, 19 Apr 2019 18:13:09 -0400 Received: from localhost (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4DD9D21736; Fri, 19 Apr 2019 22:13:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1555711988; bh=+8a0vu7tBDyFO1+w5wX00D2H23CwoNmd50qBZt4K3js=; h=In-Reply-To:References:Cc:From:Subject:To:Date:From; b=sIPZi6ezwnCxmwWGrL42h3cWCo92kPgaNRS9XD4tRDPUeSMe5rxzHglnf8EY6wqA9 U4mbzHGQIGEz3zBkSXuJRCxIJ1UB2FDmjRy6/FYKGYqwEIUgUBqDYMYKDXhZdPtqFj 6g1zOwI7XTBRgmNFVfG0KTrnrlsR3zgqvy+PujTI= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20190412183150.102131-9-sboyd@kernel.org> References: <20190412183150.102131-1-sboyd@kernel.org> <20190412183150.102131-9-sboyd@kernel.org> Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, Miquel Raynal , Jerome Brunet , Russell King , Jeffrey Hugo , Chen-Yu Tsai From: Stephen Boyd Subject: Re: [PATCH v4 8/9] clk: Allow parents to be specified via clkspec index To: Michael Turquette , Stephen Boyd Message-ID: <155571198753.15276.9424090005111204689@swboyd.mtv.corp.google.com> User-Agent: alot/0.8 Date: Fri, 19 Apr 2019 15:13:07 -0700 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Stephen Boyd (2019-04-12 11:31:49) > Some clk providers are simple DT nodes that only have a 'clocks' > property without having an associated 'clock-names' property. In these > cases, we want to let these clk providers point to their parent clks > without having to dereference the 'clocks' property at probe time to > figure out the parent's globally unique clk name. Let's add an 'index' > property to the parent_data structure so that clk providers can indicate > that their parent is a particular index in the 'clocks' DT property. >=20 > Cc: Miquel Raynal > Cc: Jerome Brunet > Cc: Russell King > Cc: Michael Turquette > Cc: Jeffrey Hugo > Cc: Chen-Yu Tsai > Signed-off-by: Stephen Boyd > --- Applied to clk-next