Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp8787758imu; Sat, 29 Dec 2018 03:51:42 -0800 (PST) X-Google-Smtp-Source: ALg8bN5BxHBxDuJL8xvDDQL7GBZi4mN5JuurTDWN3jVhfHiOBuPaikp6LXvGfRIhQqPWtK3ba9ld X-Received: by 2002:a63:4f5e:: with SMTP id p30mr1384623pgl.71.1546084301955; Sat, 29 Dec 2018 03:51:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546084301; cv=none; d=google.com; s=arc-20160816; b=bVzGHMP9up/M7DD52j2UTO/FZ8Vkq+95GZXeIwP9w6cLrKp9gtWnXiHKTJmzbnyARj nPrnJZT8cVNnbO268FpDKquFBIv4DCtT73AhwQOBYLMKQxyzcZz4xmj32DUJ2hmuQ7wA +TUonOG9qQIU+PYIqZ4olgSPmQfmG9EpFzyLNM4vWDDYQHD/uacnN45HbvFYMYQYCu0Y d7Of2aUNa1Rs444e8AASXTEPmX92rUJXE68avUELZRCK8QozqBqtk7f95npUUBUz8vFn /Uh6QxeRiZqBSERLbOIIPyx/TJY+p3Cx6x25u48XjFDHGfl8QRBYwBpPlM6M+fd8uObR wV3w== 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=we2BIHjwrTtltFQsugSRec5DicWw06wulPTypL1sUg0=; b=fapR20d09wV9/7tuqbgWU490gjjvxCpXxyo0NkauSK9f2a6W2cbyyE9j9HW0f1gtxx RkWIMvSXH+lnVyLg3W1Qng5EKii1l/zMb1IToQ/+mfOPvzBKzVrukibiSkCr6DJF+6hz qHuOoX3XofpIbuqLrJAHXv2c2b4yAqJEdfpSauilBVBj+NHsiNcs1XTBsWUohetWfoJe HHKXTtRa8ubaP2eHrzE47YLMIbwO6m1FNx9TVXFgCaoIVTHO/I5J3pbxJg0KuHbPzeaJ cV+7d3oOjKSF2Ffy5zGb8nvlYJBlHElHcUZH7b1jiRn929drfrn4YxCJ68g+VMcQWEQz IntQ== 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 i9si22545595plb.35.2018.12.29.03.51.27; Sat, 29 Dec 2018 03:51:41 -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 S1728005AbeL2BFs (ORCPT + 99 others); Fri, 28 Dec 2018 20:05:48 -0500 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:60458 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727980AbeL2BFs (ORCPT ); Fri, 28 Dec 2018 20:05:48 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by kvm5.telegraphics.com.au (Postfix) with ESMTP id AAC7022BF5; Fri, 28 Dec 2018 20:05:40 -0500 (EST) Date: Sat, 29 Dec 2018 12:06:03 +1100 (AEDT) From: Finn Thain To: LEROY Christophe cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-m68k@lists.linux-m68k.org, Michael Schmitz , "Martin K. Petersen" , "James E.J. Bottomley" , Greg Kroah-Hartman , Arnd Bergmann Subject: Re: [PATCH v8 01/25] scsi/atari_scsi: Don't select CONFIG_NVRAM In-Reply-To: <20181228173846.Horde.z_zDEJN0rVd8tkt3HjYzmg2@messagerie.si.c-s.fr> Message-ID: References: <20181228173846.Horde.z_zDEJN0rVd8tkt3HjYzmg2@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 Fri, 28 Dec 2018, LEROY Christophe wrote: > Finn Thain a ?crit?: > > > On powerpc, setting CONFIG_NVRAM=n builds a kernel with no NVRAM support. > > Setting CONFIG_NVRAM=m enables the /dev/nvram misc device module without > > enabling NVRAM support in drivers. Setting CONFIG_NVRAM=y enables the > > misc device (built-in) and also enables NVRAM support in drivers. > > > > m68k shares the valkyriefb driver with powerpc, and since that driver uses > > NVRAM, it is affected by CONFIG_ATARI_SCSI, because of the use of > > "select NVRAM". > > > > Adopt the powerpc convention on m68k to avoid surprises. > > > > Signed-off-by: Finn Thain > > Tested-by: Christian T. Steigies > > --- > > This patch temporarily disables CONFIG_NVRAM on Atari, to prevent build > > failures when bisecting the rest of this patch series. It gets enabled > > again with the introduction of CONFIG_HAVE_ARCH_NVRAM_OPS, once the > > nvram_* global functions have been moved to an ops struct. > > --- > > drivers/char/Kconfig | 5 +---- > > drivers/scsi/Kconfig | 6 +++--- > > drivers/scsi/atari_scsi.c | 7 ++++--- > > 3 files changed, 8 insertions(+), 10 deletions(-) > > > > diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig > > index 9d03b2ff5df6..5b54595dfe30 100644 > > --- a/drivers/char/Kconfig > > +++ b/drivers/char/Kconfig > > @@ -236,7 +236,7 @@ source "drivers/char/hw_random/Kconfig" > > > > config NVRAM > > tristate "/dev/nvram support" > > - depends on ATARI || X86 || GENERIC_NVRAM > > + depends on X86 || GENERIC_NVRAM > > ---help--- > > If you say Y here and create a character special file /dev/nvram > > with major number 10 and minor number 144 using mknod ("man mknod"), > > @@ -254,9 +254,6 @@ config NVRAM > > should NEVER idly tamper with it. See Ralf Brown's interrupt list > > for a guide to the use of CMOS bytes by your BIOS. > > > > - On Atari machines, /dev/nvram is always configured and does not need > > - to be selected. > > - > > To compile this driver as a module, choose M here: the > > module will be called nvram. > > > > diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig > > index 640cd1b31a18..924eb69e7fc4 100644 > > --- a/drivers/scsi/Kconfig > > +++ b/drivers/scsi/Kconfig > > @@ -1381,14 +1381,14 @@ config ATARI_SCSI > > tristate "Atari native SCSI support" > > depends on ATARI && SCSI > > select SCSI_SPI_ATTRS > > - select NVRAM > > ---help--- > > If you have an Atari with built-in NCR5380 SCSI controller (TT, > > Falcon, ...) say Y to get it supported. Of course also, if you have > > a compatible SCSI controller (e.g. for Medusa). > > > > - To compile this driver as a module, choose M here: the > > - module will be called atari_scsi. > > + To compile this driver as a module, choose M here: the module will > > + be called atari_scsi. If you also enable NVRAM support, the SCSI > > + host's ID is taken from the setting in TT RTC NVRAM. > > > > This driver supports both styles of NCR integration into the > > system: the TT style (separate DMA), and the Falcon style (via > > diff --git a/drivers/scsi/atari_scsi.c b/drivers/scsi/atari_scsi.c > > index 89f5154c40b6..99e5729d910d 100644 > > --- a/drivers/scsi/atari_scsi.c > > +++ b/drivers/scsi/atari_scsi.c > > @@ -755,9 +755,10 @@ static int __init atari_scsi_probe(struct > > platform_device *pdev) > > if (ATARIHW_PRESENT(TT_SCSI) && setup_sg_tablesize >= 0) > > atari_scsi_template.sg_tablesize = setup_sg_tablesize; > > > > - if (setup_hostid >= 0) { > > + if (setup_hostid >= 0) > > atari_scsi_template.this_id = setup_hostid & 7; > > - } else { > > +#ifdef CONFIG_NVRAM > > + else > > Such ifdefs should be avoided in C files. > It would be better to use > > } else if (IS_ENABLED(CONFIG_NVRAM)) { > I don't like #ifdefs either. However, as the maintainer of this file, I am okay with this one. The old #ifdef CONFIG_NVRAM conditional compilation convention that gets used here and under drivers/video/fbdev could probably be improved upon but I consider this to be out-of-scope for this series, which is complicated enough. And as explained in the commit log, CONFIG_NVRAM=y and CONFIG_NVRAM=m are treaded differently by drivers. Therefore, IS_ENABLED would be incorrect. -- > > /* Test if a host id is set in the NVRam */ > > if (ATARIHW_PRESENT(TT_CLK) && nvram_check_checksum()) { > > unsigned char b = nvram_read_byte(16); > > @@ -768,7 +769,7 @@ static int __init atari_scsi_probe(struct > > platform_device *pdev) > > if (b & 0x80) > > atari_scsi_template.this_id = b & 7; > > } > > - } > > +#endif > > > > /* If running on a Falcon and if there's TT-Ram (i.e., more than one > > * memory block, since there's always ST-Ram in a Falcon), then > > -- > > 2.19.2 > > >