From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [RFC 0/5] Migrate AM35xx MUSB glue to device tree and enable MUSB Date: Tue, 3 Jul 2018 00:37:59 -0700 Message-ID: <20180703073759.GQ112168@atomide.com> References: <20180625001233.9785-1-aford173@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20180625001233.9785-1-aford173@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Adam Ford Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, gregkh@linuxfoundation.org, linux-usb@vger.kernel.org, linux@armlinux.org.uk, robh+dt@kernel.org, bcousson@baylibre.com, linux-omap@vger.kernel.org, adam.ford@logicpd.com, b-liu@ti.com, linux-arm-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org * Adam Ford [180624 17:15]: > > It currently doesnt' work, but I am looking for ideas on > what I may have missed or done incorrectly. Check the drivers/phy/ti driver part and make sure that works and has pins and clocks configured. The rest should be pretty much generic stuff for musb as long as the SoC glue layer can deal with the module, clocks and pins. Regards, Tony