From: Michael Ellerman <mpe@ellerman.id.au>
To: "Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Nicholas Piggin <npiggin@gmail.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Mark Brown <broonie@kernel.org>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Increasing build coverage for drivers/spi/spi-ppc4xx.c
Date: Wed, 28 Feb 2024 16:37:22 +1100 [thread overview]
Message-ID: <87cysh1759.fsf@mail.lhotse> (raw)
In-Reply-To: <a9d99374-a118-4f7d-9e31-8cb7db657212@csgroup.eu>
Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> Le 27/02/2024 à 15:00, Uwe Kleine-König a écrit :
>> On Tue, Feb 27, 2024 at 01:52:07PM +0000, Christophe Leroy wrote:
>>> Le 27/02/2024 à 11:58, Uwe Kleine-König a écrit :
>>>> On Tue, Feb 27, 2024 at 10:25:15AM +0000, Christophe Leroy wrote:
>>>>> Le 27/02/2024 à 09:46, Uwe Kleine-König a écrit :
>>>>>> recently the spi-ppc4xx.c driver suffered from build errors and warnings
>>>>>> that were undetected for longer than I expected. I think it would be
>>>>>> very beneficial if this driver was enabled in (at least) a powerpc
>>>>>> allmodconfig build.
>>>>>>
>>>>>> The challenge to do so is that spi-ppc4xx.c uses dcri_clrset() which is
>>>>>> only defined for 4xx (as these select PPC_DCR_NATIVE).
...
>>
>> The reason I'd like to see it in allmodconfig is that testing
>> allmodconfig on several archs is the check I do for my patch series.
>
> I think for powerpc you should really check ppc32_allmodconfig in
> addition to allmodconfig
Yeah.
arch/powerpc is really ~7 separate sub architectures.
Building allmodconfig and ppc32_allmodconfig at least covers the bulk of
the code. But it doesn't include 4xx, or several other platforms.
I think the best/easiest option is just to enable this driver in the 44x
defconfig. At least that way the auto builders should catch any problems.
eg.
diff --git a/arch/powerpc/configs/ppc44x_defconfig b/arch/powerpc/configs/ppc44x_defconfig
index 8b595f67068c..95a1e7efb79f 100644
--- a/arch/powerpc/configs/ppc44x_defconfig
+++ b/arch/powerpc/configs/ppc44x_defconfig
@@ -67,6 +67,8 @@ CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_GPIO=m
CONFIG_I2C_IBM_IIC=m
+CONFIG_SPI=y
+CONFIG_SPI_PPC4xx=y
# CONFIG_HWMON is not set
CONFIG_FB=m
CONFIG_USB=m
cheers
prev parent reply other threads:[~2024-02-28 5:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 8:46 Increasing build coverage for drivers/spi/spi-ppc4xx.c Uwe Kleine-König
2024-02-27 8:54 ` Tudor Ambarus
2024-02-27 9:05 ` Uwe Kleine-König
2024-02-27 10:25 ` Christophe Leroy
2024-02-27 10:58 ` Uwe Kleine-König
2024-02-27 13:52 ` Christophe Leroy
2024-02-27 14:00 ` Uwe Kleine-König
2024-02-27 14:38 ` Christophe Leroy
2024-02-28 5:37 ` Michael Ellerman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cysh1759.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@kernel.org \
--cc=broonie@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-spi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).