[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161007033346.GA3954@vireshk-i7>
Date: Fri, 7 Oct 2016 09:03:46 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Markus Mayer <markus.mayer@...adcom.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
Broadcom Kernel List <bcm-kernel-feedback-list@...adcom.com>,
Device Tree List <devicetree@...r.kernel.org>,
Power Management List <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH v2 2/3] cpufreq: brcmstb-avs-cpufreq: AVS CPUfreq
driver for Broadcom STB SoCs
On 06-10-16, 07:51, Markus Mayer wrote:
> During early development, when the driver couldn't fully register, I
> would see the init() function called four times, i.e. once for each
> core. If the first call succeeded, that was it. It would only get
> called once. But if it failed, all cores would try to register. And I
> wanted to avoid spilling the same error message four times.
This is the current behavior of the cpufreq core.
> I'll look at that again. It may have had something to do with how the
> driver worked back then. If it doesn't happen anymore, I'll just get
> rid of this code.
I don't think so, but again, we don't need to have special code to save few
lines which get printed only in the rare case of errors.
--
viresh
Powered by blists - more mailing lists