linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org, sre@kernel.org, nekit1000@gmail.com,
	mpartap@gmx.net, merlijn@wizzup.org, martin_rysavy@centrum.cz
Subject: Re: v5.10-rc3 vs. Droid 4
Date: Sun, 15 Nov 2020 20:24:58 +0100	[thread overview]
Message-ID: <20201115192458.GA19769@duo.ucw.cz> (raw)
In-Reply-To: <20201115174909.GB32085@duo.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 3646 bytes --]

On Sun 2020-11-15 18:49:09, Pavel Machek wrote:
> Hi!
> > > 
> > > Does anyone have Droid 4 working with 5.10-rc3?
> > > 
> > > I tried it with the original config; I got message about culomb
> > > counter calibration done scrolling (and boot progressing very slowly
> > > or not at all) . So ... I disabled cpcap battery & charger
> > > support. But init still drops me to emergency shell.
> > > 
> > > I may try some more, but if someone know what is going on, let me
> > > know.
> > 
> > I ran into this too, sorry I thought I added you to Cc but looks like not.
> > See the fix here:
> > 
> > https://lore.kernel.org/lkml/20201111170613.46057-1-tony@atomide.com/
> 
> You did (thank you!) but I failed to realize importance of that
> email. I have tested it and the culomb counter messages are gone.
> 
> Good.
> 
> But it looks like my mmcblk interfaces got re-numbered, from mmcblk0 &
> mmcblk1 to mmcblk0 & mmcblk2. ... which breaks my startup. If someone
> knows what is going on there, please tell me :-).

It seems like my wireless card sabotages the mmc? If I disable mmc3
completely, I'm back to working system. (Those omap3 changes are
probably not needed).

Best regards,
									Pavel


diff --git a/arch/arm/boot/dts/motorola-mapphone-common.dtsi b/arch/arm/boot/dts/motorola-mapphone-common.dtsi
index ae4c0f7c7383..21a5375f1e66 100644
--- a/arch/arm/boot/dts/motorola-mapphone-common.dtsi
+++ b/arch/arm/boot/dts/motorola-mapphone-common.dtsi
@@ -394,6 +394,7 @@
 	ti,non-removable;
 };
 
+#if 0
 &mmc3 {
 	pinctrl-names = "default";
 	pinctrl-0 = <&mmc3_pins>;
@@ -420,6 +421,7 @@
 		tcxo-clock-frequency = <26000000>;
 	};
 };
+#endif
 
 &i2c1 {
 	led-controller@38 {
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index 1fed802175fc..60eb3ebdc6b8 100644
--- a/arch/arm/boot/dts/omap3-n900.dts
+++ b/arch/arm/boot/dts/omap3-n900.dts
@@ -866,9 +866,11 @@
 	no-sd;
 };
 
+#if 0
 &mmc3 {
 	status = "disabled";
 };
+#endif
 
 &gpmc {
 	ranges = <0 0 0x01000000 0x01000000>,	/* 16 MB for OneNAND */
diff --git a/arch/arm/boot/dts/omap3-n950-n9.dtsi b/arch/arm/boot/dts/omap3-n950-n9.dtsi
index 8601e5ab85b8..704e4c7149ed 100644
--- a/arch/arm/boot/dts/omap3-n950-n9.dtsi
+++ b/arch/arm/boot/dts/omap3-n950-n9.dtsi
@@ -563,9 +563,11 @@
 	ti,non-removable;
 };
 
+#if 0
 &mmc3 {
 	status = "disabled";
 };
+#endif
 
 /* RNG not directly accessible on N950/N9. */
 &rng_target {
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index 9dcae1f2bc99..ba575e76b75a 100644
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -532,6 +532,7 @@
 			dma-names = "tx", "rx";
 		};
 
+#if 0
 		mmc3: mmc@480ad000 {
 			compatible = "ti,omap3-hsmmc";
 			reg = <0x480ad000 0x200>;
@@ -540,6 +541,7 @@
 			dmas = <&sdma 77>, <&sdma 78>;
 			dma-names = "tx", "rx";
 		};
+#endif
 
 		mmu_isp: mmu@480bd400 {
 			#iommu-cells = <0>;
diff --git a/arch/arm/boot/dts/omap4-l4.dtsi b/arch/arm/boot/dts/omap4-l4.dtsi
index de742bf84efb..477246f8d5c1 100644
--- a/arch/arm/boot/dts/omap4-l4.dtsi
+++ b/arch/arm/boot/dts/omap4-l4.dtsi
@@ -2214,6 +2214,7 @@
 			ranges = <0x0 0xa8000 0x4000>;
 		};
 
+#if 0
 		target-module@ad000 {			/* 0x480ad000, ap 63 50.0 */
 			compatible = "ti,sysc-omap4", "ti,sysc";
 			reg = <0xad000 0x4>,
@@ -2245,6 +2246,7 @@
 				dma-names = "tx", "rx";
 			};
 		};
+#endif		
 
 		target-module@b0000 {			/* 0x480b0000, ap 47 40.0 */
 			compatible = "ti,sysc";




-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2020-11-15 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14 20:57 v5.10-rc3 vs. Droid 4 Pavel Machek
2020-11-15  8:31 ` Tony Lindgren
2020-11-15 17:49   ` Pavel Machek
2020-11-15 19:24     ` Pavel Machek [this message]
2020-11-15 18:47   ` Pavel Machek

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=20201115192458.GA19769@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=martin_rysavy@centrum.cz \
    --cc=merlijn@wizzup.org \
    --cc=mpartap@gmx.net \
    --cc=nekit1000@gmail.com \
    --cc=sre@kernel.org \
    --cc=tony@atomide.com \
    /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;
as well as URLs for NNTP newsgroup(s).