Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp457103imu; Thu, 8 Nov 2018 10:38:52 -0800 (PST) X-Google-Smtp-Source: AJdET5d1XAyiAJGnTitIltLs1EgFFS6bBkm5Rv1qChly3nZcnsqhKkdXd5aGe8ORxRhTP4ji5Qxq X-Received: by 2002:a17:902:8e8a:: with SMTP id bg10-v6mr5664991plb.214.1541702332305; Thu, 08 Nov 2018 10:38:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541702332; cv=none; d=google.com; s=arc-20160816; b=TEYcu1G9Fyk82SZ8hYpOCn9FKiAFZGOFvLFpORU8majTds+RW9HprPqXuJMw4UQZBH +L8chzC5ntwqyvK691v09IrrVFU3x7vfB+f1rvkUpKZ7IE4w+AYo2DIcvtD/r8KnKDGV WvBZPfj0wlHrPz+P4gEFvi/gbek9jkDQUbNfdIikRXM/AVET1Ez8DZ3DFqeKZ4keCzEd ggX3j/AjOZuqgAAmjDsR+S59JxiQ3SkpihHyH1oZZTjyHBMb54wGXQ8V14jk9Fid+NqL LDOOPzoChtUSX9TMEC3qybne7kTgCNkPKn6vYPiDFkGX/SUcHtDbftZVzwd9QNSj8Zwl Q93w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:date:subject:user-agent:message-id :references:cc:in-reply-to:from:to:content-transfer-encoding :mime-version:dkim-signature; bh=0kvz1cgnIX528UcnUKDxkJ1gsIEwI7ms/33cUKH1/MM=; b=qjsWSkmqLEcMvvSYVUp1v57A2aNSLH5Xviwa4gjYqGS5JQt5/nvJZFkSjEoHLXnvvv +i4eI8j8/YToiwe+A3t5/odwUeY6SbN4orQCSNMPqkgNGTk1hjQpH9nfa2W0tVlAbIOx d/RrS+eXfKK97n6h2OZSfxqE/pbUG6nftBl+ufLyQ845xqMmQD++JTFAYYZGdw0v6NFi hHvw5jap8cLPuXwJ1TXBTNxWIdgU1SqZ4rpEMu3srQAOnV+oZ6800tidxrYuEpBBWuF8 iLi+ZbMMq+G9+X8nc/1TB0C0vESdugRje1NKPfoialJmte2u1y9qofcFvjKl4md/GBcC I31w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=BBMbSbtn; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a61-v6si5384877pla.430.2018.11.08.10.38.37; Thu, 08 Nov 2018 10:38:52 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=BBMbSbtn; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727517AbeKIEOS (ORCPT + 99 others); Thu, 8 Nov 2018 23:14:18 -0500 Received: from mail.kernel.org ([198.145.29.99]:57474 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727485AbeKIEOR (ORCPT ); Thu, 8 Nov 2018 23:14:17 -0500 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 30CAA2081C; Thu, 8 Nov 2018 18:28:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541701728; bh=0kvz1cgnIX528UcnUKDxkJ1gsIEwI7ms/33cUKH1/MM=; h=To:From:In-Reply-To:Cc:References:Subject:Date:From; b=BBMbSbtnZQTc6iwuXvbv4n3L3xdo+3XqW66UuT/V/DJ3UZZUyT/7N+4Nnm/j/tSEX UVcP+EhOS2pYUrVlkox8kcclENeDCT9QN4wfF8L0pVOiPQ0bqaxr2NRWxOj9Kosgus fhLgAIgAE+iadN97/M9gD/5ywBSdqXFw2hi5zTWg= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable To: Abel Vesa From: Stephen Boyd In-Reply-To: <20181108122938.mnhu3ttnlztfeyot@fsr-ub1664-175> Cc: Andrey Smirnov , Anson Huang , "A.s. Dong" , Fabio Estevam , Lucas Stach , Rob Herring , Sascha Hauer , dl-linux-imx , Abel Vesa , Shawn Guo , Sascha Hauer , Michael Turquette , open list , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , "open list:COMMON CLK FRAMEWORK" References: <1537785597-26499-1-git-send-email-abel.vesa@nxp.com> <1537785597-26499-4-git-send-email-abel.vesa@nxp.com> <153980615257.5275.13866740376184829057@swboyd.mtv.corp.google.com> <20181107115444.gscxwud7e57nx3c7@fsr-ub1664-175> <154161726247.88331.15629902810537417880@swboyd.mtv.corp.google.com> <20181107202624.oya2runvbbwcilzu@fsr-ub1664-175> <154163631513.88331.1765456171211364913@swboyd.mtv.corp.google.com> <20181108122938.mnhu3ttnlztfeyot@fsr-ub1664-175> Message-ID: <154170172752.88331.2213352243956732809@swboyd.mtv.corp.google.com> User-Agent: alot/0.7 Subject: Re: [PATCH v9 3/5] clk: imx: add SCCG PLL type Date: Thu, 08 Nov 2018 10:28:47 -0800 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Abel Vesa (2018-11-08 04:29:39) > On Wed, Nov 07, 2018 at 04:18:35PM -0800, Stephen Boyd wrote: > > Quoting Abel Vesa (2018-11-07 12:26:25) > > > On Wed, Nov 07, 2018 at 11:01:02AM -0800, Stephen Boyd wrote: > > > > = > > > > = > > > > What's the plan to clean it up? > > > = > > > So I'm doing this in our internal tree first to make sure I don't bre= ak the > > > other (newer) socs. > > > = > > > I already have a prototype in testing but it's a long way to upstream= it. > > > = > > > Basically, I'm replacing all of this with a single, more like a compo= site, > > > more complex, clock type that does all the magic inside. > > > = > > > One of the problems is the fact that the bypasses can have the same s= ources > > > and in my case, I'm implementing that as a list of parents name, but = the > > > parent names list doesn't work with duplicates, so I have to find som= e other > > > way to do it. > > > = > > > Once I have something clean and tested enough I'll send it upstream. > > = > > Ok. Thanks for the info. > > = > = > Just to avoid any kind of confusion. > = > The whole refactoring of the SCCG clock will be done in a separate (later= ) change > and will not be part of this patchset. > = > I already sent the 12th version of this current patch series and I would = really > like to get this in ASAP so that the booting up of imx8mq will not be del= ayed. > = Ok. Well we're in rc1 right now, and so we're not merging new drivers into mainline. I can merge the clk driver into clk-next, but you'll have to wait for the stabilization period to end (approximately 6 or 7 weeks) before this can get into the next kernel version. It will be in linux-next much sooner of course.