From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] fbdev: simplefb: add support for 'memory-region' property on DT node
Date: Fri, 02 Feb 2018 14:20:35 +0900 [thread overview]
Message-ID: <20180202142035.CEB7.4A936039@socionext.com> (raw)
In-Reply-To: <2359956.Z9lQWSAgHb@amdc3058>
Hi Bartlomiej, Rob, Mark,
On Thu, 1 Feb 2018 16:56:08 +0100 <b.zolnierkie@samsung.com> wrote:
>
> Hi,
>
> On Tuesday, January 23, 2018 08:34:56 PM Kunihiko Hayashi wrote:
> > Enables 'memory-region' property referring to the memory description on
> > the reserved-memory node in case of devicetree use.
> > If there is no 'reg' property that specifies the address and size of
> > the framebuffer, the address and size written in the memory description
> > on the reserved-memory node can be used for the framebuffer.
> >
> > Furthermore, the reserved-memory node needs to have "no-map" attributes
> > because simplefb driver maps the region by ioremap_wc().
> >
> > Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
>
> This needs an ACK from Rob or Mark (DT bindings Maintainers).
Thanks for pointing out.
Rob, Mark, would you please confirm the patch?
This patch contains the addition to dt-bindings.
---
Best Regards,
Kunihiko Hayashi
next prev parent reply other threads:[~2018-02-02 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180123113510epcas1p1fc8a6e3ad50127bb84fe350b156a8c07@epcas1p1.samsung.com>
2018-01-23 11:34 ` Kunihiko Hayashi
2018-01-23 14:45 ` Hans de Goede
2018-02-01 15:56 ` Bartlomiej Zolnierkiewicz
2018-02-01 19:03 ` Andy Shevchenko
2018-02-02 5:21 ` Kunihiko Hayashi
2018-02-02 5:20 ` Kunihiko Hayashi [this message]
2018-02-05 6:09 ` Rob Herring
2018-02-05 12:03 ` Kunihiko Hayashi
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=20180202142035.CEB7.4A936039@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=b.zolnierkie@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®