From: Tero Kristo <t-kristo@ti.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: <linux-omap@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<tony@atomide.com>, <paul@pwsan.com>, <sboyd@codeaurora.org>,
<mturquette@baylibre.com>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCHv3 2/7] clk: ti: add clkdev get helper
Date: Tue, 12 Jul 2016 18:18:01 +0300 [thread overview]
Message-ID: <57850A29.4010806@ti.com> (raw)
In-Reply-To: <20160712102228.GE5783@n2100.arm.linux.org.uk>
On 12/07/16 13:22, Russell King - ARM Linux wrote:
> On Thu, Jun 30, 2016 at 05:13:33PM +0300, Tero Kristo wrote:
>> /**
>> + * ti_clk_get - lookup a TI clock handle
>> + * @dev_id: device to lookup clock for
>> + * @con_id: connection ID to find
>> + *
>> + * Searches for a TI clock handle based on the DT node name.
>> + * Returns the pointer to the clock handle, or ERR_PTR in failure.
>> + */
>> +static struct clk *ti_clk_get(const char *dev_id, const char *con_id)
>> +{
>> + struct of_phandle_args clkspec;
>> + struct device_node *node;
>> + struct clk *clk;
>> +
>> + /* Only check for cases of type clk_get_sys(NULL, "xyz") */
>> + if (dev_id || !con_id)
>> + return ERR_PTR(-ENOENT);
>> +
>> + if (of_have_populated_dt()) {
>> + node = of_find_node_by_name(NULL, con_id);
>> + clkspec.np = node;
>> + clk = of_clk_get_from_provider(&clkspec);
>> +
>> + if (!IS_ERR(clk))
>> + return clk;
>> + }
>> +
>> + return ERR_PTR(-ENOENT);
>> +}
>
> I _really_ don't like this. This takes us back to the totally broken
> idea, that's already been proven to be greatly harmful in OMAP land,
> that the "con_id" is not a _DEVICE SPECIFIC CONNECTION NAME_ but is a
> CLOCK NAME. The connection ID is supposed to be a static string in
> the requestor of the clock, not some random string picked out from
> DT.
What is the harm in that actually? I have most likely missed some
discussion but please educate me. The problem is, we are already using
this convention all over the place in the kernel (not only OMAPs), and
trying to clean up the kernel requires some intermediate steps being
taken, otherwise we end up doing all the clean-ups in a single massive
patch I fear (change all the hwmod data + clock data + any
implementations related to these at the same time.)
This specific implementation should be possible to deprecate later once
the hwmod database is gone btw, and is mostly required for hwmod data
only (+ OMAP timer implementation, maybe some others.) The biggest
abuser of clk_get interface atm is omap-hwmod.
>
> This series started out with the assertion that the new clkdev hook
> was to avoid registering lots of clock aliases, but it seems with
> this patch we're going to end up with lots of specifically named
> nodes in DT instead. It's just moving the problem to somewhere else.
That is true, it will end up adding new DT nodes. However, as OMAP
already is doing this extensively, I wonder what would be the
alternative. Maybe move all the clock data back to kernel space to
increase the size of multi-v7 builds?
-Tero
WARNING: multiple messages have this Message-ID (diff)
From: Tero Kristo <t-kristo@ti.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
tony@atomide.com, paul@pwsan.com, sboyd@codeaurora.org,
mturquette@baylibre.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv3 2/7] clk: ti: add clkdev get helper
Date: Tue, 12 Jul 2016 18:18:01 +0300 [thread overview]
Message-ID: <57850A29.4010806@ti.com> (raw)
In-Reply-To: <20160712102228.GE5783@n2100.arm.linux.org.uk>
On 12/07/16 13:22, Russell King - ARM Linux wrote:
> On Thu, Jun 30, 2016 at 05:13:33PM +0300, Tero Kristo wrote:
>> /**
>> + * ti_clk_get - lookup a TI clock handle
>> + * @dev_id: device to lookup clock for
>> + * @con_id: connection ID to find
>> + *
>> + * Searches for a TI clock handle based on the DT node name.
>> + * Returns the pointer to the clock handle, or ERR_PTR in failure.
>> + */
>> +static struct clk *ti_clk_get(const char *dev_id, const char *con_id)
>> +{
>> + struct of_phandle_args clkspec;
>> + struct device_node *node;
>> + struct clk *clk;
>> +
>> + /* Only check for cases of type clk_get_sys(NULL, "xyz") */
>> + if (dev_id || !con_id)
>> + return ERR_PTR(-ENOENT);
>> +
>> + if (of_have_populated_dt()) {
>> + node = of_find_node_by_name(NULL, con_id);
>> + clkspec.np = node;
>> + clk = of_clk_get_from_provider(&clkspec);
>> +
>> + if (!IS_ERR(clk))
>> + return clk;
>> + }
>> +
>> + return ERR_PTR(-ENOENT);
>> +}
>
> I _really_ don't like this. This takes us back to the totally broken
> idea, that's already been proven to be greatly harmful in OMAP land,
> that the "con_id" is not a _DEVICE SPECIFIC CONNECTION NAME_ but is a
> CLOCK NAME. The connection ID is supposed to be a static string in
> the requestor of the clock, not some random string picked out from
> DT.
What is the harm in that actually? I have most likely missed some
discussion but please educate me. The problem is, we are already using
this convention all over the place in the kernel (not only OMAPs), and
trying to clean up the kernel requires some intermediate steps being
taken, otherwise we end up doing all the clean-ups in a single massive
patch I fear (change all the hwmod data + clock data + any
implementations related to these at the same time.)
This specific implementation should be possible to deprecate later once
the hwmod database is gone btw, and is mostly required for hwmod data
only (+ OMAP timer implementation, maybe some others.) The biggest
abuser of clk_get interface atm is omap-hwmod.
>
> This series started out with the assertion that the new clkdev hook
> was to avoid registering lots of clock aliases, but it seems with
> this patch we're going to end up with lots of specifically named
> nodes in DT instead. It's just moving the problem to somewhere else.
That is true, it will end up adding new DT nodes. However, as OMAP
already is doing this extensively, I wonder what would be the
alternative. Maybe move all the clock data back to kernel space to
increase the size of multi-v7 builds?
-Tero
WARNING: multiple messages have this Message-ID (diff)
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 2/7] clk: ti: add clkdev get helper
Date: Tue, 12 Jul 2016 18:18:01 +0300 [thread overview]
Message-ID: <57850A29.4010806@ti.com> (raw)
In-Reply-To: <20160712102228.GE5783@n2100.arm.linux.org.uk>
On 12/07/16 13:22, Russell King - ARM Linux wrote:
> On Thu, Jun 30, 2016 at 05:13:33PM +0300, Tero Kristo wrote:
>> /**
>> + * ti_clk_get - lookup a TI clock handle
>> + * @dev_id: device to lookup clock for
>> + * @con_id: connection ID to find
>> + *
>> + * Searches for a TI clock handle based on the DT node name.
>> + * Returns the pointer to the clock handle, or ERR_PTR in failure.
>> + */
>> +static struct clk *ti_clk_get(const char *dev_id, const char *con_id)
>> +{
>> + struct of_phandle_args clkspec;
>> + struct device_node *node;
>> + struct clk *clk;
>> +
>> + /* Only check for cases of type clk_get_sys(NULL, "xyz") */
>> + if (dev_id || !con_id)
>> + return ERR_PTR(-ENOENT);
>> +
>> + if (of_have_populated_dt()) {
>> + node = of_find_node_by_name(NULL, con_id);
>> + clkspec.np = node;
>> + clk = of_clk_get_from_provider(&clkspec);
>> +
>> + if (!IS_ERR(clk))
>> + return clk;
>> + }
>> +
>> + return ERR_PTR(-ENOENT);
>> +}
>
> I _really_ don't like this. This takes us back to the totally broken
> idea, that's already been proven to be greatly harmful in OMAP land,
> that the "con_id" is not a _DEVICE SPECIFIC CONNECTION NAME_ but is a
> CLOCK NAME. The connection ID is supposed to be a static string in
> the requestor of the clock, not some random string picked out from
> DT.
What is the harm in that actually? I have most likely missed some
discussion but please educate me. The problem is, we are already using
this convention all over the place in the kernel (not only OMAPs), and
trying to clean up the kernel requires some intermediate steps being
taken, otherwise we end up doing all the clean-ups in a single massive
patch I fear (change all the hwmod data + clock data + any
implementations related to these at the same time.)
This specific implementation should be possible to deprecate later once
the hwmod database is gone btw, and is mostly required for hwmod data
only (+ OMAP timer implementation, maybe some others.) The biggest
abuser of clk_get interface atm is omap-hwmod.
>
> This series started out with the assertion that the new clkdev hook
> was to avoid registering lots of clock aliases, but it seems with
> this patch we're going to end up with lots of specifically named
> nodes in DT instead. It's just moving the problem to somewhere else.
That is true, it will end up adding new DT nodes. However, as OMAP
already is doing this extensively, I wonder what would be the
alternative. Maybe move all the clock data back to kernel space to
increase the size of multi-v7 builds?
-Tero
next prev parent reply other threads:[~2016-07-12 15:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 14:13 [PATCHv3 0/7] clk: ti add support for hwmod clk type Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` [PATCHv3 1/7] clkdev: add helper registration API Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` [PATCHv3 2/7] clk: ti: add clkdev get helper Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-07-12 10:22 ` Russell King - ARM Linux
2016-07-12 10:22 ` Russell King - ARM Linux
2016-07-12 15:18 ` Tero Kristo [this message]
2016-07-12 15:18 ` Tero Kristo
2016-07-12 15:18 ` Tero Kristo
2016-07-12 15:34 ` Russell King - ARM Linux
2016-07-12 15:34 ` Russell King - ARM Linux
2016-07-12 15:49 ` Tero Kristo
2016-07-12 15:49 ` Tero Kristo
2016-07-12 15:49 ` Tero Kristo
2016-07-12 17:40 ` Michael Turquette
2016-07-12 17:40 ` Michael Turquette
2016-07-12 17:40 ` Michael Turquette
2016-06-30 14:13 ` [PATCHv3 3/7] clk: ti: remove un-used definitions from public clk_hw_omap struct Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` [PATCHv3 4/7] clk: ti: mux: export mux clock APIs locally Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` [PATCHv3 5/7] clk: ti: am33xx: fix timer3/6 init time setup for module clocks Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` [PATCHv3 6/7] dt-bindings: clk: ti: Document module clock type Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` [PATCHv3 7/7] clk: ti: add support for omap4 module clocks Tero Kristo
2016-06-30 14:13 ` Tero Kristo
2016-06-30 14:13 ` Tero Kristo
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=57850A29.4010806@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=paul@pwsan.com \
--cc=sboyd@codeaurora.org \
--cc=tony@atomide.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 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.