Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755201AbaFYHyC (ORCPT ); Wed, 25 Jun 2014 03:54:02 -0400 Received: from mail-we0-f170.google.com ([74.125.82.170]:38359 "EHLO mail-we0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755126AbaFYHx6 (ORCPT ); Wed, 25 Jun 2014 03:53:58 -0400 MIME-Version: 1.0 In-Reply-To: <074a01cf8fc1$e906f0c0$bb14d240$%debski@samsung.com> References: <1403614495-9291-1-git-send-email-k.debski@samsung.com> <074a01cf8fc1$e906f0c0$bb14d240$%debski@samsung.com> Date: Wed, 25 Jun 2014 08:53:54 +0100 Message-ID: Subject: Re: [PATCH] phy: phy-samsung-usb2: Change phy power on/power off sequence From: Daniel Drake To: Kamil Debski Cc: linux-kernel@vger.kernel.org, linux-samsung-soc , linux-usb@vger.kernel.org, kishon@ti.com, Tomasz Figa , Marek Szyprowski , gautam.vivek@samsung.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 24, 2014 at 4:35 PM, Kamil Debski wrote: > By reboot I guess that you mean typing "reboot" or by using SysRq magic > and not power cycling? > > If so, I had experienced the same symptoms. I guess that the Ethernet > chip is not reset properly and fails to enumerate without power cycling > (it's nRESET pin is connected to P3V3). > > I found that removing regulator-always-on from buck8_reg: BUCK8 in the > dts file fixes this problem. Yes, that fixes the problem. Thanks! Tested-by: Daniel Drake -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/