Re: PM: RE: [PATCH] ARM: dts: imx6dl-yapp4: Use correct pseudo PHY address for the switch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Christian,

I added all the original recipients back to your PM as we may get some
useful feedback from someone.

On 21. 03. 19 0:17, Christian Lamparter wrote:
On Wednesday, March 20, 2019 12:09:05 PM CET you wrote:
The switch is accessible through pseudo PHY which is located at 0x10.

It doesn't look like your patch made it to the device-tree patchwork?!
(Maybe your @ysoft.com is blacklisted or something else is broken?)

I am aware of that and I am quite sure my mail is not blacklisted.
I submitted quite some patches recently and some of those made it to
the device-tree patchwork with no problem. I've got the impression that
only patches that modify something inside Documentation/devicetree/ are
visible there (but I do not really know how the system works).

@Rob, would you mind to shortly clarify how this works?

Also I don't think devicetree-tree would merge it. I think the best bet
would be to resent the mail and include netdev mailing list and everyone
from the get_maintainer.pl output:

I always use the get_maintainter.pl script to get some initial list and
then I apply common sense to shrink/broaden the list to which people and
lists send the patches.

Shawn Guo <shawnguo@xxxxxxxxxx> (maintainer:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)
Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> (maintainer:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)
Pengutronix Kernel Team <kernel@xxxxxxxxxxxxxx> (reviewer:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)
Fabio Estevam <festevam@xxxxxxxxx> (reviewer:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)
NXP Linux Team <linux-imx@xxxxxxx> (reviewer:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)
devicetree@xxxxxxxxxxxxxxx (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
linux-arm-kernel@xxxxxxxxxxxxxxxxxxx (moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE)

In this case this is really trivial patch so I think bothering all those
people is not necessary. In my case the script actually reports more
items then what you posted.

I added you, Florian and Andrew just because I tripped around your patch
that fixes the device tree example of the qca8k binding and this change
is related to it.

I actually expect the patch to be picked by Shawn (AFAIK he takes care
of the imx device trees).

@Shawn, if my expectation is wrong, please correct me.

Anyway, thanks a lot for your comments Christian!

Best regards,
Michal

Signed-off-by: Michal Vokáč <michal.vokac@xxxxxxxxx>
---
  arch/arm/boot/dts/imx6dl-yapp4-common.dtsi | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/boot/dts/imx6dl-yapp4-common.dtsi b/arch/arm/boot/dts/imx6dl-yapp4-common.dtsi
index 091d829f6b05..e8d800fec637 100644
--- a/arch/arm/boot/dts/imx6dl-yapp4-common.dtsi
+++ b/arch/arm/boot/dts/imx6dl-yapp4-common.dtsi
@@ -114,9 +114,9 @@
  			reg = <2>;
  		};
- switch@0 {
+		switch@10 {
  			compatible = "qca,qca8334";
-			reg = <0>;
+			reg = <10>;
switch_ports: ports {
  				#address-cells = <1>;




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux