Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp358753imm; Tue, 9 Oct 2018 19:50:25 -0700 (PDT) X-Google-Smtp-Source: ACcGV63snWPGo5Wt+cHseZogjAGlS8BIPgKdHT963HNcI7rUkAar2H6YErV4dIQsmDv917iFJJ6r X-Received: by 2002:a17:902:3fa5:: with SMTP id a34-v6mr31492280pld.244.1539139825404; Tue, 09 Oct 2018 19:50:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539139825; cv=none; d=google.com; s=arc-20160816; b=kXQY6jU7KTTiSz6f84wzUevEJTXQFNxWpDyJGfrJdGHsi82SjjLmvU21CgLJG2kU35 sp8NPn1CtUAi1khk4+TvagXw3H6mtOoB5TPhtEfiiaDQwWMjzME2zDvXs/KYP6Pzvxi9 jqY2ToCXf71GLiSq6meE6o7OT/tyXSj71B0ohJf7+rZ/JScdIvLhe9IIqRAB+WVTYtgg eswdXFhmKFVkqelbJXOI9Ic+dIcm3dX4YnsRuB1IE3XNtK6qlAYAADndtDVZJZzsUYmQ 0txwRZSqYFlP2G/Zmg2J4Gt2W7O1MDTWJEUyqshNxLz6LDGiP0hoBKSqpt67NQLE9RtW +E2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:dkim-signature; bh=euMYv3Bsh2iyBVECjPxyfDDrxgVokwQKgV8/BYe648s=; b=qklJP9637jo67dBc89jdpUECkpL7dS1JZFbrNKg0glIHmEAqRk4pHBdK7Fbteb63oQ 1PQaz2FCIJJ+YayvP3B/4Smy+nji+UQ10jQOe9HTOp4oVTb364g9pSaALcIWhYQJklMf rNf759maJFKKhUk/M6IoUq9s6A6sxgJaxBzpui8IX4BycKaJLEMD9X+xxigARx7N5sA5 stoF9wumyPhdklZrDUQyrnCUGdhvdflHdK7F5FyfnQ+B9HNlfSY6o8fUwhCURV43eWXA ct/QzSeWJqN0Zqh45ySOLNqCCZPksLM4LSuGXEGZu6ERFtdd5p21czwunBs5Vr7bdBLh uM+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=qtol+mSJ; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v4-v6si22083522plp.247.2018.10.09.19.50.10; Tue, 09 Oct 2018 19:50:25 -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=@gmail.com header.s=20161025 header.b=qtol+mSJ; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727168AbeJJKER (ORCPT + 99 others); Wed, 10 Oct 2018 06:04:17 -0400 Received: from mail-pl1-f195.google.com ([209.85.214.195]:37550 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725837AbeJJKEQ (ORCPT ); Wed, 10 Oct 2018 06:04:16 -0400 Received: by mail-pl1-f195.google.com with SMTP id az3-v6so1762694plb.4; Tue, 09 Oct 2018 19:44:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=euMYv3Bsh2iyBVECjPxyfDDrxgVokwQKgV8/BYe648s=; b=qtol+mSJ6IO6DWvK9/UpRUyRZMctfHCijkKTO5ODgLQtVk56XKlnPth8QgjFP/mHOt Zt0kk60qChfSOJgY/YgwXmvOLLPkgx4GWPKR+8IwSjZmioFoZJCHt/K4fX59EY3HSFac +8vd2qVV2qZiQGu8ZRwKSMaWHZvBrbOK2I3qzKOYB9Qw573tEV5Suw8NvQF2VkbcXua6 jLr32AV+7B5x+uWoXrqpiS1N3QFxLOBfxJDI1Ei6CHUSeizCTNLbe/mRUN0AB2MWKfAr baOLn4oeOQFM1Dm2ErIB83Qy01xGFeY37XVh3+9NhZixUg2jEeG7W6sDy5kD3k3gag8p 7Ubw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=euMYv3Bsh2iyBVECjPxyfDDrxgVokwQKgV8/BYe648s=; b=gupkO+QTDiuhA2Yh3XDQSwtTvkv4KKrexIwUSraYU2+WvdXBSM1vWf3OcVVAc/ZmDY VCJRVisNzybCGMrX+rJsAdfaMutxPyKtfxOYLeHrO/mu5Nu/I9HxrjJ3caixItTDZ0eJ CV1QalT8lw2OBVvhFamilS3LbD0nRCQZweSvsQhGQnQ7FOm0FW3ipVXA2PBXDNDL9Q1b CDgz5612H20m74TJiaV7hhul6YiyRgFbZLN9IQ0gHuB4Guu4ML264Z7s+PMAuyecSOXp qDH1fnLCvuPcJPQYCqCIiuEj0idOsUSjfHoQCHdm73bbPYnvF9Mypd8I/eITeddwnquw CXKw== X-Gm-Message-State: ABuFfohO7+m3ng7OmlsH/qOSMxdvrADqo0vGg+RW3bON9Y1er5ape/ey JCT7WiWgmJ+LP26JrtOELhg= X-Received: by 2002:a17:902:830a:: with SMTP id bd10-v6mr31415038plb.214.1539139459982; Tue, 09 Oct 2018 19:44:19 -0700 (PDT) Received: from [192.168.1.70] (c-24-6-192-50.hsd1.ca.comcast.net. [24.6.192.50]) by smtp.gmail.com with ESMTPSA id r18-v6sm25162222pgj.51.2018.10.09.19.44.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Oct 2018 19:44:19 -0700 (PDT) Subject: Re: [PATCH v15 06/16] of/fdt: add helper functions for handling properties To: "AKASHI, Takahiro" , Rob Herring , David Gibson , Catalin Marinas , Will Deacon , David Howells , Vivek Goyal , Herbert Xu , David Miller , dyoung@redhat.com, Baoquan He , Arnd Bergmann , Martin Schwidefsky , Heiko Carstens , prudo@linux.ibm.com, Ard Biesheuvel , James Morse , bhsharma@redhat.com, kexec@lists.infradead.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org References: <20180928064841.14117-1-takahiro.akashi@linaro.org> <20180928064841.14117-7-takahiro.akashi@linaro.org> <20181005030849.GK32578@linaro.org> <20181009003733.GN32578@linaro.org> <20181010011426.GV32578@linaro.org> From: Frank Rowand Message-ID: <1280f007-6164-dd31-b5a7-3d34f4eb2e9b@gmail.com> Date: Tue, 9 Oct 2018 19:44:17 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20181010011426.GV32578@linaro.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/09/18 18:14, AKASHI, Takahiro wrote: > Frank, Rob, > > On Tue, Oct 09, 2018 at 10:47:15AM -0700, Frank Rowand wrote: >> On 10/08/18 17:37, AKASHI, Takahiro wrote: >>> On Fri, Oct 05, 2018 at 08:23:57AM -0500, Rob Herring wrote: >>>> On Thu, Oct 4, 2018 at 10:07 PM AKASHI, Takahiro >>>> wrote: >>>>> >>>>> Rob, >>>>> >>>>> # I haven't replied to this comment yet. >>>>> >>>>> On Fri, Sep 28, 2018 at 08:44:42AM -0500, Rob Herring wrote: >>>>>> +David Gibson >>>>>> >>>>>> On Fri, Sep 28, 2018 at 1:48 AM AKASHI Takahiro >>>>>> wrote: >>>>>>> >>>>>>> These functions will be used later to handle kexec-specific properties >>>>>>> in arm64's kexec_file implementation. >>>>>>> >>>>>>> Signed-off-by: AKASHI Takahiro >>>>>>> Cc: Rob Herring >>>>>>> Cc: Frank Rowand >>>>>>> Cc: devicetree@vger.kernel.org >>>>>>> --- >>>>>>> drivers/of/fdt.c | 56 ++++++++++++++++++++++++++++++++++++++++++ >>>>>>> include/linux/of_fdt.h | 4 +++ >>>>>>> 2 files changed, 60 insertions(+) >>>>>>> >>>>>>> diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c >>>>>>> index 800ad252cf9c..c65c31562ccb 100644 >>>>>>> --- a/drivers/of/fdt.c >>>>>>> +++ b/drivers/of/fdt.c >>>>>>> @@ -25,6 +25,7 @@ >>>>>>> #include >>>>>>> #include >>>>>>> #include >>>>>>> +#include >>>>>>> >>>>>>> #include /* for COMMAND_LINE_SIZE */ >>>>>>> #include >>>>>>> @@ -1323,3 +1324,58 @@ late_initcall(of_fdt_raw_init); >>>>>>> #endif >>>>>>> >>>>>>> #endif /* CONFIG_OF_EARLY_FLATTREE */ >>>>>>> + >>>>>>> +#define FDT_ALIGN(x, a) (((x) + (a) - 1) & ~((a) - 1)) >>>>>>> +#define FDT_TAGALIGN(x) (FDT_ALIGN((x), FDT_TAGSIZE)) >>>>>>> + >>>>>>> +int fdt_prop_len(const char *prop_name, int len) >>>>>>> +{ >>>>>>> + return (strlen(prop_name) + 1) + >>>>>>> + sizeof(struct fdt_property) + >>>>>>> + FDT_TAGALIGN(len); >>>>>> >>>>>> Looks like you are using this to calculate how much space you need to >>>>>> allocate in addition to the current DTB for a couple of new or >>>>>> replaced properties. I'm not sure that this calculation is completely >>>>>> accurate. And it is strange there doesn't seem to be any libfdt >>>>>> function for this already. It would be simpler to just add some fixed >>>>>> additional amount. >>>>>> >>>>>> Maybe David G has comments on this? >>>>>> >>>>>>> +} >>>>>>> + >>>>>> >>>>>> The rest of this should go in drivers/of/fdt_address.c. Ultimately, it >>>>>> should go into libfdt, but I'm fine with having it in the kernel for >>>>>> now. >>>>> >>>>> I'd like to have this function in the kernel for now. >>>>> >>>>>>> +static void fill_property(void *buf, u64 val64, int cells) >>>>>>> +{ >>>>>>> + __be32 val32; >>>>>>> + >>>>>>> + while (cells) { >>>>>>> + val32 = cpu_to_fdt32((val64 >> (32 * (--cells))) & U32_MAX); >>>>>>> + memcpy(buf, &val32, sizeof(val32)); >>>>>>> + buf += sizeof(val32); >>>>>> >>>>>> This is kind of hard to read. I would copy u-boot's fdt_pack_reg function. >>>>> >>>>> Are you sure? >>>>> I originally implemented this function in a similar way that fdt_pack_reg() >>>>> was, but, you suggested, in your past comment[1], that we'd be better to >>>>> have of_read_number()-like implementation. >>>>> >>>>> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2018-May/579118.html >>>> >>>> Yeah, you're right. Plus, I'm not sure the u-boot one would work for >>>> unaligned accesses with armv5 and earlier h/w. >>>> >>>> My only comment then is I think you can drop the U32_MAX masking. >>> >>> Okay, then I will leave this function, yet renaming it to >>> cpu64_to_fdt_cells() after Frank's comment. >> >> I have second guessed myself and do not like the name I suggested >> because what the function really does is either cpu32 to be32 or >> cpu64 to be64. > > Okay. > >> I agree with Rob that readability is important here. Instead of >> having a fill_property() function, how about having inline code, >> something like (untested even for thinkos): >> >> prop = buf; >> >> if (addr_cells == 1) { >> *(__be32 *)prop = cpu32_to_be32(addr); >> prop += 4; >> } else { >> *(__be64 *)prop = cpu64_to_be64(addr); >> prop += 8; >> } >> >> if (size_cells == 1) >> *(__be32 *)prop = cpu32_to_be32(size); >> else >> *(__be64 *)prop = cpu64_to_be64(size); >> >> You might want to also give Rob a chance to bike shed on this >> suggestion. > > Basically, I don't care either way, but what Rob suggested > is that some architecture(s) might not handle correctly > unaligned memory access here. Good point about unaligned memory access. That rules out my suggestion above. But if using the fill_property() implementation, either come up with a name that better describes what the function does or add a function header comment that gives the reader a clue as to what the function accomplishes. -Frank > I just want to stay tuned with Rob. > > Thanks, > -Takahiro Akashi > >> -Frank >> >>> >>> Thanks, >>> -Takahiro Akashi >>>> >>>> Rob >>> >> >