[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240104100727.xtwn76lhp72ika7i@pengutronix.de>
Date: Thu, 4 Jan 2024 11:07:27 +0100
From: Marco Felsch <m.felsch@...gutronix.de>
To: Frank Li <Frank.li@....com>
Cc: krzysztof.kozlowski@...aro.org, devicetree@...r.kernel.org,
conor+dt@...nel.org, hongxing.zhu@....com,
krzysztof.kozlowski+dt@...aro.org, imx@...ts.linux.dev,
linux-pci@...r.kernel.org, lpieralisi@...nel.org,
linux-kernel@...r.kernel.org, s.hauer@...gutronix.de,
helgaas@...nel.org, linux-imx@....com, kernel@...gutronix.de,
manivannan.sadhasivam@...aro.org, bhelgaas@...gle.com,
shawnguo@...nel.org, kw@...ux.com, festevam@...il.com,
robh@...nel.org, linux-arm-kernel@...ts.infradead.org,
l.stach@...gutronix.de
Subject: Re: [PATCH v7 01/16] PCI: imx6: Simplify clock handling by using
bulk_clk_*() function
On 24-01-03, Frank Li wrote:
> On Tue, Jan 02, 2024 at 09:47:44AM +0100, Marco Felsch wrote:
> > Hi Frank,
> >
> > On 23-12-27, Frank Li wrote:
> > > Refactors the clock handling logic. Adds clk_names[] define in drvdata.
> > > Using clk_bulk*() api simplifies the code.
> >
> > does this influence the clock enable/disable sequence ordering? Just
> > asking to avoid regressions on older platforms which may require some
> > sort of order (e.g. require clock-a before clock-b).
>
> drvdata::clk_names is order of enble sequence. So far we have not found
> the problem.
Okay, thanks.
Regards,
Marco
Powered by blists - more mailing lists