From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Niklas Cassel <nks@flawful.org>, Andy Gross <agross@kernel.org>,
Niklas Cassel <niklas.cassel@linaro.org>,
linux-arm-msm@vger.kernel.org, amit.kucheria@linaro.org,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 7/7] clk: qcom: apcs-msm8916: use clk_parent_data to specify the parent
Date: Thu, 26 Dec 2019 18:26:52 -0800 [thread overview]
Message-ID: <20191227022652.GH1908628@ripper> (raw)
In-Reply-To: <20191224021636.CF47E20643@mail.kernel.org>
On Mon 23 Dec 18:16 PST 2019, Stephen Boyd wrote:
> Quoting Niklas Cassel (2019-12-20 09:56:16)
> > On Wed, Dec 18, 2019 at 10:23:39PM -0800, Stephen Boyd wrote:
> > > This is odd. The clks could be registered with of_clk_hw_register() but
> > > then we lose the device provider information. Maybe we should search up
> > > one level to the parent node and if that has a DT node but the
> > > clk controller device doesn't we should use that instead?
> >
> > Hello Stephen,
> >
> > Having this in the clk core is totally fine with me,
> > since it solves my problem.
> >
> > Will you cook up a patch, or do you want me to do it?
> >
>
> Can you try the patch I appended to my previous mail? I can write
> something up more proper later this week.
>
Unfortunately we have clocks with no dev, so this fail as below. Adding
a second check for dev != NULL to your oneliner works fine though.
I.e. this ugly hack works fine:
core->of_node = np ? : (dev ? dev_of_node(dev->parent) : NULL);
Regards,
Bjorn
[ 0.000000] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000040
[ 0.000000] Mem abort info:
[ 0.000000] ESR = 0x96000004
[ 0.000000] EC = 0x25: DABT (current EL), IL = 32 bits
[ 0.000000] SET = 0, FnV = 0
[ 0.000000] EA = 0, S1PTW = 0
[ 0.000000] Data abort info:
[ 0.000000] ISV = 0, ISS = 0x00000004
[ 0.000000] CM = 0, WnR = 0
[ 0.000000] [0000000000000040] user address but active_mm is swapper
[ 0.000000] Internal error: Oops: 96000004 [#1] PREEMPT SMP
[ 0.000000] Modules linked in:
[ 0.000000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.5.0-rc2-next-20191220-00017-g359fd8f91acb-dirty #107
[ 0.000000] Hardware name: Qualcomm Technologies, Inc. QCS404 EVB 4000 (DT)
[ 0.000000] pstate: 80000085 (Nzcv daIf -PAN -UAO)
[ 0.000000] pc : __clk_register (drivers/clk/clk.c:3679)
[ 0.000000] lr : __clk_register (drivers/clk/clk.c:3664)
[ 0.000000] sp : ffffdb6871043d70
[ 0.000000] x29: ffffdb6871043d70 x28: ffff00003ddf4518
[ 0.000000] x27: 0000000000000001 x26: 0000000000000008
[ 0.000000] x25: 0000000000000000 x24: 0000000000000000
[ 0.000000] x23: 0000000000000000 x22: 0000000000000000
[ 0.000000] x21: ffff00003d821080 x20: ffffdb6871043e60
[ 0.000000] x19: ffff00003d822000 x18: 0000000000000014
[ 0.000000] x17: 000000006f7295ba x16: 0000000043d45a86
[ 0.000000] x15: 000000005f0037cd x14: 00000000b22e3fc4
[ 0.000000] x13: 0000000000000001 x12: 0000000000000000
[ 0.000000] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
[ 0.000000] x9 : fefefefefefefeff x8 : 7f7f7f7f7f7f7f7f
[ 0.000000] x7 : 6371606e612c6e77 x6 : ffff00003d821109
[ 0.000000] x5 : 0000000000000000 x4 : ffff00003dd9d060
[ 0.000000] x3 : 0000000000000000 x2 : 0000000000000009
[ 0.000000] x1 : ffff00003ddf47b9 x0 : ffffdb68705b0ee0
[ 0.000000] Call trace:
[ 0.000000] __clk_register (drivers/clk/clk.c:3679)
[ 0.000000] clk_hw_register (./include/linux/err.h:60 drivers/clk/clk.c:3760)
[ 0.000000] clk_hw_register_fixed_rate_with_accuracy (drivers/clk/clk-fixed-rate.c:82)
[ 0.000000] _of_fixed_clk_setup (drivers/clk/clk-fixed-rate.c:98 drivers/clk/clk-fixed-rate.c:173)
[ 0.000000] of_fixed_clk_setup (drivers/clk/clk-fixed-rate.c:193)
[ 0.000000] of_clk_init (drivers/clk/clk.c:4856)
[ 0.000000] time_init (arch/arm64/kernel/time.c:59)
[ 0.000000] start_kernel (init/main.c:697)
next prev parent reply other threads:[~2019-12-27 2:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 13:59 [PATCH v3 0/7] Clock changes to support cpufreq on QCS404 Niklas Cassel
2019-11-25 13:59 ` [PATCH v3 2/7] clk: qcom: gcc: limit GPLL0_AO_OUT operating frequency Niklas Cassel
2019-12-19 6:24 ` Stephen Boyd
2019-11-25 13:59 ` [PATCH v3 3/7] clk: qcom: hfpll: register as clock provider Niklas Cassel
2019-12-19 6:24 ` Stephen Boyd
2019-11-25 13:59 ` [PATCH v3 4/7] clk: qcom: hfpll: CLK_IGNORE_UNUSED Niklas Cassel
2019-12-19 6:25 ` Stephen Boyd
2019-11-25 13:59 ` [PATCH v3 5/7] clk: qcom: hfpll: use clk_parent_data to specify the parent Niklas Cassel
2019-12-19 6:25 ` Stephen Boyd
2019-11-25 13:59 ` [PATCH v3 6/7] clk: qcom: apcs-msm8916: silently error out on EPROBE_DEFER Niklas Cassel
2019-12-19 6:25 ` Stephen Boyd
2019-11-25 13:59 ` [PATCH v3 7/7] clk: qcom: apcs-msm8916: use clk_parent_data to specify the parent Niklas Cassel
2019-12-19 6:23 ` Stephen Boyd
2019-12-20 17:22 ` Bjorn Andersson
2019-12-20 17:56 ` Niklas Cassel
2019-12-24 2:16 ` Stephen Boyd
2019-12-27 2:26 ` Bjorn Andersson [this message]
2019-12-30 18:04 ` Stephen Boyd
2020-01-03 7:47 ` Bjorn Andersson
2019-12-18 12:16 ` [PATCH v3 0/7] Clock changes to support cpufreq on QCS404 Niklas Cassel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191227022652.GH1908628@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=niklas.cassel@linaro.org \
--cc=nks@flawful.org \
--cc=sboyd@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).