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 phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 55B4BC61DA4 for ; Thu, 23 Feb 2023 13:56:58 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id BE17185738; Thu, 23 Feb 2023 14:56:55 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=reject dis=none) header.from=mailbox.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; secure) header.d=mailbox.org header.i=@mailbox.org header.b="W0GGG/NR"; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b="XySJUDm8"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 7844B85670; Thu, 23 Feb 2023 14:56:54 +0100 (CET) Received: from mout-y-111.mailbox.org (mout-y-111.mailbox.org [IPv6:2001:67c:2050:103:465::111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id CF77285738 for ; Thu, 23 Feb 2023 14:56:48 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=reject dis=none) header.from=mailbox.org Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=marek.vasut@mailbox.org Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-y-111.mailbox.org (Postfix) with ESMTPS id 4PMvhZ4G2cz9sfC; Thu, 23 Feb 2023 14:56:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1677160606; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+MElZ4dCbGXd6Ui1e1eYeg6c0JPUyCr1UeDKkMRI2Ss=; b=W0GGG/NRS9MNuYqdajWRBDbM8ReJtDf/WKrsJDvP90hrooGHQZ1ZG6cTL4hdvjuvKfxgnL iEOK+W8ALd4MOf+YslIodqxenHh9DrwvUviQoaNT1/RE7E5qErGDydY2EaI5OemGUddmSM HouK3bs93IZkfRvWS5zQRK1yEnW8M6xVfONifpDmBJDy+cmOOos2mRAZk8fVpAC2qaJPnb 4BfYzEUb6SYYQ9RLK+ehgMiw5g+nXcl5rJbIQfOADmLVC+uFgwMmiHTINwfVJwRPNj0HMp gnmaxMqStU2Tz3zT7GfG+XnT0r4E9LJbX3O4aQC/GNrXl/hOgnGVbXd1JOQAzg== Message-ID: <83a45ea0-edd1-3a79-4772-90876559dc75@mailbox.org> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1677160604; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+MElZ4dCbGXd6Ui1e1eYeg6c0JPUyCr1UeDKkMRI2Ss=; b=XySJUDm8EkjI2VA6gzW3OnuEaKGAL2DKea6QfBMBZirluRJxpyKHwJqCDIuWS3n/IjVyyW Fq6htdOgFWF9/y+9mUxHEAPmq13U8muGsVlbO9CqLtb+rcDsZ7G5IhBUzI8aIwaIb9kf+Y 044h6Nm+G1azL6yi3XSrjMEfz7XHBokOL6HaYxvaDxAuI5kgF7zR4vUnmcKTBPGr7PW6A2 icBGQqyaOou/LXoT98ZvaWlZTjFQRzSuH8Ul9+hGzR6Qi2bf9qboYc1NLdYY62y0R6wnpG DYOGrhPc6lpqS4s2P8U28T68Z6Axfwy1bc9NAIDN4f/xD4oPAHN9Jmfr+rF6xg== Date: Thu, 23 Feb 2023 14:56:41 +0100 MIME-Version: 1.0 Subject: Re: [RFC PATCH v3 3/9] clk: renesas: add R906G032 driver Content-Language: en-US To: Miquel Raynal Cc: Ralph Siemsen , u-boot@lists.denx.de, Hai Pham , Lukasz Majewski , Marek Vasut , Sean Anderson References: <20230222154414.49219-1-ralph.siemsen@linaro.org> <20230222154414.49219-4-ralph.siemsen@linaro.org> <49f64e41-adfe-b426-2a57-9c4721894885@mailbox.org> <20230222165749.GA50215@maple.netwinder.org> <20230222172145.GB50215@maple.netwinder.org> <20230222183220.GC50215@maple.netwinder.org> <0e3597e5-d72a-f246-c779-1fd153299ce8@mailbox.org> <20230222193200.GD50215@maple.netwinder.org> <124b691a-57bc-1df4-60b7-caa7acea2229@mailbox.org> <20230223081741.455273e3@xps-13> From: Marek Vasut In-Reply-To: <20230223081741.455273e3@xps-13> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-MBO-RS-ID: 194eb9e217a55f6953f X-MBO-RS-META: a93up586h8pciq144em988pstqrnrykp X-Rspamd-Queue-Id: 4PMvhZ4G2cz9sfC X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.6 at phobos.denx.de X-Virus-Status: Clean On 2/23/23 08:17, Miquel Raynal wrote: > Hello Marek & Ralph, > > marek.vasut@mailbox.org wrote on Thu, 23 Feb 2023 01:12:49 +0100: > >> On 2/22/23 20:32, Ralph Siemsen wrote: >>> On Wed, Feb 22, 2023 at 07:45:45PM +0100, Marek Vasut wrote: >>>> On 2/22/23 19:32, Ralph Siemsen wrote: >>>>> On Wed, Feb 22, 2023 at 06:47:44PM +0100, Marek Vasut wrote: >>>>>> Are those fixes in mainline Linux ? >>>>> >>>>> Yes, they are in mainline: >>>>> 2dee50ab9e72 clk: renesas: r9a06g032: Fix UART clkgrp bitsel >>>>>   merged into 6.0, and also backported to earlier LTS branches >>>>> 2a6da4a11f47 clk: renesas: r9a06g032: Fix the RTC hclock description >>>>>    merged into 5.19, seems to be missing from LTS branches >>>> >>>> Use Linux 6.2.y as a base then. >>> >>> Okay, done. >>> >>>> And please submit the missing patches for LTS branch inclusion too if >> possible, I guess they were missing Fixes: tag ? >>> >>> Seems it was part of a series which added support for the RTC device: >>> https://lore.kernel.org/all/20220421090016.79517-3-miquel.raynal@bootlin.com/ >>> Since it is new feature, I guess one could argue that the clock table > fix is not needed in older LTS kernels, since no driver uses that clock. >>> But most likely it was just overlooked. I'll check with Miquel. >> >> Much appreciated, thanks ! >> >> +CC Miquel > > As Ralph rightly pointed out, even though the clock description was > wrong there was no user at that time so I did not bother with a Fixes > tag. Anyhow, as the change does only impact the RTC clock, it should be > harmless to backport if you want. Either way is fine by me, I just want to be sure the u-boot clock tables are in sync with Linux as much as possible, and can be easily resynced in the future, that's all.