From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] DW SPI: Get clock value from Device Tree
Date: Tue, 17 Oct 2017 17:03:59 +0200 [thread overview]
Message-ID: <c0f7a8af-3f85-b380-402b-adea978fc47c@denx.de> (raw)
In-Reply-To: <4881796E12491D4BB15146FE0209CE6467F9F602@DE02WEMBXB.internal.synopsys.com>
On 10/17/2017 04:57 PM, Alexey Brodkin wrote:
> Hi Jagan,
>
>> -----Original Message-----
>> From: Eugeniy Paltsev [mailto:paltsev at synopsys.com]
>> Sent: Tuesday, October 17, 2017 4:33 PM
>> To: jagannadh.teki at gmail.com
>> Cc: u-boot at lists.denx.de; uboot-snps-arc at synopsys.com
>> Subject: [uboot-snps-arc] Re: [PATCH v2] DW SPI: Get clock value from Device Tree
>>>
>>> How hard it is to make others to use clock manager? do you have any list?
>>
>> clock_manager.h is an old (and non-generic) way to deal with different clocks.
>> For example in SOCFPGA_GEN5 and SOCFPGA_ARRIA10 clock_manager.h provides
>> cm_get_spi_controller_clk_hz function to deal with spi controller clock.
>>
>> But today we have another, linux-like alternative: to bind clocks via device tree
>> and manipulate with clocks via generic functions provided by clk.h
>>
>> In this patch I added option to get clock via device tree using standard bindings
>> and restrict clock_manager.h functions usage only to targets which still use it,
>> so new targets can simply bind clock via device tree and they do not need to
>> implement/define something in clock_manager.h
>>
>> So we don't need to make others to use clock manager :)
>
> Maybe it worth trying the other way around and think about switching SOCFPGA platforms to
> generic clk framework?
That'd be real neat.
> Marek, any plans for that?
Patches welcome, +CC Dinh.
> -Alexey
>
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2017-10-17 15:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 15:18 [U-Boot] [PATCH v2] DW SPI: Get clock value from Device Tree Eugeniy Paltsev
2017-10-16 17:07 ` Jagan Teki
2017-10-17 13:32 ` Eugeniy Paltsev
2017-10-17 14:57 ` Alexey Brodkin
2017-10-17 15:02 ` Jagan Teki
2017-10-19 15:36 ` Eugeniy Paltsev
2017-10-19 15:51 ` Marek Vasut
2017-10-19 18:20 ` Dinh Nguyen
2017-10-23 11:43 ` Eugeniy Paltsev
2017-10-24 6:08 ` Marek Vasut
2017-10-24 9:52 ` Jagan Teki
2017-10-25 6:50 ` Marek Vasut
2017-10-27 13:54 ` Eugeniy Paltsev
2017-10-28 11:39 ` Marek Vasut
2017-10-30 6:04 ` Jagan Teki
2017-10-30 10:54 ` Marek Vasut
2017-10-30 11:36 ` Jagan Teki
2017-10-30 11:42 ` Marek Vasut
2017-10-31 8:27 ` Jagan Teki
2017-10-31 9:33 ` Marek Vasut
2017-10-17 15:03 ` Marek Vasut [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=c0f7a8af-3f85-b380-402b-adea978fc47c@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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.