All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maksim Kozlov <m.kozlov@samsung.com>
To: qemu-devel@nongnu.org
Cc: kyungmin.park@samsung.com
Subject: Re: [Qemu-devel] [PATCH v4 1/2] ARM: exynos4210: CMU support
Date: Tue, 17 Jul 2012 16:12:17 +0400	[thread overview]
Message-ID: <500556A1.7090903@samsung.com> (raw)
In-Reply-To: <CAFEAcA-iWXBJGgqA5-QA0zAc_HMxR_MwXiBAf4PFB=nD4ZgGpQ@mail.gmail.com>

17.07.2012 01:05, Peter Maydell пишет:
> On 4 July 2012 17:27, Maksim Kozlov<m.kozlov@samsung.com>  wrote:
>> Add exynos4210 Clock Management Units emulation
>
> General comment, which I suspect you're not going to like...
>
> Underlying the exynos-specific code here, there's a general
> mechanism of "I'm a device, I have a clock input, I want to be
> able to find out when that clock is reprogrammed so I can
> adjust my behaviour, and I want to do things like ask what
> its rate is", and there's a provider of clock signals which
> has some kind of clock tree, possibly rearrangable at runtime
> by reprogramming the clock management unit. This is basically
> the same thing the OMAP clock code in hw/omap_clk.c also provides
> (though again the commonality is obscured under a heap of OMAP
> specific stuff).
>
> I think we need a generic interface for providing clocks
> and plumbing them together, which can then be used by both
> OMAP and Exynos and whatever later platforms come along
> with clock trees. I'd also really like to see this use QOM
> links rather than being a set of ad-hoc C functions for
> register/get rate/etc.
>
> You're platform number two, which I'm afraid means you get
> the pain of writing a generic mechanism...
>
> (There is a conceptual parallel with the kernel efforts to
> move to a common struct_clk infrastructure, I think; I'd
> much rather we did this while we have two clock tree models
> rather than waiting until we have half a dozen.)
>
> I've added some specific code review comments below, but
> this is the biggie.
>
Ok, I will think what I can do in this direction.
Thanks

  reply	other threads:[~2012-07-17 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 16:27 [Qemu-devel] [PATCH v4 0/2] ARM: Samsung Exynos4210 CMU support Maksim Kozlov
2012-07-04 16:27 ` [Qemu-devel] [PATCH v4 1/2] ARM: exynos4210: " Maksim Kozlov
2012-07-16 21:05   ` Peter Maydell
2012-07-17 12:12     ` Maksim Kozlov [this message]
2012-07-04 16:27 ` [Qemu-devel] [PATCH v4 2/2] exynos4210: UART: Added using of CMU-callback functionality Maksim Kozlov

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=500556A1.7090903@samsung.com \
    --to=m.kozlov@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=qemu-devel@nongnu.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.