Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp3260624imm; Mon, 10 Sep 2018 13:49:35 -0700 (PDT) X-Google-Smtp-Source: ANB0Vda3nMh85I6F2w2BZMxZGKHLCbsF7Kz1Ej0SJLXPF56gC6Axh9Oef05cdncUq5l1zlNOlhrX X-Received: by 2002:a62:6781:: with SMTP id t1-v6mr25779033pfj.200.1536612575475; Mon, 10 Sep 2018 13:49:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536612575; cv=none; d=google.com; s=arc-20160816; b=GlvzdBYdB+4W+28tKmMAqbOHKddOypLI+ir1ZlZ2l57PWSczFgddZ7ssNIcshXWZ2C ftMdSTWpCNvnBxAHbdTQJ9wWLThNEgWYq1Z3SjhUKZv01QoArUmSSlZGV5H4v4Xs8SoM nPjKUr8fzWXUfc/RjzngMUvUkg8YgawldEd6h6bXx20PlezaIKP4T1u48WeKId0PJIEH QIl2LaJ/Y7jwjJVJZfhhVCY4mu9l+zCtvFMVgrzU7NEHZKd6LeUMwcf02cFitzezfuSb E11ZK6aDiIWgbKUnLW54oxKViH6e3tz8x4upxKSQdAAprmGTrJJBh0ZtnUS/rKQbJXAE FK3w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=qXybzrn47r2UwyUE/7E1D73V+iIG0bGVkgw9Jn9KH88=; b=ggAuHv7plz6luOm2Hyw1nm+UDFKYhhJLFLgjLiTG4jpKIkbn+lr/xLpDy0Up6suuwL VC9irTyB3fSPlCsXdVy76Me+ey1K70xJAehuIjnSVArrMFa/fbqLBlP9d44kke7IDT5Y vD7d7QBlp3n9j/LChFsFkW3AZ25O6VKrK1B/JcDrmHSQym7Xt4YCnITQmaCmtzqoVJju yTJG/pNQ4cnP8I8cNeT/uA4ooFakmsOmhKdJZoQmoJfNg1R/yHdnuWHUgRfUHvE3Nmy8 iOI2Z96gxSH69hAIUhKFUph0WBjK+PdUmUhTbGqJK9Beg36GiVA4DLtzZs14B5UDbiGy CtDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=VgtqcP1w; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q132-v6si19104409pfc.159.2018.09.10.13.49.18; Mon, 10 Sep 2018 13:49:35 -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=@kernel.org header.s=default header.b=VgtqcP1w; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726612AbeIKBpG (ORCPT + 99 others); Mon, 10 Sep 2018 21:45:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:51042 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726150AbeIKBpF (ORCPT ); Mon, 10 Sep 2018 21:45:05 -0400 Received: from mail-qt0-f169.google.com (mail-qt0-f169.google.com [209.85.216.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 7796620865; Mon, 10 Sep 2018 20:49:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1536612553; bh=qXybzrn47r2UwyUE/7E1D73V+iIG0bGVkgw9Jn9KH88=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=VgtqcP1wPYW11FbZIbig7wepKD4wAd+vxUeJH9XU8N3QvLuu+CgPPMhg3/OEIhHA6 dqyI9WaGtXkpEnKXr74YOEwLT5LOBIC+YKH1Q6aMRJ7sDL8PJ+0Z1TDmZplimG+i5s 8XxurTik/b2YpxDZe5hosw/MOmH/Q0wNzWiWecOw= Received: by mail-qt0-f169.google.com with SMTP id l42-v6so590886qtf.13; Mon, 10 Sep 2018 13:49:13 -0700 (PDT) X-Gm-Message-State: APzg51DDXg+ZXeCIIkT4zpnqyqy7d/6wpej6zcdEm+Yb+VLpfj+/s7NZ XE9yT/HDG2ozL4sRvRgJrjw6slzrEtqQYnjE/g== X-Received: by 2002:a0c:e9ce:: with SMTP id q14-v6mr16313165qvo.106.1536612552531; Mon, 10 Sep 2018 13:49:12 -0700 (PDT) MIME-Version: 1.0 References: <20180905193738.19325-1-robh@kernel.org> <20180905193738.19325-9-robh@kernel.org> <8b227f8c-f351-18da-b55d-e8979281f510@xilinx.com> In-Reply-To: <8b227f8c-f351-18da-b55d-e8979281f510@xilinx.com> From: Rob Herring Date: Mon, 10 Sep 2018 15:49:01 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 08/21] microblaze: get cpu node with of_get_cpu_node To: Michal Simek Cc: devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 10, 2018 at 9:56 AM Michal Simek wrote: > > On 5.9.2018 21:37, Rob Herring wrote: > > "device_type" use is deprecated for FDT though it has continued to be used > > for nodes like cpu nodes. Use of_get_cpu_node() instead which works using > > node names by default. This will allow the eventually removal of cpu > > device_type properties. > > > > Also, fix a leaked reference by adding a missing of_node_put. > > > > Cc: Michal Simek > > Signed-off-by: Rob Herring > > --- > > Please ack and I will take via the DT tree. This is dependent on the > > first 2 patches. > > I have tested it and it is align with the spec and all dtses generated > before 2015 will work without any issue. > In 2015 new device tree generator was introduced and it is not adding > reg property to cpu node which is required by this change. > This will be fixed but that means that all generated dtses from 2015 are > affected. Patch 2 was supposed to handle that case. However, it does expect that there should be an #address-cells equal to 0 in that case. Is that not a valid assumption? > That's why will be great if you can also change that pr_err message to > mentioned to also check reg property to give users a chance to fix it > properly. Error log below. I don't think breaking users is good. I could make this a find by path (/cpus/cpu) instead or just drop it for microblaze. It doesn't really affect my plans for removing device_node.type ptr. Rob > Anyway here is my > Tested-by: Michal Simek > > Thanks, > Michal