This reverts commit 7daa213700758b5b08fc0daab09bb139dd334165.
The original commit has several problems:
- vdd-cpus and aldo3 (AVCC of the SoC) are not set to always-on, which
leads to system hang when disabling unused regulators.
- GMAC (which uses dldo1 and aldo2) and Wi-Fi (which uses aldo1) are not
considered, and will fail to work after adding this commit.
This indicates that this patch should be not tested at all.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
---
arch/arm/boot/dts/sun6i-a31s-sinovoip-bpi-m2.dts | 57 ------------------------
1 file changed, 57 deletions(-)
Hello,
On Sat, 3 Feb 2018 19:23:53 +0800
Icenowy Zheng [off-list ref] wrote:
This reverts commit 7daa213700758b5b08fc0daab09bb139dd334165.
The original commit has several problems:
- vdd-cpus and aldo3 (AVCC of the SoC) are not set to always-on, which
leads to system hang when disabling unused regulators.
Indeed I should have make those always-on.
- GMAC (which uses dldo1 and aldo2) and Wi-Fi (which uses aldo1) are not
considered, and will fail to work after adding this commit.
While I understand the problem with vdd-cpus and aldo3 I don't see why
when you don't declare regulator the code should do something with it.
DT is supposed to describe the hardware and the code should not use
hardware not described right ?
The gmac node doesn't declare any regulators and the mmc2 uses
reg_vcc3v0 (haven't checked on the schematics yet if it is correct).
This indicates that this patch should be not tested at all.
This have indeed not been tested with linux.
I think that this commit should not be reverted, I'll send a proper
patch tonight or tomorow night max.
P.S.: Also as I'm the original sender I think I should have been in CC
no ?
Cheers,
--
2.15.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Emmanuel Vadot [off-list ref] [off-list ref]
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello,
On Sat, 3 Feb 2018 19:23:53 +0800
Icenowy Zheng [off-list ref] wrote:
quoted
This reverts commit 7daa213700758b5b08fc0daab09bb139dd334165.
The original commit has several problems:
- vdd-cpus and aldo3 (AVCC of the SoC) are not set to always-on,
which
quoted
leads to system hang when disabling unused regulators.
Indeed I should have make those always-on.
quoted
- GMAC (which uses dldo1 and aldo2) and Wi-Fi (which uses aldo1) are
not
quoted
considered, and will fail to work after adding this commit.
While I understand the problem with vdd-cpus and aldo3 I don't see why
when you don't declare regulator the code should do something with it.
DT is supposed to describe the hardware and the code should not use
hardware not described right ?
The gmac node doesn't declare any regulators and the mmc2 uses
reg_vcc3v0 (haven't checked on the schematics yet if it is correct).
It's because the regulator support isn't present before
this commit. However these parts really need special
regulators. I don't have M2 schematics at hand, so you'd
check it by yourself.
P.S. a proper device tree with AXP shouldn't use
reg_vcc3v0/3v3/1v8/etc. They're dummy
regulator nodes for
not implemented or not controllable regulators.
quoted
This indicates that this patch should be not tested at all.
This have indeed not been tested with linux.
I think that this commit should not be reverted, I'll send a proper
patch tonight or tomorow night max.
Please test patches sent to Linux on Linux :-)
P.S.: Also as I'm the original sender I think I should have been in CC
no ?
get_maintainer.pl didn't mention you and I forgot... sorry.
--
2.15.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello,
On Sat, 3 Feb 2018 19:23:53 +0800
Icenowy Zheng [off-list ref] wrote:
quoted
This reverts commit 7daa213700758b5b08fc0daab09bb139dd334165.
The original commit has several problems:
- vdd-cpus and aldo3 (AVCC of the SoC) are not set to always-on,
which
quoted
leads to system hang when disabling unused regulators.
Indeed I should have make those always-on.
quoted
- GMAC (which uses dldo1 and aldo2) and Wi-Fi (which uses aldo1) are
not
quoted
considered, and will fail to work after adding this commit.
While I understand the problem with vdd-cpus and aldo3 I don't see why
when you don't declare regulator the code should do something with it.
DT is supposed to describe the hardware and the code should not use
hardware not described right ?
The gmac node doesn't declare any regulators and the mmc2 uses
reg_vcc3v0 (haven't checked on the schematics yet if it is correct).
It's because the regulator support isn't present before
this commit. However these parts really need special
regulators. I don't have M2 schematics at hand, so you'd
check it by yourself.
Yes but why does the PMIC should disable regulators not defined in the
DTS ? That the part I don't understand and want to know where it is
described/documented.
P.S. a proper device tree with AXP shouldn't use
reg_vcc3v0/3v3/1v8/etc. They're dummy
regulator nodes for
not implemented or not controllable regulators.
quoted
quoted
This indicates that this patch should be not tested at all.
This have indeed not been tested with linux.
I think that this commit should not be reverted, I'll send a proper
patch tonight or tomorow night max.
Please test patches sent to Linux on Linux :-)
If my patches adhere to the bindings I don't see why.
quoted
P.S.: Also as I'm the original sender I think I should have been in CC
no ?
get_maintainer.pl didn't mention you and I forgot... sorry.
From: Maxime Ripard <hidden> Date: 2018-02-13 10:30:29
On Fri, Feb 09, 2018 at 10:20:57PM +0100, Emmanuel Vadot wrote:
quoted
P.S. a proper device tree with AXP shouldn't use
reg_vcc3v0/3v3/1v8/etc. They're dummy
regulator nodes for
not implemented or not controllable regulators.
quoted
quoted
This indicates that this patch should be not tested at all.
This have indeed not been tested with linux.
I think that this commit should not be reverted, I'll send a proper
patch tonight or tomorow night max.
Please test patches sent to Linux on Linux :-)
If my patches adhere to the bindings I don't see why.
Adhering to a binding and being functional is a completely different
story.
And the latter is the most important.
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
Hello,
On Sat, 3 Feb 2018 19:23:53 +0800
Icenowy Zheng [off-list ref] wrote:
quoted
This reverts commit 7daa213700758b5b08fc0daab09bb139dd334165.
The original commit has several problems:
- vdd-cpus and aldo3 (AVCC of the SoC) are not set to always-on,
which
quoted
leads to system hang when disabling unused regulators.
Indeed I should have make those always-on.
quoted
- GMAC (which uses dldo1 and aldo2) and Wi-Fi (which uses aldo1) are
not
quoted
considered, and will fail to work after adding this commit.
While I understand the problem with vdd-cpus and aldo3 I don't see why
when you don't declare regulator the code should do something with it.
DT is supposed to describe the hardware and the code should not use
hardware not described right ?
The gmac node doesn't declare any regulators and the mmc2 uses
reg_vcc3v0 (haven't checked on the schematics yet if it is correct).
It's because the regulator support isn't present before
this commit. However these parts really need special
regulators. I don't have M2 schematics at hand, so you'd
check it by yourself.
Yes but why does the PMIC should disable regulators not defined in the DTS
? That the part I don't understand and want to know where it is
described/documented.
They are defined. See axp22x.dtsi, which you included in your patch.
Now the system is free to do whatever it wants under the constraints
of the device tree. Since you do not reference the regulator, the
kernel is free to turn it off to save power.
quoted
P.S. a proper device tree with AXP shouldn't use
reg_vcc3v0/3v3/1v8/etc. They're dummy
regulator nodes for
not implemented or not controllable regulators.
quoted
quoted
This indicates that this patch should be not tested at all.
This have indeed not been tested with linux.
I think that this commit should not be reverted, I'll send a proper
patch tonight or tomorow night max.
Please test patches sent to Linux on Linux :-)
If my patches adhere to the bindings I don't see why.
It adheres to the bindings, but does not accurately describe the
hardware constraints.
ChenYu
quoted
quoted
P.S.: Also as I'm the original sender I think I should have been in CC
no ?
get_maintainer.pl didn't mention you and I forgot... sorry.
--
You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/d/optout.
Hello,
On Sat, 3 Feb 2018 19:23:53 +0800
Icenowy Zheng [off-list ref] wrote:
quoted
This reverts commit 7daa213700758b5b08fc0daab09bb139dd334165.
The original commit has several problems:
- vdd-cpus and aldo3 (AVCC of the SoC) are not set to always-on,
which
quoted
leads to system hang when disabling unused regulators.
Indeed I should have make those always-on.
quoted
- GMAC (which uses dldo1 and aldo2) and Wi-Fi (which uses aldo1) are
not
quoted
considered, and will fail to work after adding this commit.
While I understand the problem with vdd-cpus and aldo3 I don't see why
when you don't declare regulator the code should do something with it.
DT is supposed to describe the hardware and the code should not use
hardware not described right ?
The gmac node doesn't declare any regulators and the mmc2 uses
reg_vcc3v0 (haven't checked on the schematics yet if it is correct).
It's because the regulator support isn't present before
this commit. However these parts really need special
regulators. I don't have M2 schematics at hand, so you'd
check it by yourself.
Yes but why does the PMIC should disable regulators not defined in the DTS
? That the part I don't understand and want to know where it is
described/documented.
They are defined. See axp22x.dtsi, which you included in your patch.
Now the system is free to do whatever it wants under the constraints
of the device tree. Since you do not reference the regulator, the
kernel is free to turn it off to save power.
Yeah I realized that now and feel stupid ...
Thanks for the clarification.
quoted
quoted
P.S. a proper device tree with AXP shouldn't use
reg_vcc3v0/3v3/1v8/etc. They're dummy
regulator nodes for
not implemented or not controllable regulators.
quoted
quoted
This indicates that this patch should be not tested at all.
This have indeed not been tested with linux.
I think that this commit should not be reverted, I'll send a proper
patch tonight or tomorow night max.
Please test patches sent to Linux on Linux :-)
If my patches adhere to the bindings I don't see why.
It adheres to the bindings, but does not accurately describe the
hardware constraints.
Is there a place where there is build of the linux kernel for
sunxi/multi7 and initrd available for download so I can add that to my
test bench ?
Cheers,
ChenYu
quoted
quoted
quoted
P.S.: Also as I'm the original sender I think I should have been in CC
no ?
get_maintainer.pl didn't mention you and I forgot... sorry.