Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752639Ab3JVKsw (ORCPT ); Tue, 22 Oct 2013 06:48:52 -0400 Received: from drsnuggles.stderr.nl ([94.142.244.14]:41059 "EHLO drsnuggles.stderr.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751659Ab3JVKst (ORCPT ); Tue, 22 Oct 2013 06:48:49 -0400 Date: Tue, 22 Oct 2013 12:48:29 +0200 From: Matthijs Kooijman To: Kishon Vijay Abraham I Cc: Matt Porter , Rob Herring , Pawel Moll , Mark Rutland , Stephen Warren , Ian Campbell , Felipe Balbi , Greg Kroah-Hartman , Paul Zimmerman , Devicetree List , Linux USB List , Linux ARM Kernel List , Linux Kernel Mailing List Subject: Re: [RFC] Does PHY UTMI data width belong to DWC2 or PHY binding? Message-ID: <20131022104829.GF15425@login.drsnuggles.stderr.nl> Mail-Followup-To: Matthijs Kooijman , Kishon Vijay Abraham I , Matt Porter , Rob Herring , Pawel Moll , Mark Rutland , Stephen Warren , Ian Campbell , Felipe Balbi , Greg Kroah-Hartman , Paul Zimmerman , Devicetree List , Linux USB List , Linux ARM Kernel List , Linux Kernel Mailing List References: <20131018141221.GH2721@beef> <5264F37E.9060307@ti.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="L2Brqb15TUChFOBK" Content-Disposition: inline In-Reply-To: <5264F37E.9060307@ti.com> X-PGP-Fingerprint: 7F6A 9F44 2820 18E2 18DE 24AA CF49 D0E6 8A2F AFBC X-PGP-Key: http://www.stderr.nl/static/files/gpg_pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -2.6 (--) X-Spam-Report: Spamchecked on "mail.drsnuggles.stderr.nl" pts rule name description ---- ---------------------- ------------------------------------------- -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.0 AWL AWL: From: address is in the auto white-list Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1482 Lines: 43 --L2Brqb15TUChFOBK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Kishon, On Mon, Oct 21, 2013 at 02:57:26PM +0530, Kishon Vijay Abraham I wrote: > I think it makes sense to keep the data width property in the dwc2 node itself. > I mean it describes how the dwc2 IP is configured in that particular SoC (given > that it can be either <8> or <16>). If I'm reading the RT3052 datasheet correctly (GHWCFG4 register), the IP can be configured for 8, 16 or 8 _and_ 16. In the latter case, the "8 and 16 supported" would make sense as a property of dwc2 (though this value should be autodetectable through GHWCFG4), while the actual 8 or 16 supported by the PHY would make sense as property of a phy. Note sure if this is really useful in practice as well, or if just setting the actual width to use on dwc2 makes more sense... Gr. Matthijs --L2Brqb15TUChFOBK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAlJmV/0ACgkQz0nQ5oovr7wK2wCgn3SiRjbqky+YLRJ/40XWcUpN n+AAn0PGfchNovg/dACI0f/vrn8YK7KB =jIvk -----END PGP SIGNATURE----- --L2Brqb15TUChFOBK-- -- 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/