From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH v2 6/6] usb: chipidea: add work-around for Marvell HSIC PHY startup Date: Wed, 20 May 2015 22:47:42 -0500 Message-ID: References: <1432087805-16671-1-git-send-email-robh@kernel.org> <1432087805-16671-7-git-send-email-robh@kernel.org> <20150521031334.GA2897@shlinux2> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20150521031334.GA2897@shlinux2> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Peter Chen Cc: Greg Kroah-Hartman , Kishon Vijay Abraham I , Linux USB List , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Arnd Bergmann , Alan Stern List-Id: devicetree@vger.kernel.org On Wed, May 20, 2015 at 10:13 PM, Peter Chen wrote: > On Tue, May 19, 2015 at 09:10:05PM -0500, Rob Herring wrote: >> The Marvell 28nm HSIC PHY requires the port to be forced to HS mode after >> the port power is applied. This is done using the test mode in the PORTSC >> register. >> >> As HSIC is always HS, this work-around should be safe to do with all HSIC >> PHYs. If not, a flag can also be added. > > I think a flag is needed, not sure all vendors can work well with that. Only i.MX6Sx uses HSIC in mainline. Is that something you can test? It would be better to not add flags unless they are really needed. Otherwise you end up with dozens of flags like SDHCI drivers have. Rob -- 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