mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Kurz <akurz@blala.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: zynq7000: make PS_CLK Kconfigurable
Date: Wed, 15 Mar 2017 09:05:34 +0100	[thread overview]
Message-ID: <20170315080534.4wfb7thp3eiddax4@pengutronix.de> (raw)
In-Reply-To: <1489350420-10640-1-git-send-email-akurz@blala.de>

Hi ALexander,

On Sun, Mar 12, 2017 at 09:27:00PM +0100, Alexander Kurz wrote:
> The main clock source on Zynq-7000 based boards (PS_CLK) is not uniform
> for all boards, while typical boards are clocked with 33.3MHz, the
> Z-7010 based Digilent Zybo board is clocked with 50MHz.
> Since barebox is not yet OF aware for Zynq, make PS_CLK board dependent
> via Kconfig.

We shouldn't encode differences between boards in Kconfig.

One way around it would be to add platform_data to the clk device and
call zynq_init() (with an additional freq argument) from the board code rather
than directly from an initcall.
Creating a small zynq_set_ps_clk() which sets the clock and is to
be called by the board before the clock driver is initialized would be
simpler but also work.

Sascha

-- 
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 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2017-03-15  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 20:27 Alexander Kurz
2017-03-15  8:05 ` Sascha Hauer [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=20170315080534.4wfb7thp3eiddax4@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=akurz@blala.de \
    --cc=barebox@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