From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Rutland Subject: Re: [PATCH 09/13] mfd: omap-usb-host: Add device tree support and binding information Date: Tue, 5 Feb 2013 16:11:41 +0000 Message-ID: <20130205161141.GD26842@e106331-lin.cambridge.arm.com> References: <1359993540-20780-1-git-send-email-rogerq@ti.com> <1359993540-20780-10-git-send-email-rogerq@ti.com> <20130205142049.GC26842@e106331-lin.cambridge.arm.com> <51111A41.4050607@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <51111A41.4050607@ti.com> Content-Disposition: inline Sender: linux-omap-owner@vger.kernel.org To: Roger Quadros Cc: "tony@atomide.com" , "linux@arm.linux.org.uk" , "devicetree-discuss@lists.ozlabs.org" , "linux-usb@vger.kernel.org" , "balbi@ti.com" , "stern@rowland.harvard.edu" , Samuel Ortiz , "linux-omap@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" List-Id: devicetree@vger.kernel.org [...] > >> + > >> +- single_ulpi_bypass: Must be present if the controller contains a single > >> + ULPI bypass control bit. e.g. OMAP3 silicon <= ES2.1 > > > > Again it would be nicer to have '-' rather than '_' here. It might be worth > > prefixing this "ti,". > > Is prefixing with "ti" really required? how does it better? I thought single-ulpi-bypass sounded rather generic, but it probably is specific enough as-is. I don't know enough about USB hardware to have strong feelings either way. [...] > Thanks for the in-depth review :). You're welcome. Thanks, Mark.