linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/5] simplefb: add clock handling code
Date: Fri, 31 Oct 2014 08:15:31 +0000	[thread overview]
Message-ID: <54534523.8080801@ti.com> (raw)
In-Reply-To: <1413996311-4287-1-git-send-email-hdegoede@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 648 bytes --]

Hi Hans,

On 22/10/14 19:45, Hans de Goede wrote:

> -We will add a clocks property to the simplefb devicetree bindings, so
>  that u-boot setup framebuffers passed to the kernel (for early console
>  support) can properly list the clocks used, and simplefb can claim them to
>  avoid them getting turned off, thereby breaking the early console

Perhaps this has been discussed earlier, but I started to wonder if
managing clocks is enough.

What about regulators (to power the LCD), gpios (to keep the LCD
enabled) and pinctrl (for video signals)? I guess any those could be
reset by the kernel if no driver uses them.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-10-31  8:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 16:45 [PATCH v4 0/5] simplefb: add clock handling code Hans de Goede
2014-10-22 16:45 ` [PATCH v4 1/5] simplefb: Add simplefb MAINTAINERS entry Hans de Goede
2014-11-11 16:27   ` Grant Likely
2014-10-22 16:45 ` [PATCH v4 2/5] dt-bindings: Add a clocks property to the simple-framebuffer binding Hans de Goede
2014-11-11 21:42   ` Grant Likely
     [not found]     ` <546373C6.4010001@redhat.com>
2014-11-12 14:56       ` Grant Likely
2014-11-12 15:27         ` Hans de Goede
     [not found]         ` <CACxGe6vBq5Y6HbogbpVUy9VLaocfrAsR_XRbio4zBB_vY5GRsw@mail.gmail.com>
2014-11-12 17:43           ` Rob Herring
2014-10-22 16:45 ` [PATCH v4 3/5] simplefb: formalize pseudo palette handling Hans de Goede
2014-11-11 16:34   ` Grant Likely
2014-10-22 16:45 ` [PATCH v4 4/5] simplefb: add goto error path to probe Hans de Goede
2014-10-22 16:45 ` [PATCH v4 5/5] simplefb: add clock handling code Hans de Goede
2014-10-28 10:44 ` [PATCH v4 0/5] " Tomi Valkeinen
2014-10-28 11:08   ` Hans de Goede
2014-10-28 11:11   ` Rob Herring
2014-10-28 11:30     ` [linux-sunxi] " Hans de Goede
2014-10-29 11:08       ` Tomi Valkeinen
2014-10-31 20:47         ` Rob Herring
2014-11-02 14:39           ` Hans de Goede
2014-11-02 15:28           ` jonsmirl
2014-11-05  8:02             ` Luc Verhaegen
2014-11-11 21:49           ` [linux-sunxi] " Grant Likely
2014-11-12  8:34             ` Geert Uytterhoeven
2014-11-12  9:57               ` Grant Likely
2014-11-12 10:08                 ` Geert Uytterhoeven
2014-11-12 10:28                   ` Grant Likely
2014-10-31  8:15 ` Tomi Valkeinen [this message]
2014-10-31  9:00   ` [linux-sunxi] " Hans de Goede
2014-10-31  9:37     ` Javier Martinez Canillas
2014-10-31  9:51       ` Hans de Goede
2014-10-31 10:19         ` Javier Martinez Canillas
2014-11-06 14:18   ` Tomi Valkeinen
2014-11-06 15:05     ` [linux-sunxi] " Hans de Goede
2014-11-11 21:54       ` Grant Likely

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=54534523.8080801@ti.com \
    --to=tomi.valkeinen@ti.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).