From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] net: mvneta: mmc: get optional axi clk
Date: Wed, 20 Jan 2016 12:03:03 +0100 [thread overview]
Message-ID: <569F6967.9040302@gmail.com> (raw)
In-Reply-To: <20160120174223.53ccc36b@xhacker>
On 01/20/2016 10:42 AM, Jisheng Zhang wrote:
> On Wed, 20 Jan 2016 10:31:18 +0100 Sebastian Hesselbarth wrote:
>
>> On January 20, 2016 9:15:22 AM Jisheng Zhang wrote:
>>
>>> Some platforms may provide more than one clk for the mvneta IP, for
>>> example Marvell BG4CT provides "core" clk for the mac core, and
>>> "axi" clk for the AXI bus logic. Obviously this "axi" clk also need to
>>> be enabled. This patch adds this optional "axi" clk support.
>>
>> Jisheng,
>>
>> although I do not expect mvneta to appear on a non-AXI bus
>> anytime soon, how about naming the clock "bus" instead?
>
> Good question. IIRC, this IP expects AXI bus, but I'll check with HW people.
Actually, I am quite sure the current IP requires AXI. But my comment
was more about to make the binding a little bit more flexible to
_future_ variants/SoCs we may stumble upon.
Naming the clock "bus" or "dma" will work for the current _and_ future
IPs, while "axi" may not.
Sebastian
>>
>> If you know the clock is only required for bus master DMA but
>> not for register access, "dma" would be an even better name.
>>
>> Sebastian
>>
>>
>>> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
>>> ---
>>> drivers/net/ethernet/marvell/mvneta.c | 8 ++++++++
>>> 1 file changed, 8 insertions(+)
>>>
>>> diff --git a/drivers/net/ethernet/marvell/mvneta.c
>>> b/drivers/net/ethernet/marvell/mvneta.c
>>> index aca0a73..6bb709a 100644
>>> --- a/drivers/net/ethernet/marvell/mvneta.c
>>> +++ b/drivers/net/ethernet/marvell/mvneta.c
>>> @@ -373,6 +373,8 @@ struct mvneta_port {
>>>
>>> /* Core clock */
>>> struct clk *clk;
>>> + /* AXI clock */
>>> + struct clk *clk_axi;
>>> u8 mcast_count[256];
>>> u16 tx_ring_size;
>>> u16 rx_ring_size;
>>> @@ -3615,6 +3617,10 @@ static int mvneta_probe(struct platform_device *pdev)
>>>
>>> clk_prepare_enable(pp->clk);
>>>
>>> + pp->clk_axi = devm_clk_get(&pdev->dev, "axi");
>>> + if (!IS_ERR(pp->clk_axi))
>>> + clk_prepare_enable(pp->clk_axi);
>>> +
>>> res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>>> pp->base = devm_ioremap_resource(&pdev->dev, res);
>>> if (IS_ERR(pp->base)) {
>>> @@ -3727,6 +3733,7 @@ err_free_ports:
>>> free_percpu(pp->ports);
>>> err_clk:
>>> clk_disable_unprepare(pp->clk);
>>> + clk_disable_unprepare(pp->clk_axi);
>>> err_put_phy_node:
>>> of_node_put(phy_node);
>>> err_free_irq:
>>> @@ -3744,6 +3751,7 @@ static int mvneta_remove(struct platform_device *pdev)
>>>
>>> unregister_netdev(dev);
>>> clk_disable_unprepare(pp->clk);
>>> + clk_disable_unprepare(pp->clk_axi);
>>> free_percpu(pp->ports);
>>> free_percpu(pp->stats);
>>> irq_dispose_mapping(dev->irq);
>>> --
>>> 2.7.0.rc3
>>>
>>
>>
>
next prev parent reply other threads:[~2016-01-20 11:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 8:06 [PATCH 0/4] net: mvneta: support more than one clk Jisheng Zhang
2016-01-20 8:06 ` [PATCH 1/4] net: mvneta: sort the headers in alphabetic order Jisheng Zhang
2016-01-20 8:46 ` Thomas Petazzoni
2016-01-20 8:06 ` [PATCH 2/4] net: mvneta: Try to get named core clock first Jisheng Zhang
2016-01-20 8:47 ` Thomas Petazzoni
2016-01-20 8:06 ` [PATCH 3/4] net: mvneta: mmc: get optional axi clk Jisheng Zhang
2016-01-20 8:51 ` Thomas Petazzoni
2016-01-20 8:53 ` Jisheng Zhang
2016-01-20 9:31 ` Sebastian Hesselbarth
2016-01-20 9:42 ` Jisheng Zhang
2016-01-20 11:03 ` Sebastian Hesselbarth [this message]
2016-01-20 11:11 ` Jisheng Zhang
2016-01-20 8:06 ` [PATCH 4/4] net: mvneta: update clocks property and document additional clock-names Jisheng Zhang
2016-01-20 9:07 ` Thomas Petazzoni
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=569F6967.9040302@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).