Received: by 10.223.164.221 with SMTP id h29csp4806452wrb; Fri, 20 Oct 2017 01:07:29 -0700 (PDT) X-Received: by 10.84.176.163 with SMTP id v32mr3561862plb.175.1508486849578; Fri, 20 Oct 2017 01:07:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508486849; cv=none; d=google.com; s=arc-20160816; b=YNsvkks1Bbp0kyn4oFKPeZKnfmJ9Nt3Bo7wJkCPHx6W6mA1fACTVN+IRSvo+zB4q45 pXSYhj8jibqKTWk1nYdvAqOtlVsFhsHaRL666ka0oNwjM/TqDxPTrwnwQ4aJyhVOgyAX wDXxilD1NzQXpe9dbS4lXwRm6Dbyp0eW9ayrh5po9uZok6aZliU2UCj7eI1yI1TyIm2N ztwbXagY6l3bSAygWOH936U8nq/78WGKARPsRqR5I9iSieDcXYQ/cHLQRErkKGxqMqSH I8vsEIh0dmjF5sIoMNh8CyvX/WUGK08D4vab7s7Vc2k5qOmSxYsVfgqsITjubY2NfuiE iSsQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version:dkim-signature:arc-authentication-results; bh=Wuw8qd88lBNmLFWNMwxcAohbgn4u9i3/o1hkdYDvot4=; b=I/3ZUfy7LBsR5PVaVCqAThtc/HKREPoAZx9+Euqo1t7W21mjBV+YeiOU6olu4NhfS7 QoefkW9iYwZfgjtAPtO5YEab1HiEdM0CBJtWgDXWNH7Pt77WPrLBJDS3658sbuH8MiGW 7mqdWkgJT8gjtpGZEgniIg+NFTv0+chCtDSwSwhrQlDUzKe3T5UpF6DiglTOLBSOGy0V OeWzRL1vyzifqyMt0cHRkNpgoeAJaEbnymnKkgbXskxqAk0JVnDgy7BnN0Rt5ymJRJni CAim5JhXwROS+WxQbdDZDfXMKdN+lgZeC8WIbqkM4RoBMt8V4sySpDT7vMSDptqLbs0k XGBA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@konsulko.com header.s=google header.b=eACxIBVR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e9si325298pln.708.2017.10.20.01.07.15; Fri, 20 Oct 2017 01:07:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@konsulko.com header.s=google header.b=eACxIBVR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752317AbdJTIGf (ORCPT + 99 others); Fri, 20 Oct 2017 04:06:35 -0400 Received: from mail-wr0-f196.google.com ([209.85.128.196]:44494 "EHLO mail-wr0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751989AbdJTIG2 (ORCPT ); Fri, 20 Oct 2017 04:06:28 -0400 Received: by mail-wr0-f196.google.com with SMTP id z55so4540049wrz.1 for ; Fri, 20 Oct 2017 01:06:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=konsulko.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Wuw8qd88lBNmLFWNMwxcAohbgn4u9i3/o1hkdYDvot4=; b=eACxIBVRFE7YWbjj46qv4MPOMwEcQ+YXIFqZeILESm/ocCiULp8jH3Nd6hLDafziMk ToTDsaduLLeuR/T3irzZXuAal3vxefUZOZZG/M5f38i2nPonMulPOhWZxN40i/9jLuvT bL4TA6ccAumaHk/3a032Frg+Q8vd0KKUCq6KY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Wuw8qd88lBNmLFWNMwxcAohbgn4u9i3/o1hkdYDvot4=; b=GdZa7epFQuNmNHbIpRbEbcKfR7e2AoobUkT0iLgDuTGNa8TzfCsbkIZslJWJWu4D2K 06KsOmMipYCdAMOcKYOYfRswtFzh6XzoxpPsOeenhJq+O31JtXuO6+eSYVYcbp1Ypq81 aFFEoRtbJvE2YcCsnFo7smbiMMMFrK4uxp+Q6fhA44qCkrfFK7x+H4mh2yuxvPOR0CN6 4/UbLmd9qpoxDAjMYvRJnj073xla4ogmxT/BtWYXoy4XGXCTOojfeBftrWuvOu5MvrU7 5QbkARjaQto3llSgeEpthbN+Ldzc7TsgWn0XaFXuk+PVU0U5N3LFhzN6s3KJIeEp3bBT RD2Q== X-Gm-Message-State: AMCzsaXdGDgWF0lnPxJd82WFLIxm2FcVwZFdFGG2PBZRnf2izTDc8XFT HRkxifpvKQ9vGi0i+RGl3g56W+T1ToY= X-Google-Smtp-Source: ABhQp+TDmvhe2Z2VokW+LdG64pxB3jMkjTIZd/TLZySduhvyAcwncI3exTJuC3V7nndIy0nG32DOHg== X-Received: by 10.223.185.33 with SMTP id k30mr1709155wrf.40.1508486787626; Fri, 20 Oct 2017 01:06:27 -0700 (PDT) Received: from [192.168.2.2] ([195.97.110.117]) by smtp.gmail.com with ESMTPSA id 31sm436439wrr.6.2017.10.20.01.06.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Oct 2017 01:06:26 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [PATCH v2 5/5] of/fdt: only store the device node basename in full_name From: Pantelis Antoniou In-Reply-To: <59E91D4D.8000200@gmail.com> Date: Fri, 20 Oct 2017 11:06:23 +0300 Cc: Moritz Fischer , Rob Herring , Alan Tull , "devicetree@vger.kernel.org" , Michael Ellerman , linuxppc-dev , linux-kernel , Benjamin Herrenschmidt , Paul Mackerras , David Laight , linux-fpga@vger.kernel.org Content-Transfer-Encoding: quoted-printable Message-Id: <331B5EB4-9C97-4B2C-9B54-BF648F309A50@konsulko.com> References: <20170821151651.25096-1-robh@kernel.org> <20170821151651.25096-6-robh@kernel.org> <59E69786.2030406@gmail.com> <1508341985.25643.12.camel@hp800z> <4393AFA4-620F-4C21-995D-A9806DAE1990@konsulko.com> <20171019200615.GA10743@tyrael.ni.corp.natinst.com> <59E91D4D.8000200@gmail.com> To: Frank Rowand X-Mailer: Apple Mail (2.3273) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Frank, > On Oct 20, 2017, at 00:46 , Frank Rowand = wrote: >=20 > On 10/19/17 13:06, Moritz Fischer wrote: >=20 > < snip > >=20 >> We also have plenty of code that is just not aware of overlays, and >> assumes certain parts of the tree to stay static. >=20 > I would state that somewhat differently. :-) There is very little > code that is aware of overlays, and most code assumes the device tree > does not change after early boot. >=20 > This is one of the areas where the creation of overlays needs to be > done with care. >=20 Correct. But this is not breaking the kernel. In general we have the following case where we load overlays (at least well formed overlays that are not doing stupid things). 1. Activation of a new device. Usually this works since is something = that=E2=80=99s normally done at boot. 2. Deactivation of a device. This might break because the removal paths of platform device especially are not well tested (or never executed for = that matter). 3. Modification of properties in an already activated device. If the = device driver has not installed a device tree modification hook (as in almost 99% of = the devices) it will do absolutely nothing, since the device tree is parsed only at = probe time. I can argue that for these cases we could have a catch-all hook that = displays a message that nothing happened. 4. Modification of some part of the tree that=E2=80=99s not part of a = device driver, perhaps the aliases or chosen node. This may potentially be harmful or harmless = depending on what has been modified. For instance modifying an already existing alias = might cause internal inconsistency about device naming, while adding a new aliases = should be harmless. This is a matter of policy per board, whether to allow or not. Are there other cases that are potentially more harmful? >=20 >> I ran into that issue when I tried to add thermal zones via an = overlay, >> I've been investigating how to fix the thermal framework to work with >> overlays since then and have some partially working code. >> Currently the thermal framework parses the thermal-zones node at = boot, >> and assumes this stays static. This breaks with overlays. >>=20 >> I agree we eventually need to fix the parts that break when we use >> overlays. >=20 Regards =E2=80=94 Pantelis From 1581727945082203622@xxx Thu Oct 19 22:48:36 +0000 2017 X-GM-THRID: 1576354368386704057 X-Gmail-Labels: Inbox,Category Forums