[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9b54c25e-27e9-4590-9ba4-030ba485abcc@kernel.org>
Date: Mon, 2 Jun 2025 11:16:19 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: "irving.ch.lin" <irving-ch.lin@...iatek.com>,
Wim Van Sebroeck <wim@...ux-watchdog.org>, Guenter Roeck
<linux@...ck-us.net>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>, Rob Herring <robh+dt@...nel.org>,
Philipp Zabel <p.zabel@...gutronix.de>, nfraprado@...labora.com
Cc: angelogioacchino.delregno@...labora.com,
Project_Global_Chrome_Upstream_Group@...iatek.com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
linux-pm@...r.kernel.org, netdev@...r.kernel.org,
linux-mediatek@...ts.infradead.org,
Irving lin <irving-ch.lin@...iatek.corp-partner.google.com>
Subject: Re: clk: mt8189: Porting driver for clk
On 02/06/2025 10:25, irving.ch.lin wrote:
> From: Irving lin <irving-ch.lin@...iatek.corp-partner.google.com>
>
> 1. Add mt8189 clk driver
> 2. Fix mux failed
> 3. Add apll12_div_tdmout_b
> 4. Add disable-unused configs
>
> BUG=b:387252012
> TEST=emerge-skywalker chromeos-kernel-6_6
6_6 feels like v6.6, so nope. You need to start working on mainline and
TESTING on mainline.
This also explains a bit all the issues which you copied from downstream
drivers... although they were fixed in v6.6 as well, so maybe not. :/
Best regards,
Krzysztof
Powered by blists - more mailing lists