From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752193Ab1GTWXS (ORCPT ); Wed, 20 Jul 2011 18:23:18 -0400 Received: from hqemgate04.nvidia.com ([216.228.121.35]:1697 "EHLO hqemgate04.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751593Ab1GTWXQ convert rfc822-to-8bit (ORCPT ); Wed, 20 Jul 2011 18:23:16 -0400 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Wed, 20 Jul 2011 15:23:08 -0700 From: Andrew Chew To: "'Grant Likely'" CC: "olof@lixom.net" , Stephen Warren , Dan Willemsen , Rhyland Klein , Venkat Moganty , "devicetree-discuss@lists.ozlabs.org" , "linux-tegra@vger.kernel.org" , "linux-usb@vger.kernel.org" , "linux-kernel@vger.kernel.org" Date: Wed, 20 Jul 2011 15:23:07 -0700 Subject: RE: [PATCH 1/3 v2] usb: tegra20-ehci: Add devicetree support. Thread-Topic: [PATCH 1/3 v2] usb: tegra20-ehci: Add devicetree support. Thread-Index: AcxHF/dB+sbXVNoRSQiKUl6LNrkNkwAEu7sQ Message-ID: <643E69AA4436674C8F39DCC2C05F76383CF0DD2279@HQMAIL03.nvidia.com> References: <1311190690-18334-1-git-send-email-achew@nvidia.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > +Required properties for type = "utmi".  These values are > derived from > > +characterization by system engineering. > > + - hssync_start_delay > > + - idle_wait_delay > > + - elastic_limit > > + - term_range_adj > > + - xcvr_setup > > + - xcvr_lsfslew > > + - xcvr_lsrslew > > All of these custom properties should be prefixed with "nvidia," to > avoid namespace collisions. Are you saying we should prefix with "nvidia," on ALL of the properties I've defined for the tegra20-ehci node? Or specifically those seven that you pointed out? Because I don't see a difference in terms of "custom"-ality between say, hssync-start-delay, and the other stuff like phy-type, mode, power-down-on-bus-suspend, and the reset-gpio and clk from phy-type=ulpi...unless we're considering stuff like phy-type to be a standard USB host controller node property.