Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2114075imu; Sat, 5 Jan 2019 15:09:55 -0800 (PST) X-Google-Smtp-Source: AFSGD/Wz75pmqHFL2PG709ImJnazz57/NDaK6sQe0s8AMCuwd/UtlqEVGVL9vwbupE6Tth5wb/yj X-Received: by 2002:a62:2a4b:: with SMTP id q72mr57018685pfq.61.1546729795010; Sat, 05 Jan 2019 15:09:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546729794; cv=none; d=google.com; s=arc-20160816; b=a1kBBfUfzrTENfrfqxR7+nAvHBLpbEbCTVBF6ePEO9mpFtZh357Nz7s7O7UgzB/Tft Wb9y9xu5rZ55odwFFX27N9nc6HOY0qXHQgU3JC2agIRehhlY2WZHwElm/b7OYZwRvt6f Hq9xjuKeqj0sJndzPIRrbwPk+h7eMGJ3Gwucrs+9fPEUGtjWpGKqZNhifZ0UeeLgu5Sj XS4VARW2VP3Sqmd1nzAtoVDaaG1J9svUTgouFmSccE7dKDhvmEStIjPD62fTTcGVbrDG YoSuXUvRRMHWv+HGFO6EsXGA4uLDnAyufg1AzY0pqaHaFNhpDZyaW1YoRBXdryMPTsHo 9ykQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:message-id :in-reply-to:subject:cc:to:from:date; bh=izkave6YXTqWoJ8qd11BaaZ+yzhTV5r8pwkvWgTXESM=; b=lQU+yGmd5eHvQnXkpP7j3FlgCeyD/JOkfMelhKxBje/N05pxkodm9etH7Ql3H1Xvsj niSxAkn2Ng0EBexv6yMFJBFDpQAar6kJu7soZrVaR3H+PexRFEbALgfb1GcrkA5cVtUg Xq11Dau+iQ6It0xisbelIE3tj1PZjAzh7MHwdFdVNn/234NsbMEjIa1hoYQFvhFyRSJ5 u+i/XtVKfPkq0Xdci3QjcN5QnRPiwxzH8lVsRtAM6cIksVr2kI6eYRM0kI0MZT9rISKh VosIoO4tB7dyKbwxhgXpzG1iUO2OBCsA6CTX1Yxu6BBHPyzWUUgtZTMzq/SBh2TnGn3E SmDg== ARC-Authentication-Results: i=1; mx.google.com; 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 w11si39127918pgf.452.2019.01.05.15.09.23; Sat, 05 Jan 2019 15:09:54 -0800 (PST) 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; 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 S1726375AbfAEXGA (ORCPT + 99 others); Sat, 5 Jan 2019 18:06:00 -0500 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:42840 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726357AbfAEXGA (ORCPT ); Sat, 5 Jan 2019 18:06:00 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by kvm5.telegraphics.com.au (Postfix) with ESMTP id 09123272DE; Sat, 5 Jan 2019 18:05:50 -0500 (EST) Date: Sun, 6 Jan 2019 10:06:24 +1100 (AEDT) From: Finn Thain To: LEROY Christophe , Arnd Bergmann cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-m68k@lists.linux-m68k.org, Bartlomiej Zolnierkiewicz , Michael Ellerman , Paul Mackerras , Benjamin Herrenschmidt , Greg Kroah-Hartman Subject: Re: [PATCH v8 20/25] powerpc, fbdev: Use arch_nvram_ops methods instead of nvram_read_byte() and nvram_write_byte() In-Reply-To: Message-ID: References: <7e8eb87ea829c03941c895c968df2ebd0f80512f.1545784679.git.fthain@telegraphics.com.au> <20181229180236.Horde.idY3gOIzkSWywjIrqlXJMA1@messagerie.si.c-s.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 30 Dec 2018, I wrote: > On Sat, 29 Dec 2018, LEROY Christophe wrote: > > > Finn Thain a ?crit?: > > > > > Make use of arch_nvram_ops in device drivers so that the nvram_* function > > > exports can be removed. > > > > > > Since they are no longer global symbols, rename the PPC32 nvram_* functions > > > appropriately. > > > > > > Signed-off-by: Finn Thain > > > --- > > > arch/powerpc/kernel/setup_32.c | 8 ++++---- > > > drivers/char/generic_nvram.c | 4 ++-- > > > drivers/video/fbdev/controlfb.c | 4 ++-- > > > drivers/video/fbdev/imsttfb.c | 4 ++-- > > > drivers/video/fbdev/matrox/matroxfb_base.c | 2 +- > > > drivers/video/fbdev/platinumfb.c | 4 ++-- > > > drivers/video/fbdev/valkyriefb.c | 4 ++-- > > > 7 files changed, 15 insertions(+), 15 deletions(-) > > > > > > diff --git a/arch/powerpc/kernel/setup_32.c b/arch/powerpc/kernel/setup_32.c > > > index e0d045677472..bdbe6acbef11 100644 > > > --- a/arch/powerpc/kernel/setup_32.c > > > +++ b/arch/powerpc/kernel/setup_32.c > > > @@ -152,20 +152,18 @@ __setup("l3cr=", ppc_setup_l3cr); > > > > > > #ifdef CONFIG_GENERIC_NVRAM > > > > > > -unsigned char nvram_read_byte(int addr) > > > +static unsigned char ppc_nvram_read_byte(int addr) > > > { > > > if (ppc_md.nvram_read_val) > > > return ppc_md.nvram_read_val(addr); > > > return 0xff; > > > } > > > -EXPORT_SYMBOL(nvram_read_byte); > > > > > > -void nvram_write_byte(unsigned char val, int addr) > > > +static void ppc_nvram_write_byte(unsigned char val, int addr) > > > { > > > if (ppc_md.nvram_write_val) > > > ppc_md.nvram_write_val(addr, val); > > > } > > > -EXPORT_SYMBOL(nvram_write_byte); > > > > > > static ssize_t ppc_nvram_get_size(void) > > > { > > > @@ -182,6 +180,8 @@ static long ppc_nvram_sync(void) > > > } > > > > > > const struct nvram_ops arch_nvram_ops = { > > > + .read_byte = ppc_nvram_read_byte, > > > + .write_byte = ppc_nvram_write_byte, > > > .get_size = ppc_nvram_get_size, > > > .sync = ppc_nvram_sync, > > > }; > > > diff --git a/drivers/char/generic_nvram.c b/drivers/char/generic_nvram.c > > > index f32d5663de95..41b76bf9614e 100644 > > > --- a/drivers/char/generic_nvram.c > > > +++ b/drivers/char/generic_nvram.c > > > @@ -48,7 +48,7 @@ static ssize_t read_nvram(struct file *file, char __user > > > *buf, > > > if (*ppos >= nvram_len) > > > return 0; > > > for (i = *ppos; count > 0 && i < nvram_len; ++i, ++p, --count) > > > - if (__put_user(nvram_read_byte(i), p)) > > > + if (__put_user(arch_nvram_ops.read_byte(i), p)) > > > > Instead of modifying all drivers (in this patch and previous ones related to > > other arches), wouldn't it be better to add helpers like the following in > > nvram.h: > > > > Static inline unsigned char nvram_read_byte(int addr) > > { > > return arch_nvram_ops.read_byte(addr); > > } > > > > Is there some benefit, or is that just personal taste? > > Avoiding changes to call sites avoids code review, but I think 1) the > thinkpad_acpi changes have already been reviewed and 2) the fbdev changes > need review anyway. > > Your suggesion would add several new entities and one extra layer of > indirection. > Contrary to what I said above, this kind of double indirection could be useful if it allows us to avoid the kind of double indirection which Arnd objected to (which arises when an arch_nvram_ops method invokes a ppc_md method). For example, static inline unsigned char nvram_read_byte(int addr) { #ifdef CONFIG_PPC return ppc_md.nvram_read_byte(addr); #else return arch_nvram_ops.read_byte(addr); #endif } I'll try this approach for v9 if there are no objections. It may be the least invasive approach. Also, arch_nvram_ops can remain const. --