From mboxrd@z Thu Jan 1 00:00:00 1970 From: maxime.ripard@free-electrons.com (Maxime Ripard) Date: Thu, 30 Jun 2016 22:41:52 +0200 Subject: [linux-sunxi] Re: [PATCH 06/14] ARM: dts: sun8i: Add cpu0 label to sun8i-h3.dtsi In-Reply-To: References: <20160623192104.18720-1-megous@megous.com> <20160623192104.18720-7-megous@megous.com> <20160625070208.GA4000@lukather> <380ebf34-fd4a-ea2d-f9cf-68b8ede44757@megous.com> <20160629204553.GJ6095@lukather> Message-ID: <20160630204152.GD5485@lukather> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Jun 30, 2016 at 01:04:40PM +0200, Michal Suchanek wrote: > > You're probably right. Operating points should be part of h3.dtsi, and > > if some board is particularly bad, and can't handle being above certain > > frequency safely, due to thermal design issues, we can override > > operating points in its dts file. > > > > Can you override them? > > AFAIK you cannot replace a property set in SoC file in a board file. You totally can, we have litterally dozens of examples of that already. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Ripard Subject: Re: Re: [PATCH 06/14] ARM: dts: sun8i: Add cpu0 label to sun8i-h3.dtsi Date: Thu, 30 Jun 2016 22:41:52 +0200 Message-ID: <20160630204152.GD5485@lukather> References: <20160623192104.18720-1-megous@megous.com> <20160623192104.18720-7-megous@megous.com> <20160625070208.GA4000@lukather> <380ebf34-fd4a-ea2d-f9cf-68b8ede44757@megous.com> <20160629204553.GJ6095@lukather> Reply-To: maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1sNVjLsmu1MXqwQ/" Return-path: Sender: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: Michal Suchanek Cc: megous-5qf/QAjKc83QT0dZR+AlfA@public.gmane.org, Chen-Yu Tsai , dev , linux-arm-kernel , Rob Herring , Mark Rutland , Russell King , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , open list List-Id: devicetree@vger.kernel.org --1sNVjLsmu1MXqwQ/ Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline On Thu, Jun 30, 2016 at 01:04:40PM +0200, Michal Suchanek wrote: > > You're probably right. Operating points should be part of h3.dtsi, and > > if some board is particularly bad, and can't handle being above certain > > frequency safely, due to thermal design issues, we can override > > operating points in its dts file. > > > > Can you override them? > > AFAIK you cannot replace a property set in SoC file in a board file. You totally can, we have litterally dozens of examples of that already. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com --1sNVjLsmu1MXqwQ/-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752589AbcF3Ul4 (ORCPT ); Thu, 30 Jun 2016 16:41:56 -0400 Received: from down.free-electrons.com ([37.187.137.238]:56675 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752073AbcF3Uly (ORCPT ); Thu, 30 Jun 2016 16:41:54 -0400 Date: Thu, 30 Jun 2016 22:41:52 +0200 From: Maxime Ripard To: Michal Suchanek Cc: megous@megous.com, Chen-Yu Tsai , dev , linux-arm-kernel , Rob Herring , Mark Rutland , Russell King , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , open list Subject: Re: [linux-sunxi] Re: [PATCH 06/14] ARM: dts: sun8i: Add cpu0 label to sun8i-h3.dtsi Message-ID: <20160630204152.GD5485@lukather> References: <20160623192104.18720-1-megous@megous.com> <20160623192104.18720-7-megous@megous.com> <20160625070208.GA4000@lukather> <380ebf34-fd4a-ea2d-f9cf-68b8ede44757@megous.com> <20160629204553.GJ6095@lukather> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1sNVjLsmu1MXqwQ/" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --1sNVjLsmu1MXqwQ/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 30, 2016 at 01:04:40PM +0200, Michal Suchanek wrote: > > You're probably right. Operating points should be part of h3.dtsi, and > > if some board is particularly bad, and can't handle being above certain > > frequency safely, due to thermal design issues, we can override > > operating points in its dts file. > > >=20 > Can you override them? >=20 > AFAIK you cannot replace a property set in SoC file in a board file. You totally can, we have litterally dozens of examples of that already. Maxime --=20 Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com --1sNVjLsmu1MXqwQ/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXdYQQAAoJEBx+YmzsjxAgreAQAL/SaT1Rqb4KaN0HmNarirKY ORV0EZrLHt/aAXShyX/HgNxgpZjVxFPq4BKtscExQvQVsoZ3LXbisJdd4dzfpFC8 WVf1f4ris8XFrvTO5CZJHcvg6sw0izFRR4tZ8B4JbKSO1pbgqWWIseI7voIJGoDT rdjOOHW1WilGVSbNSJqARsWiTDt+IDmvWf9WeXZgBOVQDLIFbXLrPimWsDbhEBFz 5lr1S/7NfA6ds2mqa12OCpgnRnrK0bbA/DmDaEoTYYZYw3F9LiTWASoSfKlm4Mxr 8YVgbSrRIEnlhbDkOaJ+d+/7JVwNrMeCemN2h0Atv1zNcJH2yywO7KDJJ0Ew/OA5 w1734I/ZZi8TrZpgj07scetmtu7KDbyl731kDK4Y/lwGDXpD9AIzaKeXmUM8XuCB UH1ufYsNKmxa6xhgIpTdPu0cwBNphmPVTrQQb/jnAphkLXa3QzOBW8jiur+/Rrb6 s70WKfAEPtOyJ7y3UvqNVLex8jWKTSlEYcL+LCOXZgqzC81icuocxUFHJimlv2/1 YA3PF7/KKa6PawFVczyDTA98QHigLcCJCFVv2hMvu86KAR7JxgMuwGsFshUU+xv3 U7l4eCO6Ayh3HfxsR2ZxqqVM+7Lm1zCDe+YiLx6T7Wk2drokyNn0ZVNHizFFGTso TXlMr46jwVJ+uDwwvcLz =/r3M -----END PGP SIGNATURE----- --1sNVjLsmu1MXqwQ/--