From: Kevin Hilman <firstname.lastname@example.org>
To: Neil Armstrong <email@example.com>,
Kevin Hilman <firstname.lastname@example.org>,
Cc: email@example.com, firstname.lastname@example.org
Subject: Re: [PATCH v2 2/2] soc: amlogic: ee-pwrc: ensure driver state maches HW state
Date: Thu, 26 Sep 2019 12:08:01 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
Neil Armstrong <firstname.lastname@example.org> writes:
> On 25/09/2019 23:35, Kevin Hilman wrote:
>> From: Kevin Hilman <email@example.com>
>> During init, ensure that the driver on/off state as well as clock and
>> reset state matches the hardware state. Do this by always calling the
>> drivers 'on' function, and then callling the 'off' function if the
>> HW state was initially detected as off.
> I don't see what you are trying to solve except simplifying the code.
Simplifying the code is a worthwhile goal on its own, but that's not the
only thing I'm tring to accomplish.
Part of the goal is make the init less VPU specific and thus make it
more understandable/maintainable. But the more important part is to
ensure that the driver state and HW state is consistent for all the
domains (not just VPU.) I've had to debug lots of power-domain issues,
and inconsistiences between HW state and driver state tend to be the
primary cause of problems.
Also I'm generally not a fan of the "don't mess with bootloader state"
approach as that leads to subtle dependencies on specific bootloader
versions that are also difficult to debug.
Antother equally important goal is to actually be able to power-down the
VPU when it's not used. Right now, we'll never power off the VPU if the
bootloader enabled it, and that seems a bit extreme so I'm looking to
improve that and be able to power off the VPU when not used.
> And the case is more that "matching the clock state" here, the
> pm_domain_always_on_gov was is a real case when booting from the Amlogic
I'm not understanding what you mean about vendor uboot. I've done
testing with vendor uboot too:
I tried on g12a-u200, g12a-x96-max, and sm1-khadas-vim3l all of which
have vendor uboot, and I tried before and after $SUBJECT patch.
In all cases, I see the vendor uboot splash screen, and I see the
framebuffer console from linux after kernel boot. I see the same
behavior before and after my patch.
I also tried on g12b-odroid-n2 (vendor uboot), and there is _no_ uboot
spash screen, but I see the linux framebuffer console come up both
before and after my patch.
What's the specific case you're worried about with vendor uboot?
Also... note something interesting I noticed on sm1-khadas-vim3l:
before my patch, the framebuffer console appears, but the background is
a bluish/green color. After my patch, the background is black (as
> The display power domain is complex and as been half solved by using
> "simple-framebuffer" on gx and is missing on g12a/g12b/sm1.
> For example, Debian installer runs without the modules, but will use
> the EFIfb set by U-Boot, but in this precise case :
> - the DRM driver isn't loaded
> - we can't hook this power domain with EFIfb
OK, so I agree that this case where we want the display to continue to
work but linux DRM drivers never loaded is a special case.
Is there a way to check if efifb is enabled? Is the the linux driver
(drivers/video/fbdev/efifb.c) or something else only done by uboot?
If we can detect efifb from the kernel (not just whether the domain is
already on), then a simple addition to my patch like this:
+ else if (efifb_is_enabled)
+ dom->base.flags |= GENPD_FLAG_ALWAYS_ON;
would force the domain always-on in the case of efifb.
In fact, now that I think of it, simply adding:
+ dom->base.flags |= GENPD_FLAG_ALWAYS_ON;
to my current patch would get back to the same behavior of the existing
driver. But I still don't like the idea that we can *never* power off
the VPU if the bootloader enables it. :( I'd rather see patches
conditionally adding that flag with detailed explanations as to why it's
> When *not* in EFIfb, we use simple-framebuffer on GX, using this
> power domain, but it hasn't been copied to G12A.
I don't quite understand what problem simple-framebuffer is
solving. Could you explain that in more detail.
Assuming it is solving something, why can't it be used on g12[ab]/sm1 ?
> Personally I'll leave this code until we really tested and checked all
> uses cases,
Right, I don't want to break anything on purpose, but I think the
current state of this driver is fragile and difficult to
understand/maintain, so I would be grateful for any help in
understanding the corner cases better, as well as testing them (or
explaining to me how to reproduce them.)
Generally, with long-term maintenance in mind, if I'm forced to choose
between understandable/maintainable code and "covers 100% of corner
cases" I will most often chose the former.
> not only on the sei510/sei610 using mainline u-boot.
See above about all the other boards with vendor uboots also tested.
linux-amlogic mailing list
next prev parent reply other threads:[~2019-09-26 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 21:35 [PATCH v2 0/2] soc: amlogic: ee-pwrc: cleanup init state Kevin Hilman
2019-09-25 21:35 ` [PATCH v2 1/2] soc: amlogic: ee-pwrc: rename get_power Kevin Hilman
2019-09-25 21:35 ` [PATCH v2 2/2] soc: amlogic: ee-pwrc: ensure driver state maches HW state Kevin Hilman
2019-09-26 9:05 ` Neil Armstrong
2019-09-26 19:08 ` Kevin Hilman [this message]
2019-09-27 6:37 ` Neil Armstrong
2019-09-27 16:02 ` Kevin Hilman
2019-09-30 8:22 ` Jerome Brunet
2019-09-30 15:32 ` Kevin Hilman
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).