From: s.trumtrar@pengutronix.de (Steffen Trumtrar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Socfpga: clk: trivial fixes and cleanup
Date: Tue, 12 Nov 2013 08:40:28 +0100 [thread overview]
Message-ID: <20131112074028.GW28790@pengutronix.de> (raw)
In-Reply-To: <5281A332.6060300@gmail.com>
Hi Dinh,
On Mon, Nov 11, 2013 at 09:40:34PM -0600, Dinh Nguyen wrote:
>
> On 11/11/13 6:12 PM, Dinh Nguyen wrote:
> > Hi Steffen,
> >
> > On Thu, 2013-11-07 at 16:07 +0100, Steffen Trumtrar wrote:
> >> Hi!
> >>
> >> This series includes two trivial fixes to the code (1,2),
> >> then goes on to split the single clk.c file up into clock-type
> >> specific files (3) and finally adds a divider to the peripheral
> >> clock path.
> >>
> >> The patches are rebased to the for-next branch of
> >>
> >> git://git.rocketboards.org/linux-socfpga-next.git
> >>
> >> Regards,
> >> Steffen
> >>
> >> Steffen Trumtrar (4):
> >> ARM: socfpga: clk: remove unused field
> >> ARM: socfpga: clk: fix define typo
> > The first two patches are fine.
> >
> >> ARM: socfpga: clk: split clk code
> >> ARM: socfpga: clk: add clk_divider to periph
> > These two patches are causing the ethernet driver to not be able to grab
> > the correct clock during probe.
> >
> > Lets wait for 3.13-rc1 and I will push a new for-next that will be more
> > up-to-date.
>
Hm, okay. It works fine on my SoCKit. But maybe I missed something in the
split up.
> Also the values do not look correct with your patch:
>
> per_nand_mmc_clk 1 1 52631578
> nand_clk 0 0 13157894
> nand_x_clk 0 0 52631578
> sdmmc_clk 1 1 52631578
>
> Without your patch:
>
> per_nand_mmc_clk 1 1 50000000
> nand_clk 0 0 12500000
> nand_x_clk 0 0 50000000
> sdmmc_clk 1 1 50000000
>
Yes. I can confirm that on my board, too. I actually seem to have read over
those three values and missed them.
Let's wait for 3.13-rc1, then.
I actually also wanted to change the l3_sp_clk, as it seems to be neglect
the "1 or 2" divider from l3_mp_clk IIRC, but I couldn't come up with a good
way without changing the binding or something. What do you thing about that?
Is that wrong at the moment or do I miss something?
Thanks,
Steffen
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2013-11-12 7:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 15:07 [PATCH 0/4] Socfpga: clk: trivial fixes and cleanup Steffen Trumtrar
2013-11-07 15:07 ` [PATCH 1/4] ARM: socfpga: clk: remove unused field Steffen Trumtrar
2013-11-07 15:07 ` [PATCH 2/4] ARM: socfpga: clk: fix define typo Steffen Trumtrar
2013-11-07 15:07 ` [PATCH 3/4] ARM: socfpga: clk: split clk code Steffen Trumtrar
2013-11-07 15:07 ` [PATCH 4/4] ARM: socfpga: clk: add clk_divider to periph Steffen Trumtrar
2013-11-12 0:12 ` [PATCH 0/4] Socfpga: clk: trivial fixes and cleanup Dinh Nguyen
2013-11-12 3:40 ` Dinh Nguyen
2013-11-12 7:40 ` Steffen Trumtrar [this message]
[not found] ` <CADhT+wffgF1veA8ec4zF7J3_4tsKUZXcq5-X9cLCgN5D3A7Nrw@mail.gmail.com>
2013-11-19 8:14 ` Steffen Trumtrar
2013-11-19 16:21 ` Dinh Nguyen
2013-11-19 21:34 ` Dinh Nguyen
2013-11-19 22:07 ` Steffen Trumtrar
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=20131112074028.GW28790@pengutronix.de \
--to=s.trumtrar@pengutronix.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 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).