linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: S3C64XX: Implement basic power domain support
Date: Fri, 02 Dec 2011 20:06:17 +0100	[thread overview]
Message-ID: <1540677.QKv7YOdnN3@flatron> (raw)
In-Reply-To: <20111202185743.GA27227@opensource.wolfsonmicro.com>

On Friday 02 of December 2011 18:57:43 Mark Brown wrote:
> On Fri, Dec 02, 2011 at 07:25:01PM +0100, Tomasz Figa wrote:
> > Please do not forget that there might be some drivers not yet submited
> > to mainline and mainline should not break them with an assumption that
> > there are no such drivers.
> > 
> > For example, there is an on-going work on an open source OpenGL
> > implementation for the GPU in S3C6410, known as OpenFIMG. Currently it
> > uses a little kernel module for low level hardware management
> > (interrupts, contexts, locking, power management), involving clock
> > gating and runtime power management, but a DRM driver is planned.
> 
> As I said in the commit message for the patch you're following up on
> I don't think that's a problem as it's pretty straightforward to add the
> requisite hooks as part of adding the actual drivers.  The power domain
> framework is really easy to use so it's not like it should cause real
> effort, if you can figure out how to drive a 3D graphics engine adding a
> device to a power domain shouldn't be too hard.
> 
> There will need to be arch/arm changes to add the platform devices and
> hook up the clocks anyway so it's not like this is creating a need for
> modifications.  Indeed I'd suggest adding the arch/arm stuff as it gets
> written anyway, even if the actual drivers are still a work in progress.
> It's one less thing to carry out of tree and it means that updates like
> this or like the clk API reworks that I'd expect to start appearing soon
> will happen for free.

Yeah, I'm okay with that, I just noted that there is more support for S3C6410 
available than just what is present in mainline.

Best regards,
Tom

  reply	other threads:[~2011-12-02 19:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 18:48 [PATCH 1/3] PM: Provide an always on power domain governor Mark Brown
2011-12-01 18:48 ` [PATCH 2/3] ARM: mach-shmobile: Use common " Mark Brown
2011-12-01 20:37   ` Rafael J. Wysocki
2011-12-02  0:33     ` Mark Brown
2011-12-02 22:36       ` Rafael J. Wysocki
2011-12-03 11:03         ` Mark Brown
2011-12-03 22:31           ` Rafael J. Wysocki
2011-12-04  1:22             ` Mark Brown
2011-12-04 19:53               ` Rafael J. Wysocki
2011-12-04  1:24           ` [PATCH v2] " Mark Brown
2011-12-01 18:48 ` [PATCH 3/3] ARM: S3C64XX: Implement basic power domain support Mark Brown
2011-12-02  0:35   ` Kyungmin Park
2011-12-02  0:56     ` Mark Brown
2011-12-02 18:25       ` Tomasz Figa
2011-12-02 18:57         ` Mark Brown
2011-12-02 19:06           ` Tomasz Figa [this message]
2011-12-02 20:10   ` Sylwester Nawrocki
2011-12-02 21:07     ` Mark Brown
2011-12-07 21:44       ` Rafael J. Wysocki
2011-12-08  1:09         ` Mark Brown
2011-12-08 22:15           ` Rafael J. Wysocki
2011-12-08 22:22             ` Rafael J. Wysocki
2011-12-04 20:56 ` [PATCH 1/3] PM: Provide an always on power domain governor Rafael J. Wysocki
2011-12-04 23:10   ` Mark Brown
2011-12-05  0:15     ` Rafael J. Wysocki
2011-12-05  0:15       ` Mark Brown
2011-12-06 10:20         ` Kukjin Kim
2011-12-06 12:04           ` Marek Szyprowski
2011-12-06 14:33             ` Mark Brown
2011-12-06 21:39           ` Rafael J. Wysocki
2011-12-07 12:35             ` Mark Brown
2011-12-07 21:28               ` Rafael J. Wysocki
2011-12-08  0:40                 ` Mark Brown

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=1540677.QKv7YOdnN3@flatron \
    --to=tomasz.figa@gmail.com \
    --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).