From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751522AbcBKKce (ORCPT ); Thu, 11 Feb 2016 05:32:34 -0500 Received: from down.free-electrons.com ([37.187.137.238]:46096 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750857AbcBKKcc (ORCPT ); Thu, 11 Feb 2016 05:32:32 -0500 Date: Thu, 11 Feb 2016 11:32:30 +0100 From: Maxime Ripard To: Andre Przywara Cc: Chen-Yu Tsai , linux-sunxi@googlegroups.com, Arnd Bergmann , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Catalin Marinas , Will Deacon , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree@vger.kernel.org Subject: Re: [PATCH 11/11] arm64: dts: add Pine64 support Message-ID: <20160211103230.GM31506@lukather> References: <1454348370-3816-1-git-send-email-andre.przywara@arm.com> <1454348370-3816-12-git-send-email-andre.przywara@arm.com> <20160205090337.GB1139@lukather> <56B47391.1040709@arm.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="np6E2rbShIadjoVu" Content-Disposition: inline In-Reply-To: <56B47391.1040709@arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --np6E2rbShIadjoVu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Andre, On Fri, Feb 05, 2016 at 10:04:01AM +0000, Andre Przywara wrote: > >> +&uart0 { > >> + pinctrl-names =3D "default"; > >> + pinctrl-0 =3D <&uart0_pins_a>; > >> + status =3D "okay"; > >> +}; > >> + > >> +&uart2 { > >> + pinctrl-names =3D "default"; > >> + pinctrl-0 =3D <&uart2_pins>; > >> + status =3D "okay"; > >> +}; > >> + > >> +&uart3 { > >> + pinctrl-names =3D "default"; > >> + pinctrl-0 =3D <&uart3_pins_a>; > >> + status =3D "okay"; > >> +}; > >> + > >> +&uart4 { > >> + pinctrl-names =3D "default"; > >> + pinctrl-0 =3D <&uart4_pins>; > >> + status =3D "okay"; > >> +}; > >=20 > > Our policy for boards with "open" pin headers the user can plug > > anything he wants is that unless the pin is explicitly dedicated to > > that usage, we simply leave them aside so that we don't enforce > > anything. >=20 > Makes sense, I just wonder what a user is expected to do if she wants to > use the serial ports? > Hack the DT? > Use U-Boot to create those nodes on the fly? > Use overlays? > Directly setup serial ports from userland? (thinking of this bloody > mechanism x86 (used to?) have) Until we have a configfs overlay interface, then yeah, we have to hack the DT. That's not very much different than what you'd have to do if you wanted some other bus exposed on those pins though. Thanks! Maxime --=20 Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com --np6E2rbShIadjoVu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJWvGM+AAoJEBx+YmzsjxAgR78P/jtSs4XS7A9cBB8zFCKv/RK3 4HaxJNbfxHJvtxyCR/ZB7hM6+aSGU6OcKAQMWqiUnS4IKHb/2Wen4hil2Ga5BXro D5fo2yWrd0KHPq8xzDaMWylD/37u0jlG1B4BDIT3xlSsjIyzvipyXevZovFbLzPa pXg2/Z6lRNs8kUXW8JQ/4uq1gB3vaJG5EHTnJeaPIghGx5wjDyup0lpD+ol6thaB Cpd9HeBQHgvLqVtpOP4NVoTCz28avWzh4jRyq06/thjdrVpWIDSS/LW/bw6clY7M 6vTYaGFDt0BVwnsWq/pa17xizBiOzji72AebT63OMkQMLQ+qjh9cwtAI1zhy3Ozr o7xywYqQnNiXuz+ZMrWLJf83btT/h2CxY8JybD8g0LfBM7aYW5U7+xGw7muco+BF 7pPIeiHF1MPWve7bYouIwZBvEzrfQC5v2PAiogJHB5jw2eP9YPPzOqauglL28yaA WA8GK7wheTrff0j429YbKw/UOcW6HXUGxJpyizDSBKmGCYI9ZH018jB1LEE2JAb4 wd3hNfw9aLIFHonDq+96T7NLEBR8iy53uG3mHpMyIvcAF6j1Y0TyGGm2LXezk4au g2yAixUboI1heobT7y6EuNrnSjee6Dzcm1XhbvaJUQiXo6lfQVTTgefUBZzP+3DO nKKa5d6U3Ju0vOZxCsLw =+G4b -----END PGP SIGNATURE----- --np6E2rbShIadjoVu--