From: Thierry Reding <thierry.reding@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>, Helge Deller <deller@gmx.de>
Cc: Robert Foss <rfoss@kernel.org>, Jon Hunter <jonathanh@nvidia.com>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-tegra@vger.kernel.org
Subject: [PATCH v2 0/2] fbdev/simplefb: Add missing simple-framebuffer features
Date: Wed, 1 Nov 2023 18:20:15 +0100 [thread overview]
Message-ID: <20231101172017.3872242-1-thierry.reding@gmail.com> (raw)
From: Thierry Reding <treding@nvidia.com>
Hi,
This contains two patches that bring simplefb up to feature parity with
simpledrm. The patches add support for the "memory-region" property that
provides an alternative to the "reg" property to describe the memory
used for the framebuffer and allow attaching the simple-framebuffer
device to one or more generic power domains to make sure they aren't
turned off during the boot process and take down the display
configuration.
Changes in v2:
- remove unnecessary call to simplefb_detach_genpds() since that's
already done automatically by devres
- fix crash if power-domains property is missing in DT
Thanks,
Thierry
Thierry Reding (2):
fbdev/simplefb: Support memory-region property
fbdev/simplefb: Add support for generic power-domains
drivers/video/fbdev/simplefb.c | 128 +++++++++++++++++++++++++++++++--
1 file changed, 123 insertions(+), 5 deletions(-)
--
2.42.0
next reply other threads:[~2023-11-01 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 17:20 Thierry Reding [this message]
2023-11-01 17:20 ` [PATCH v2 1/2] fbdev/simplefb: Support memory-region property Thierry Reding
2023-11-01 17:20 ` [PATCH v2 2/2] fbdev/simplefb: Add support for generic power-domains Thierry Reding
2023-11-21 1:17 ` Richard Acayan
2023-11-21 9:01 ` Hans de Goede
2023-11-22 0:01 ` Richard Acayan
2023-11-22 8:42 ` Hans de Goede
2023-11-01 17:54 ` [PATCH v2 0/2] fbdev/simplefb: Add missing simple-framebuffer features Hans de Goede
2023-11-02 10:54 ` Hans de Goede
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=20231101172017.3872242-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=jonathanh@nvidia.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rfoss@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