From: linux@rempel-privat.de (Oleksij Rempel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] clk: add clk-asm9260 driver
Date: Sat, 20 Sep 2014 20:06:21 +0200 [thread overview]
Message-ID: <541DC21D.7050303@rempel-privat.de> (raw)
In-Reply-To: <20140918075650.GB29620@piout.net>
Am 18.09.2014 um 09:56 schrieb Alexandre Belloni:
> Hi,
>
> On 18/09/2014 at 08:46:57 +0200, Oleksij Rempel wrote :
>> Am 17.09.2014 um 15:54 schrieb Alexandre Belloni:
>>> Hi,
>>>
>>> Please have a look at https://lkml.org/lkml/2014/5/14/598 which describe
>>> the preferred way of implementing clocks in the CCF where you only
>>> declare the clock generator in the DT instead of each separate clocks.
>>
>> hm... if i see it correctly. i will need to move almost everything from
>> DT to clk-driver. And i will need to create separate driver for other
>> SoC provided by AlphaScale. On other side with current (generic) driver
>> i will need only to change DT and it will work.
>>
>> May be instead of going qcom way, it will be better to have generic
>> gate, div and mux bindings for DT? Sure it will make DT a bit fuzzy, but
>> it will dramatically reduce kernel code and reduce the time of providing
>> code to upstream.
>>
>> I don't think drivers/clk/qcom/gcc-msm8974.c is less complicated solution.
>
> IT is not less complicated but it is more flexible (for exemple when
> setting flags on individual clocks, like CLK_SET_RATE_PARENT or
> CLK_IGNORE_UNUSED). Describing all the individual clocks in DT is a
> mistake we made in at91 and it will definitely bother you in the future,
> for example when you realize that your clock controller is also taking
> care of reset or power management.
>
> Also, this is the kind of driver you write only once per SoC so it is
> about the same doing it in DT or in C with the added advantage that
> doing it in C takes less memory and is probably faster.
>
> You can have a look at how it has been done for the berlin SoCs to see
> how you can easily reuse code between drivers.
What is the correct way to handle/define i2s MCLK input? I have I2S mux
clock with choice of 3 sources: Xtal, PLL and MCLK. One of pins can be
configured as MCLK src. Should i define fixedrate-clk?
--
Regards,
Oleksij
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140920/0b0c4daf/attachment.sig>
next prev parent reply other threads:[~2014-09-20 18:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 22:13 [PATCH 0/7] initial suport for Alpscale ASM9260 Oleksij Rempel
2014-09-13 22:13 ` [PATCH 1/7] ARM: add mach-asm9260 Oleksij Rempel
2014-09-14 7:12 ` Jason Cooper
2014-09-14 7:45 ` Oleksij Rempel
2014-09-14 9:05 ` Jason Cooper
2014-09-17 13:46 ` Alexandre Belloni
2014-09-17 13:53 ` Nicolas Ferre
2014-09-18 6:29 ` Oleksij Rempel
2014-09-13 22:13 ` [PATCH 2/7] add include/debug/asm9260.S Oleksij Rempel
2014-09-13 22:13 ` [PATCH 3/7] ARM: dts: add DT for Alpscale ASM9260 SoC Oleksij Rempel
2014-09-13 22:13 ` [PATCH 4/7] clk: add clk-asm9260 driver Oleksij Rempel
2014-09-17 13:54 ` Alexandre Belloni
2014-09-18 6:46 ` Oleksij Rempel
2014-09-18 7:56 ` Alexandre Belloni
2014-09-18 8:46 ` Oleksij Rempel
2014-09-20 18:06 ` Oleksij Rempel [this message]
2014-09-20 18:43 ` Alexandre Belloni
2014-09-13 22:13 ` [PATCH 5/7] clocksource: add asm9260_timer driver Oleksij Rempel
2014-09-13 22:13 ` [PATCH 6/7] irqchip: add irq-asm9260 driver Oleksij Rempel
2014-09-14 7:37 ` Jason Cooper
2014-09-15 5:52 ` Oleksij Rempel
2014-09-17 12:59 ` Jason Cooper
2014-09-13 22:13 ` [PATCH 7/7] tty/serial: add asm9260-serial driver Oleksij Rempel
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=541DC21D.7050303@rempel-privat.de \
--to=linux@rempel-privat.de \
--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 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.