From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net [23.128.96.19]) (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 185E23308B for ; Tue, 14 Nov 2023 22:30:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=baylibre-com.20230601.gappssmtp.com header.i=@baylibre-com.20230601.gappssmtp.com header.b="xKbUDYIr" Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 86E74C2 for ; Tue, 14 Nov 2023 14:30:30 -0800 (PST) Received: by mail-qt1-x82e.google.com with SMTP id d75a77b69052e-42135f8e08fso38890201cf.1 for ; Tue, 14 Nov 2023 14:30:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20230601.gappssmtp.com; s=20230601; t=1700001029; x=1700605829; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=4XST0nJe2LTZ4oHvfVDx7eyej+3hWOw1VagBLPa3XUw=; b=xKbUDYIrLlOI33Sp9f82M2rt6VNkOPlg5ByrRzr26yt/7G5zFKeYH1O6pBoZqAkfH7 vKZ4JGZR/azgL8e+X33N3ktQ29+Z9QmKdG0A94VsDCdmgDQeMkwrSWGWuNfCc/vyE7oH 45uVlJJaWYakhWIItOtwWtSKLt1242WiI5vqPfT6Zykwb+yeSz0KXhnMnbMDkZtQgYZ7 LJZqc6tcuZEFy+XY0npgygLf0anZN/l+rLqAFkSpWuWyXtsY2UKvXid7Szfb0S1VkO/l tBraPztCx0bhucOavgCxrmPVW2npCP/QLMXkMuZqoq00yxVAAQALwqJ7XDiq9Tu5dU4g SVww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700001029; x=1700605829; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=4XST0nJe2LTZ4oHvfVDx7eyej+3hWOw1VagBLPa3XUw=; b=vxbBiF/u3zUGQCaRwSKHujX79zevvOvtHCdK8D/qhk4OYHDIaGXLAqPNINbh3cORma vCmUa3uguCROL30ls7McFPGK6Uhv9R4YMrwUVuMu+GwhGmtYhkqTfahs1RcaBzQsZI1m /IvVqqjhUdv6hESvgX6lEJOfxsDas6h/ENJ8y33Kre3wDGBrP7TBBdI2QHvLDW5gPCz5 by97soj9ev7ob7YR++ecIDT38kNKkNVVVt5a1wo7xtYn3GvWI05ID5MuU0tmkBucE0H/ 1oJYMujpCAV8hPqDhkyY6AWMAdLsf/mdBL3ZW6xGXnEm19YELKv5o40GI8IkSF9jtOWw vtdA== X-Gm-Message-State: AOJu0YzuW1iBkWS9CPMcO6+coO4CevoqzKylDPKQbaUULFqVcpLHb8zs jWhNGRkp651I3jRCot69SIIWbw== X-Google-Smtp-Source: AGHT+IFMKHaDQrXdjPlVZanAMM7n0JSJwglGmnqidJ3M4rjzD/Zj6FS0kt5MVg8MvJG467X+FEDorg== X-Received: by 2002:a0c:f9cc:0:b0:66d:5dd:26f6 with SMTP id j12-20020a0cf9cc000000b0066d05dd26f6mr4147253qvo.25.1700001029699; Tue, 14 Nov 2023 14:30:29 -0800 (PST) Received: from x1 ([12.186.190.2]) by smtp.gmail.com with ESMTPSA id c14-20020a0cd60e000000b0066cf06339bcsm21546qvj.0.2023.11.14.14.30.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Nov 2023 14:30:29 -0800 (PST) Date: Tue, 14 Nov 2023 17:30:26 -0500 From: Drew Fustini To: Conor Dooley Cc: Ulf Hansson , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Jisheng Zhang , Adrian Hunter , Paul Walmsley , Palmer Dabbelt , Albert Ou , Guo Ren , Fu Wei , linux-mmc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org Subject: Re: [PATCH v6 5/7] riscv: dts: thead: Add TH1520 mmc controllers and sdhci clock Message-ID: References: <20231114-th1520-mmc-v6-0-3273c661a571@baylibre.com> <20231114-th1520-mmc-v6-5-3273c661a571@baylibre.com> <20231114-starring-swarm-0e1b641f888c@squawk> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231114-starring-swarm-0e1b641f888c@squawk> On Tue, Nov 14, 2023 at 09:27:44PM +0000, Conor Dooley wrote: > On Tue, Nov 14, 2023 at 04:07:59PM -0500, Drew Fustini wrote: > > > + sdhci_clk: sdhci-clock { > > + compatible = "fixed-clock"; > > + clock-frequency = <198000000>; > > + clock-output-names = "sdhci_clk"; > > + #clock-cells = <0>; > > + }; > > If only you had a clock driver to provide these... > > Is someone working on a resubmission of the clock driver? Yangtao Li posted an initial revision back [1] in May but I don't think there has been any follow up. It is for sure something we need to have in mainline so I'll take a look at getting that effort going again. Drew [1] https://lore.kernel.org/linux-riscv/20230515054402.27633-1-frank.li@vivo.com/