From: Thierry Reding <thierry.reding@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Mark Brown <broonie@kernel.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Will Deacon <will.deacon@arm.com>,
Doug Anderson <dianders@chromium.org>,
Tomasz Figa <tomasz.figa@gmail.com>,
"kgene.kim@samsung.com" <kgene.kim@samsung.com>,
Olof Johansson <olof@lixom.net>,
Prashanth G <prashanth.g@samsung.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"rahul.sharma@samsung.com" <rahul.sharma@samsung.com>
Subject: Re: Unable to boot mainline on snow chromebook since 3.15
Date: Tue, 30 Sep 2014 08:12:07 +0200 [thread overview]
Message-ID: <20140930061206.GG29874@ulmo> (raw)
In-Reply-To: <CACxGe6uDYNOuhgM_5iQTp=iB4X-osSz8WESiUb2QGj5ZmWFp-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]
On Mon, Sep 29, 2014 at 02:12:43PM +0100, Grant Likely wrote:
> On Mon, Sep 29, 2014 at 1:57 PM, Thierry Reding <thierry.reding@gmail.com> wrote:
> > Though there are two cases: one is to use simplefb as a means to have
> > early boot messages on a graphical display (and optionally hand off to a
> > real driver). The other is to use simplefb as the only framebuffer
> > driver until a proper driver has been implemented. The latter would have
> > the disadvantage of not allowing unused resources from being garbage
> > collected at all. Then again, I don't think power consumption is going
> > to be a very big issue on hardware where no proper display driver is
> > available.
>
> When simplefb is the only framebuffer to get a platform working, it is
> reasonable to have a placeholder driver that grabs the resources and
> nothing else. When a real driver is implemented, and merged, the
> placeholder driver should drop compatibility with the device node at
> the same time.
You mean the device node for the real device should be compatible with
"simplefb"? One problem I see with that is that there may be multiple
dummy drivers for different pieces of hardware, all of them binding to
the simplefb compatible and conflicting.
Also this assumes that a device tree node exists for the device. One of
the reasons for using simplefb is so that you don't have to write that
device tree node and its binding yet.
Presumably, though, if the firmware already knows what resources are
needed and generate them at runtime it should be possible to come up
with a static device tree node, too.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: Unable to boot mainline on snow chromebook since 3.15
Date: Tue, 30 Sep 2014 08:12:07 +0200 [thread overview]
Message-ID: <20140930061206.GG29874@ulmo> (raw)
In-Reply-To: <CACxGe6uDYNOuhgM_5iQTp=iB4X-osSz8WESiUb2QGj5ZmWFp-A@mail.gmail.com>
On Mon, Sep 29, 2014 at 02:12:43PM +0100, Grant Likely wrote:
> On Mon, Sep 29, 2014 at 1:57 PM, Thierry Reding <thierry.reding@gmail.com> wrote:
> > Though there are two cases: one is to use simplefb as a means to have
> > early boot messages on a graphical display (and optionally hand off to a
> > real driver). The other is to use simplefb as the only framebuffer
> > driver until a proper driver has been implemented. The latter would have
> > the disadvantage of not allowing unused resources from being garbage
> > collected at all. Then again, I don't think power consumption is going
> > to be a very big issue on hardware where no proper display driver is
> > available.
>
> When simplefb is the only framebuffer to get a platform working, it is
> reasonable to have a placeholder driver that grabs the resources and
> nothing else. When a real driver is implemented, and merged, the
> placeholder driver should drop compatibility with the device node at
> the same time.
You mean the device node for the real device should be compatible with
"simplefb"? One problem I see with that is that there may be multiple
dummy drivers for different pieces of hardware, all of them binding to
the simplefb compatible and conflicting.
Also this assumes that a device tree node exists for the device. One of
the reasons for using simplefb is so that you don't have to write that
device tree node and its binding yet.
Presumably, though, if the firmware already knows what resources are
needed and generate them at runtime it should be possible to come up
with a static device tree node, too.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140930/0d1900ff/attachment-0001.sig>
next prev parent reply other threads:[~2014-09-30 6:12 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 11:57 Unable to boot mainline on snow chromebook since 3.15 Will Deacon
2014-09-05 12:22 ` Will Deacon
2014-09-05 12:22 ` Will Deacon
2014-09-05 13:46 ` Ajay kumar
2014-09-05 13:46 ` Ajay kumar
2014-09-05 13:56 ` Vivek Gautam
2014-09-05 13:56 ` Vivek Gautam
2014-09-08 11:17 ` Will Deacon
2014-09-08 11:17 ` Will Deacon
2014-09-05 14:12 ` Marc Zyngier
2014-09-05 14:12 ` Marc Zyngier
2014-09-05 20:25 ` Doug Anderson
2014-09-05 20:25 ` Doug Anderson
2014-09-07 9:06 ` Javier Martinez Canillas
2014-09-07 9:06 ` Javier Martinez Canillas
2014-09-07 15:01 ` Mark Brown
2014-09-07 15:01 ` Mark Brown
2014-09-07 15:51 ` Javier Martinez Canillas
2014-09-07 15:51 ` Javier Martinez Canillas
2014-09-07 15:52 ` Tomasz Figa
2014-09-07 15:52 ` Tomasz Figa
2014-09-07 16:12 ` Javier Martinez Canillas
2014-09-07 16:12 ` Javier Martinez Canillas
2014-09-07 16:19 ` Tomasz Figa
2014-09-07 16:19 ` Tomasz Figa
2014-09-07 16:40 ` Javier Martinez Canillas
2014-09-07 16:40 ` Javier Martinez Canillas
2014-09-08 11:21 ` Will Deacon
2014-09-08 11:21 ` Will Deacon
2014-09-08 11:55 ` Javier Martinez Canillas
2014-09-08 11:55 ` Javier Martinez Canillas
2014-09-08 12:46 ` Will Deacon
2014-09-08 12:46 ` Will Deacon
2014-09-08 12:20 ` Grant Likely
2014-09-08 12:20 ` Grant Likely
2014-09-08 13:49 ` Mark Brown
2014-09-08 13:49 ` Mark Brown
2014-09-08 14:05 ` Javier Martinez Canillas
2014-09-08 14:05 ` Javier Martinez Canillas
2014-09-10 11:17 ` Will Deacon
2014-09-10 11:17 ` Will Deacon
2014-09-10 16:03 ` Doug Anderson
2014-09-10 16:03 ` Doug Anderson
2014-09-10 16:23 ` Will Deacon
2014-09-10 16:23 ` Will Deacon
2014-09-08 15:58 ` Doug Anderson
2014-09-08 15:58 ` Doug Anderson
2014-09-08 19:40 ` Grant Likely
2014-09-08 19:40 ` Grant Likely
2014-09-10 13:06 ` Olof Johansson
2014-09-10 13:06 ` Olof Johansson
2014-09-10 14:31 ` Mark Brown
2014-09-10 14:31 ` Mark Brown
2014-09-10 14:56 ` Grant Likely
2014-09-10 14:56 ` Grant Likely
2014-09-10 15:39 ` Mark Brown
2014-09-10 15:39 ` Mark Brown
2014-09-10 16:29 ` Grant Likely
2014-09-10 16:29 ` Grant Likely
2014-09-10 16:45 ` Doug Anderson
2014-09-10 16:45 ` Doug Anderson
2014-09-10 19:45 ` Mark Brown
2014-09-10 19:45 ` Mark Brown
2014-09-10 19:51 ` Doug Anderson
2014-09-10 19:51 ` Doug Anderson
2014-09-10 16:57 ` Mark Brown
2014-09-10 16:57 ` Mark Brown
2014-09-11 9:22 ` Grant Likely
2014-09-11 9:22 ` Grant Likely
2014-09-11 18:03 ` Mark Brown
2014-09-11 18:03 ` Mark Brown
2014-09-11 22:54 ` Doug Anderson
2014-09-11 22:54 ` Doug Anderson
2014-09-29 12:57 ` Thierry Reding
2014-09-29 12:57 ` Thierry Reding
2014-09-29 13:12 ` Grant Likely
2014-09-29 13:12 ` Grant Likely
2014-09-29 16:37 ` Mark Brown
2014-09-29 16:37 ` Mark Brown
2014-09-30 6:12 ` Thierry Reding [this message]
2014-09-30 6:12 ` Thierry Reding
2014-09-29 20:46 ` Maxime Ripard
2014-09-29 20:46 ` Maxime Ripard
2014-09-10 16:36 ` Olof Johansson
2014-09-10 16:36 ` Olof Johansson
2014-09-10 18:17 ` Mark Brown
2014-09-10 18:17 ` Mark Brown
2014-09-11 9:06 ` Grant Likely
2014-09-11 9:06 ` Grant Likely
2014-09-11 16:16 ` Mark Brown
2014-09-11 16:16 ` Mark Brown
2014-09-08 4:36 ` Doug Anderson
2014-09-08 4:36 ` Doug Anderson
2014-09-08 6:09 ` Javier Martinez Canillas
2014-09-08 6:09 ` Javier Martinez Canillas
2014-09-08 15:55 ` Doug Anderson
2014-09-08 15:55 ` Doug Anderson
2014-09-08 16:07 ` Will Deacon
2014-09-08 16:07 ` Will Deacon
2014-09-08 16:12 ` Doug Anderson
2014-09-08 16:12 ` Doug Anderson
2014-09-08 10:20 ` Mark Brown
2014-09-08 10:20 ` Mark Brown
2014-09-08 4:43 ` Doug Anderson
2014-09-08 4:43 ` Doug Anderson
2015-01-30 4:56 bruce m beach
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=20140930061206.GG29874@ulmo \
--to=thierry.reding@gmail.com \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=grant.likely@secretlab.ca \
--cc=javier.martinez@collabora.co.uk \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=prashanth.g@samsung.com \
--cc=rahul.sharma@samsung.com \
--cc=tomasz.figa@gmail.com \
--cc=will.deacon@arm.com \
/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.