| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20181129170332.76971464@xps13>
Date: Thu, 29 Nov 2018 17:03:32 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Maxime Ripard <maxime.ripard@...tlin.com>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Russell King <linux@...linux.org.uk>,
Antoine Tenart <antoine.tenart@...tlin.com>,
Gregory Clement <gregory.clement@...tlin.com>,
linux-kernel@...r.kernel.org,
Maxime Chevallier <maxime.chevallier@...tlin.com>,
Nadav Haklai <nadavh@...vell.com>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 2/2] clk: core: link consumer with clock driver
Hi Maxime,
Maxime Ripard <maxime.ripard@...tlin.com> wrote on Tue, 27 Nov 2018
13:38:58 +0100:
> Hi Miquel,
>
> On Thu, Nov 22, 2018 at 10:22:12PM +0100, Miquel Raynal wrote:
> > One major concern when, for instance, suspending/resuming a platform
> > is to never access registers before the underlying clock has been
> > resumed, otherwise most of the time the kernel will just crash. One
> > solution is to use syscore operations when registering clock drivers
> > suspend/resume callbacks. One problem of using syscore_ops is that the
> > suspend/resume scheduling will depend on the order of the
> > registrations, which brings (unacceptable) randomness in the process.
> >
> > A feature called device links has been introduced to handle such
> > situation. It creates dependencies between consumers and providers,
> > enforcing e.g. the suspend/resume order when needed. Such feature is
> > already in use for regulators.
> >
> > Add device links support in the clock subsystem by creating/deleting
> > the links at get/put time.
> >
> > Example of a boot (ESPRESSObin, A3700 SoC) with devices linked to clocks:
> > ahci-mvebu d00e0000.sata: Linked as a consumer to d0013000.nb-periph-clk
> > mvneta d0030000.ethernet: Linked as a consumer to d0018000.sb-periph-clk
> > xhci-hcd d0058000.usb: Linked as a consumer to d0018000.sb-periph-clk
> > xenon-sdhci d00d0000.sdhci: Linked as a consumer to d0013000.nb-periph-clk
> > xenon-sdhci d00d0000.sdhci: Dropping the link to d0013000.nb-periph-clk
> > advk-pcie d0070000.pcie: Linked as a consumer to d0018000.sb-periph-clk
> > xenon-sdhci d00d0000.sdhci: Linked as a consumer to d0013000.nb-periph-clk
> > xenon-sdhci d00d0000.sdhci: Linked as a consumer to regulator.1
> > cpu cpu0: Linked as a consumer to d0013000.nb-periph-clk
> > cpu cpu0: Dropping the link to d0013000.nb-periph-clk
> > cpu cpu0: Linked as a consumer to d0013000.nb-periph-clk
> >
> > Signed-off-by: Miquel Raynal <miquel.raynal@...tlin.com>
> > ---
> > drivers/clk/clk.c | 20 ++++++++++++++++++++
> > drivers/clk/clkdev.c | 13 ++++++++++---
> > include/linux/clk-provider.h | 2 ++
> > 3 files changed, 32 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> > index b799347c5fd6..33a0f2b0533a 100644
> > --- a/drivers/clk/clk.c
> > +++ b/drivers/clk/clk.c
> > @@ -90,6 +90,7 @@ struct clk {
> > unsigned long max_rate;
> > unsigned int exclusive_count;
> > struct hlist_node clks_node;
> > + struct device_link *link;
> > };
> >
> > /*** runtime pm ***/
> > @@ -262,6 +263,25 @@ struct clk_hw *__clk_get_hw(struct clk *clk)
> > }
> > EXPORT_SYMBOL_GPL(__clk_get_hw);
> >
> > +void __clk_device_link(struct device *consumer, struct clk *clk)
> > +{
> > + if (!consumer || !clk || !clk->core)
> > + return;
> > +
> > + clk->link = device_link_add(consumer, clk->core->dev,
> > + DL_FLAG_STATELESS);
> > +}
> > +EXPORT_SYMBOL_GPL(__clk_device_link);
> > +
> > +void __clk_device_unlink(struct clk *clk)
> > +{
> > + if (!clk || !clk->link)
> > + return;
> > +
> > + device_link_del(clk->link);
> > +}
> > +EXPORT_SYMBOL_GPL(__clk_device_unlink);
> > +
> > unsigned int clk_hw_get_num_parents(const struct clk_hw *hw)
> > {
> > return hw->core->num_parents;
> > diff --git a/drivers/clk/clkdev.c b/drivers/clk/clkdev.c
> > index 9ab3db8b3988..fccfd4c01457 100644
> > --- a/drivers/clk/clkdev.c
> > +++ b/drivers/clk/clkdev.c
> > @@ -194,20 +194,27 @@ EXPORT_SYMBOL(clk_get_sys);
> > struct clk *clk_get(struct device *dev, const char *con_id)
> > {
> > const char *dev_id = dev ? dev_name(dev) : NULL;
> > - struct clk *clk;
> > + struct clk *clk = NULL;
> >
> > if (dev && dev->of_node) {
> > clk = __of_clk_get_by_name(dev->of_node, dev_id, con_id);
> > - if (!IS_ERR(clk) || PTR_ERR(clk) == -EPROBE_DEFER)
> > + if (PTR_ERR(clk) == -EPROBE_DEFER)
> > return clk;
> > }
> >
> > - return clk_get_sys(dev_id, con_id);
> > + if (IS_ERR_OR_NULL(clk))
> > + clk = clk_get_sys(dev_id, con_id);
> > +
> > + if (!IS_ERR(clk))
> > + __clk_device_link(dev, clk);
> > +
> > + return clk;
>
> I think this doesn't address all the cases. In your case, where you
> have one consumer that is not a clock, and one provider that is a
> clock, it works just fine.
>
> However, if you have clocks providers chained, for example with one
> oscillator, a clock controller, and a device, the link will be created
> between the device and the controller, but there will be no link
> between the controller and the oscillator.
Indeed, there is not clock_get() in this case so you are right, a link
is missing if we want to track dependencies between clocks.
>
> Adding a link in __clk_init_parent looks like it would address that
> case.
I will add one, thanks for the pointer.
>
> Maxime
>
I think device links must be managed in the following situations:
* A device gets a clock -> add a link between the device and the clock,
save it in 'struct clk'.
* A device puts a clock -> remove the above link.
* A clock gets registered -> link the core clock with the parent core
clock.
* A clock gets reparentized -> remove the above link and if there is a
new parent, link the core clock to the parent core clock.
* A clock gets deregistered -> remove the link with the parent core
clock if any and remove the link with each child clock if any (this
will be done automatically because each child will get reparentized
first).
I assume that a clock getting deregistered is not an input source for
any device anymore and thus there is already no more link to destroy on
this regard.
Thanks,
Miquèl
Powered by blists - more mailing lists