From: York Sun <yorksun@freescale.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>, <linux-clk@vger.kernel.org>
Subject: What's the proper use of con_id in clkdev
Date: Mon, 5 Oct 2015 12:51:44 -0700 [thread overview]
Message-ID: <5612D4D0.30104@freescale.com> (raw)
Michael and Stephen,
Can you help me to understand "#define MAX_CON_ID 16" in clkdev.c? I am trying
to use clk_get() to acquire the clock with its name. This fails when the clock
name is more than 15 characters. I traced it to this macro.
The reason of using clk_get() is I don't have device tree for my platform until
device tree overlay is officially supported. So I use clkdev_add() in the clock
driver.
So my issue is with the MAX_CON_ID. Is there a reason to limit it to 16?
Wouldn't it be better to use kstrdup() in vclkdev_alloc()?
York
next reply other threads:[~2015-10-05 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 19:51 York Sun [this message]
2015-10-06 19:44 ` What's the proper use of con_id in clkdev Stephen Boyd
2015-10-06 19:50 ` Russell King - ARM Linux
2015-10-06 19:53 ` York Sun
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=5612D4D0.30104@freescale.com \
--to=yorksun@freescale.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.