Author: Pavel Machek Date: To: kernel list, tony, merlijn, martin_rysavy, maemo-leste Subject: Re: [maemo-leste] Modem on Droid 4 (mdm6600) in recent mainline
Hi!
> There's something very wrong with /dev/ttyUSB4 in recent kernels:
> unsolicited incoming data from the modem are getting lost; I believe
> it means also SMS notifications, but it is very easy to reproduce with
> incoming call notifications.
>
> They just don't come.
>
> But if you keep pasting "AT" into minicom, they actually do.
>
> Of course... that means that trying to debug ofono is ... "interesting".
>
> I tried playing with
> /sys/bus/platform/drivers/phy-mapphone-mdm6600/usb-phy\@1/power/control
> files and timeouts, but could not get it to work.
>
> Any idea what could be wrong there?
>
> Is there easy way to disable power management for testing?
I tried this... and it did not fix the problem :-(.
Pavel
diff --git a/drivers/phy/motorola/phy-mapphone-mdm6600.c b/drivers/phy/motorola/phy-mapphone-mdm6600.c
index 94a34cf75eb3..7ddf5aa35105 100644
--- a/drivers/phy/motorola/phy-mapphone-mdm6600.c
+++ b/drivers/phy/motorola/phy-mapphone-mdm6600.c
@@ -21,7 +21,7 @@
#define PHY_MDM6600_PHY_DELAY_MS 4000 /* PHY enable 2.2s to 3.5s */
#define PHY_MDM6600_ENABLED_DELAY_MS 8000 /* 8s more total for MDM6600 */
#define PHY_MDM6600_WAKE_KICK_MS 600 /* time on after GPIO toggle */
-#define MDM6600_MODEM_IDLE_DELAY_MS 1000 /* modem after USB suspend */
+#define MDM6600_MODEM_IDLE_DELAY_MS 100000000 /* modem after USB suspend */
#define MDM6600_MODEM_WAKE_DELAY_MS 200 /* modem response after idle */
::
Re: [maemo-leste] Modem on Droid 4 …
