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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 21 Oct 2009 00:14:51 +0200
From:	Linus Walleij <>
To:	Chaithrika U S <>
Subject: Re: [PATCH] davinci: MMC: add cpufreq support

2009/10/20 Chaithrika U S <>:

> Add cpufreq support to MMC driver. The clock divider value has to be
> modified according to the controller input frequency.
> (...)
> @@ -1040,6 +1052,52 @@ static struct mmc_host_ops mmc_davinci_ops = {
>  /*----------------------------------------------------------------------*/
> +static int mmc_davinci_cpufreq_transition(struct notifier_block *nb,
> +                                    unsigned long val, void *data)
> +{
> +       struct mmc_davinci_host *host;
> +       unsigned int mmc_pclk;
> +       struct mmc_host *mmc;
> +       unsigned long flags;
> +
> +       host = container_of(nb, struct mmc_davinci_host, freq_transition);
> +       mmc = host->mmc;
> +       mmc_pclk = clk_get_rate(host->clk);
> +
> +       if (val == CPUFREQ_POSTCHANGE) {
> +               spin_lock_irqsave(&mmc->lock, flags);
> +               host->mmc_input_clk = mmc_pclk;
> +               calculate_clk_divider(mmc, &mmc->ios);
> +               spin_unlock_irqrestore(&mmc->lock, flags);
> +       }
> +
> +       return 0;
> +}

Now the way I understand it CPUfreq is about rising/lowering the
frequency of the *CPU* when the load of the system goes up/down.

I highly suspect that there is no general rule that davinci's host->clk
will actually change just because the CPU changes frequency?

I don't know enough about davinci to tell but I suspect there are
system-wide operating points hidden behind this and CPUfreq
is being (ab)used for changing and notifying the system frequency
overall. Some of these transitions include changing the MMC clock
so if you simply broadcast them all?

I really believe this is just masking the problem that the clk
framework need support of real clk notifiers that can notify clk
users pre/post a clk change. This is really what you want for a
driver like this.

Now I don't know the davinci consensus around these things,
do you always use CPUfreq like this, for changing frequencies
of clocks that are not CPU clocks at all?

I have similar code boiling for the MMCI/PL180 PrimeCell but
I just cannot submit that because the PrimeCell is generic and
there is no way I can implicitly correlate the CPU clk with the
MMCI host clk like this, so I have to wait for real clock notifiers
(or implement them myself...)

Linus Walleij
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists