From: Randy Dunlap <rdunlap@infradead.org>
To: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: Re: rockchip_i2s_tdm.c:undefined reference to `clk_set_parent'
Date: Sat, 11 Dec 2021 11:47:04 -0800 [thread overview]
Message-ID: <3f53c496-cddc-7d2d-cf2d-a492eb5be9b2@infradead.org> (raw)
In-Reply-To: <13326272.At7iLaMNiz@archbook>
Hi--
On 12/7/21 03:32, Nicolas Frattaroli wrote:
> On Montag, 6. Dezember 2021 23:46:38 CET kernel test robot wrote:
>> [...]
>>
>> All errors (new ones prefixed by >>):
>>
>> mips-linux-ld: sound/soc/jz4740/jz4740-i2s.o: in function `jz4740_i2s_set_sysclk':
>> jz4740-i2s.c:(.text+0x3ec): undefined reference to `clk_set_parent'
>> mips-linux-ld: jz4740-i2s.c:(.text+0x44c): undefined reference to `clk_set_parent'
>> mips-linux-ld: sound/soc/rockchip/rockchip_i2s_tdm.o: in function `rockchip_i2s_tdm_calibrate_mclk.isra.0':
>>>> rockchip_i2s_tdm.c:(.text+0x10d4): undefined reference to `clk_set_parent'
>>>> mips-linux-ld: rockchip_i2s_tdm.c:(.text+0x1180): undefined reference to `clk_set_parent'
>>
>
> According to some previous conversations I've stumbled upon[1],
> this appears to be due to certain MIPS configurations not
> implementing the clock API properly, so they don't provide a
> clk_set_parent despite advertising that they have support for
> clocks.
>
> So my question is: do I need to care about this? This hardware
> will never be used on MIPS, and a lot of other drivers (as seen in
> the errors snippet from the test robot) have the same issue, and
> the problem is most likely not in my driver but in that specific
> configuration's clock API implementation.
>
>
> [1]: https://lore.kernel.org/lkml/8a41b718-a6f6-6b7f-1699-18ab619884c3@infradead.org/
Yes, AFAIK this is fixed by:
commit fc1aabb08886
Author: Randy Dunlap <rdunlap@infradead.org>
Date: Sun Nov 14 17:20:51 2021 -0800
mips: lantiq: add support for clk_get_parent()
I can't reproduce this build error with the provided config file
in a current kernel tree.
--
~Randy
prev parent reply other threads:[~2021-12-11 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 22:46 kernel test robot
2021-12-07 11:32 ` Nicolas Frattaroli
2021-12-07 13:11 ` Mark Brown
2021-12-11 19:47 ` Randy Dunlap [this message]
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=3f53c496-cddc-7d2d-cf2d-a492eb5be9b2@infradead.org \
--to=rdunlap@infradead.org \
--cc=broonie@kernel.org \
--cc=frattaroli.nicolas@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/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
all inboxes | Powered by JetHome®