From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-qv1-f44.google.com (mail-qv1-f44.google.com [209.85.219.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B66254E3ECE for ; Fri, 9 Oct 2026 14:24:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.219.44 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791555847; cv=none; b=KilQCcPUBUL6jxDyQVz2Tg6HcbpfQwnfRt6U0ZKUmZ/P45GU5d5MPPUCgdzoFGJqHo3A4JOzjzi++A9h1k88IziSq1U8LdVjh1T6elInPvu+YJEqRsJ8qwuXL/UT5BpwgKF2P9WhLca3A77Lm4Kt25+lByy8x9eDK8F4FoE9htI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791555847; c=relaxed/simple; bh=5afvs8MvB8g8cyiV0dvhk0wts/9RLtB6TmHb87Dw3Ug=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=QTM9SAGRyu3z7C+OKzXOThVgwvpLP6D/0LAGN/01WhWqmB48/BW738+9xq1JnOhTu86FQFwHk7taCO/jj2DpM1l44hFVgy9oF6UvBBmdiD018WQr93RD45fYeke9Ikp+FvlmHyvpEo8Rp/Jk5NKzfPGqPEVCwy0NUTrjwme6nF4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=riscstar.com; spf=pass smtp.mailfrom=riscstar.com; dkim=pass (2048-bit key) header.d=riscstar-com.20251104.gappssmtp.com header.i=@riscstar-com.20251104.gappssmtp.com header.b=XIgboO8F; arc=none smtp.client-ip=209.85.219.44 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=riscstar.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=riscstar.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=riscstar-com.20251104.gappssmtp.com header.i=@riscstar-com.20251104.gappssmtp.com header.b="XIgboO8F" Received: by mail-qv1-f44.google.com with SMTP id 6a1803df08f44-9142e83204aso24720956d6.1 for ; Fri, 09 Oct 2026 07:24:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=riscstar-com.20251104.gappssmtp.com; s=20251104; t=1791555844; x=1792160644; darn=vger.kernel.org; h=content-transfer-encoding:content-type:in-reply-to:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:from:to:cc:subject:date:message-id:reply-to :content-type; bh=aHhnSl5etYVacPAAIx+gDocb5CfPyv6BoCMmkWUozsk=; b=XIgboO8FzZ4ez5Czapz2VOnoaFGjL4MVDrU/ZbPjW0kkQ1CPxeW5TFLUBWWPWZFYw9 uMvzY6EmVURLCgMbvJ08Hp4Lh1nFE1y71PM3CljMVU7Fpn0jN2q5ztWPof+1k5KPhrHa vYGXei4UaSPVSFH8ND/XrO6WWR10+P0fVn3up9W3IJgBmm9qricGCepp9j+WBpzk2W4C 7URgMeDJr97NCfbrBwrg8PmY4+wFpP8BYULF1SpBiclTctYSM5m7ufdSYYm6PGEcJt9t QiF81kl023IEB59sll28R73DBfY9NlCniy8Ze2NtK5ZJAkcnLuNmQA5+TK8lz5NwPPnv wDXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1791555844; x=1792160644; h=content-transfer-encoding:content-type:in-reply-to:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to:content-type; bh=aHhnSl5etYVacPAAIx+gDocb5CfPyv6BoCMmkWUozsk=; b=tvI+haoIP7Kh/SyQ59oDXYEauHWP+gkaUuh89Y5VGAwo3hs1Ut3o3w16VYccB/i8/v gJCxERWbJLGjC1p9LGZUOVolxDWOHq8bN4mggykMxNX+1cyUwPKO/YnSBmctjvliF/J7 3y5rcb7av2gwkPzGiF5NOs29j3GaA7dPThZ48e3vVObJcyYul44vRfQXz5eTjvFAn7Aj Sl2Lg7ZoMSwfHZh1+861C6jhTJutWT+77x2935f21vVciQ2RYIJL1CTHczMKKGaFA/7V 9z4DMT2TGk/7jO2H+zZK80AVSzEYrMxYnKdTyB8+78eVu8ExnJ5jYMjhJyPOnboZAxK0 WH7A== X-Forwarded-Encrypted: i=1; AKwUvBz7MD/dPPlkIsaOTUWTtmyYv00TEnDBr/OUs2aChCqyW68jLabjdH0AZoDD2qGVzvoa/ivSjw6K3Ew=@vger.kernel.org X-Gm-Message-State: AFq9FYL85G3ZNvGSjI6LDNy+yWbUg3RgTzcjMukXMvfGjZsZIYQWzf4G Jz+Q/lB8G4jbnRaeD3fpyfpglRkg78upcNujhX0EO5BnFLUXJU/pOS0KYMzLq9sxpFUQG2n4AYq v8xAQ/U4= X-Gm-Gg: AYBFou3UWsy8tHEZvUfIihnFSSWO3lGmkjn5V4fXZWffakeSlVZAFBTevhZpoILdp+J 0Y/MIKIpzF7PLMBTYeQOgJEM7CVJRNhgcAnanIh5H43RY+ib3hKROBwZ1XaAbW1SoruPI/F4+mU Fcou43LnZmvT6vL99g6XCC/1KO5itPGIbvlRKOL6lstc9BV1xzVuGFa9BuJYMlwjQ37rb/N+D4g JUU6G2+3SphNs6dH508lIAGQtD4uHmVD4GiyLldJfi67pPs7y0VLi+5v621RvomhisPQDxb/5Ev TEQ0i+NXcLbS45w0P0no8wlqquE+Z6BCIAZBbbLi7zNik2JrUdzZjG5PiXnfURUfx0ukUVeoutx 9p0iatFeMpivqlmKJ0hlll+uYADQnOMviNTPymQkK2A1Bfqf+0oEdtVrsObSaGK/jo/jfi0ZPv6 KtvFbWJPSxd1unflVoqz4oX0M01U0BYbTiI2C6GnrVMDIU0N0Uy/xyokTS/3eJ6RMneJlUxLg= X-Received: by 2002:a05:6214:410c:b0:91b:5d85:6521 with SMTP id 6a1803df08f44-91b5d8571e7mr20208846d6.24.1791555842704; Fri, 09 Oct 2026 07:24:02 -0700 (PDT) Received: from [172.22.22.28] ([73.62.185.64]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-91b54e832edsm19562406d6.4.2026.10.09.07.23.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 09 Oct 2026 07:24:01 -0700 (PDT) Message-ID: <77dacc46-7294-47c8-899a-fd56b6a2af55@riscstar.com> Date: Fri, 9 Oct 2026 09:23:59 -0500 Precedence: bulk X-Mailing-List: linux-clk@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 1/3] dt-bindings: clock: introduce toshiba,tc9564-clock.yaml To: Krzysztof Kozlowski Cc: sboyd@kernel.org, bmasney+clk@redhat.com, jbrunet+clk@baylibre.com, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, andersson@kernel.org, konradybcio@kernel.org, abelvesa@kernel.org, kees@kernel.org, gustavoars@kernel.org, mohd.anwar@oss.qualcomm.com, lorenzo.bianconi@oss.qualcomm.com, danielt@kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org, Daniel Thompson References: <20261005230927.2000398-1-elder@riscstar.com> <20261005230927.2000398-2-elder@riscstar.com> <20261009-gifted-stylish-tortoise-95b14d@quoll> Content-Language: en-US From: Alex Elder In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 10/9/26 8:56 AM, Krzysztof Kozlowski wrote: > On 09/10/2026 15:44, Alex Elder wrote: >> On 10/9/26 4:31 AM, Krzysztof Kozlowski wrote: >>> On Mon, Oct 05, 2026 at 06:09:24PM -0500, Alex Elder wrote: >>>> Define the binding for the clock controller functionality present in >>>> the Toshiba TC9564 SoC. >>>> >>>> Co-developed-by: Daniel Thompson >>>> Signed-off-by: Daniel Thompson >>>> Signed-off-by: Alex Elder . . . >>>> +properties: >>>> + compatible: >>>> + const: toshiba,tc9564-clock >>>> + >>>> + toshiba,config-syscon: >>>> + $ref: /schemas/types.yaml#/definitions/phandle >>>> + description: >>>> + Phandle for the configuration space system controller. >>> >>> I do not see my previous comment addressed - you have no resources here, >>> so this belongs to the parent. You responded something about pci-ep, but >>> the parent is not pci-ep. Open your code: >>> https://lore.kernel.org/lkml/20260918165234.687224-5-elder@riscstar.com/ >>> >>> I clearly see code like: >>> syscon { >>> clock@ { >>> }; >>> }; >>> >>> so I do not understand what pci-ep has anything to do here. >> >> What I have now (about to send) looks like this: >> >> syscon@0 { >> compatible = "syscon", "simple-mfd"; >> reg = <0x0 0x2000>; >> >> clock { >> compatible = "toshiba,tc9564-clock"; >> #clock-cells = <1>; >> }; >> }; >> >> A reset node will also go inside the syscon, so there is another >> function for that MFD. >> >> The regmap belongs to the parent, and is looked up this way: >> >> regmap = syscon_node_to_regmap(dev_of_node(dev->parent)); > > That's driver code, so irrelevant. So how does this solve my comment > from v1? I'm trying Krzysztof. The clock controller uses two registers, 0x1004 and 0x100c, to manage whether a set of clock signals are enabled or not. (The reset controller uses two adjacent registers, 0x1008 and 0x1010, to manage whether a set of reset signals are asserted or not.) You said "no resources except a small address space" and I guess it's not clear to me what size is "big enough" to warrant representing something as a separate device. *One* of the managed clocks is a 25 MHz clock, exposed through a pin on the SoC. That one clock signal is therefore usable by the platform (although on the RB3gen2 it's not used). Rather than expose the register addresses in the clock node, a syscon is defined, covering 8 KB, and the actual offsets used are just defined in the clock and reset driver source code. If that's not the right thing to do, please say that. >>> What's more, I still do not see any usage of these clocks outside. And I >>> still did not receive actual answers (or I missed them) how these clocks >>> are routed OUTSIDE of the connector. You said for example: >>> "Ultimately the TC9564 SoC has a single 25 MHz input clock," . . . >> The single exposed clock *might* justify presenting the >> clock controller device in devicetree. There are also >> resets exposed externally via GPIOs, and these control >> external entities (PHYs). > > I cannot find any of these exposed. Please point me to DTS code showing > this. It is not used by this platform, but is available for other platforms to use. Its name is "REFCLKO" and is exposed on ball C17 of the SoC, if a platform designer decided to use it. I only mention its existence as a reason to justify defining the clock as a separate device, but I realize you are arguing that I should do it somehow differently. -Alex > > Best regards, > Krzysztof