Message ID | ac8d6190-06ae-b538-1293-07efedbfe94e@gmail.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:c923:0:b0:3e4:2afc:c1 with SMTP id j3csp1552121vqt; Mon, 17 Jul 2023 23:59:53 -0700 (PDT) X-Google-Smtp-Source: APBJJlH4mUqBvv5yyBlqH4+ZoR6XDkS+GOiTBMAoC9ndB1DYbDwmQkLGJXpURWUvjnUClCx418Kf X-Received: by 2002:a17:902:db04:b0:1b5:1467:c4e8 with SMTP id m4-20020a170902db0400b001b51467c4e8mr1779140plx.15.1689663593388; Mon, 17 Jul 2023 23:59:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689663593; cv=none; d=google.com; s=arc-20160816; b=YtVpM2NP1zkZmPHapIC3hCZ7HHvQUNHGpHoK7CKMegNXeZUha0oQc09h6XHFHv6k45 yxADbETT+UFs7ijc5T3ICQy5AjncdipciH9wJgiXr44RWxbALQow0mEKgwzDnHh0NsAm RS+6KFdkM70K4Y8A+pynS9MgasvME32xiRs16xk6bnLQUBH+SL25iSNdHdUqa0GnV1wJ ekobFTomYYtwfAltZWfcd8ND+WD2toCpkjlx49NafqAJrxgLTv7JF4UWZO7J+xtNJ4qx p+qPEGWdnq89f7iiz9qPrfF3aRbkJJ1RqmXVCZpKrWRSoWJWJsWi84h/9Kj2InphcbRY oc1w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:subject:from:cc:to :content-language:user-agent:mime-version:date:message-id :dkim-signature; bh=ss351zSIYWfQhu+bNWxKLoSYfDEjnuyNfe4mYrOgQz8=; fh=jnDt7IPt5MJ0jWIX4X2VqCybkLX/cq2pLcwQt0YPWnU=; b=Ww9ZF8q2rmLqNldQEbPV2Ag+yfEFT3HqBryfZfZDD6V34jeoFSWmpPdYKoKnMVy9cN Ho73PJ3nJdspA1+Zz+MbWcL37/77HGsci4eYlqYXbZDFMvrPSiranuiTXRy6NmRmfYRN T6w2Grvxo7igH2W1PSzhut90z7x5RSwijedELWP9+s/fZ7lNLHgVemIq6NqD+es9ioGc NhLS3STHdY01seynLEobbwb92p8LM2vqyxwLU8cG+Eb7Kg3nhcLiJoiYktJZZHRNKmWo K/EmVSkcOw4rMNqndSdWgeP7Go4u+2lY8V667mxnbvTicwZOeIOTuim6f0Yc9D8URn4C GLpA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=ESd7x52k; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id lm16-20020a170903299000b001bb2093efb6si1199490plb.45.2023.07.17.23.59.40; Mon, 17 Jul 2023 23:59:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=ESd7x52k; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S230286AbjGRGlL (ORCPT <rfc822;daweilics@gmail.com> + 99 others); Tue, 18 Jul 2023 02:41:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46006 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229480AbjGRGlK (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 18 Jul 2023 02:41:10 -0400 Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F2098B2; Mon, 17 Jul 2023 23:41:07 -0700 (PDT) Received: by mail-pl1-x62c.google.com with SMTP id d9443c01a7336-1b9cd6a0051so32859085ad.1; Mon, 17 Jul 2023 23:41:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689662467; x=1692254467; h=content-transfer-encoding:subject:from:cc:to:content-language :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=ss351zSIYWfQhu+bNWxKLoSYfDEjnuyNfe4mYrOgQz8=; b=ESd7x52kPKUq9jbEJD7WQPWYjN/lysuEr1+dHZ1irC8juSQbRBQPfOkZdqVrHvrf8b t+Sn21wECswvesNAfG73UVV2kWn+Qg9q/fd2EzEmC//N6An54GE/LheNo3hUHe4nuYNz D/zzR+np2XE0MG5r/xc1OQ/Aors4QXRUb7+oK/LDWXah5dO3huc/VdTKSPn7/aqEEf9v EpFZKJn0FoB8vctr3H4DAvOdEfutbkU4f8xBt2Nd9QZ+NE/smQiXntRyytuVaLVZIuGc n2PL+YtyQ2KXo4whhWl7zDY0BPIqzuYMpXkNuLX2LtOJV+zbbTPN1Q8FzE/6ZYbd5RHa XYXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689662467; x=1692254467; h=content-transfer-encoding:subject:from:cc:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=ss351zSIYWfQhu+bNWxKLoSYfDEjnuyNfe4mYrOgQz8=; b=IWKas61rX6MyPqTd8HsoXbRcTfhILafRkF7XXakqJN0xV4csfI6HTozIzWYxdIYNZ5 qafvHpYLGBnaNQj7LRmcvUWAWC4SOmJTLorM7mEbS5tE0OjLHQE03dYWKEbY4fxBAU5f DN2vnl8vgw/z+Hb09dUz5TrW2Hx4Y3rR9vMSa0z7CJnrJ29TkU5e2A9xUHGp5MjQooSd EiVchuYpoz2g1m5U+xSxy0DMHyNVIUXz6ImrFN8OMe9s+A+R4t9zhzPCGrqlMUll5XIf cFXAnIAyC4sgGJpTQ1rHSWJ0Qg/zHW5jsk5SHrNDvjg0m0Q4pabDSeWAOi4heuHo+coE aAlA== X-Gm-Message-State: ABy/qLZ8YRGx3U76C79ivwtac7T/HbOonDBBzbQy1EKjrIl063islqid guyFlm5o3t3wcAPSteHVNwdD2WClGMC6yw== X-Received: by 2002:a17:902:d2d2:b0:1bb:2d0b:1a19 with SMTP id n18-20020a170902d2d200b001bb2d0b1a19mr1391506plc.62.1689662467236; Mon, 17 Jul 2023 23:41:07 -0700 (PDT) Received: from ?IPV6:2601:1c2:980:9ec0::2764? ([2601:1c2:980:9ec0::2764]) by smtp.gmail.com with ESMTPSA id p12-20020a170902eacc00b001b89466a5f4sm993434pld.105.2023.07.17.23.41.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 17 Jul 2023 23:41:06 -0700 (PDT) Message-ID: <ac8d6190-06ae-b538-1293-07efedbfe94e@gmail.com> Date: Mon, 17 Jul 2023 23:41:06 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Content-Language: en-US To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, linux-pwm@vger.kernel.org Cc: Biju Das <biju.das.jz@bp.renesas.com>, Thierry Reding <thierry.reding@gmail.com>, =?utf-8?q?Uwe_Kleine-K=C3=B6nig?= <u.kleine-koenig@pengutronix.de> From: Randy Dunlap <rd.dunlab@gmail.com> Subject: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1771740691902368885 X-GMAIL-MSGID: 1771740691902368885 |
Series |
[v2] pwm: fix pwm-rz-mtu3.c build errors
|
|
Commit Message
Randy Dunlap
July 18, 2023, 6:41 a.m. UTC
From: Randy Dunlap <rd.dunlab@gmail.com> When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build errors: ld: vmlinux.o: in function `rz_mtu3_pwm_config': drivers/pwm/pwm-rz-mtu3.c:374: undefined reference to `rz_mtu3_disable' ld: drivers/pwm/pwm-rz-mtu3.c:377: undefined reference to `rz_mtu3_8bit_ch_write' ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' ld: vmlinux.o: in function `rz_mtu3_pwm_config': drivers/pwm/pwm-rz-mtu3.c:382: undefined reference to `rz_mtu3_8bit_ch_write' ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' ld: drivers/pwm/pwm-rz-mtu3.c:111: undefined reference to `rz_mtu3_16bit_ch_write' ld: vmlinux.o: in function `rz_mtu3_pwm_config': drivers/pwm/pwm-rz-mtu3.c:397: undefined reference to `rz_mtu3_enable' ld: vmlinux.o: in function `rz_mtu3_pwm_disable': drivers/pwm/pwm-rz-mtu3.c:259: undefined reference to `rz_mtu3_8bit_ch_write' ld: drivers/pwm/pwm-rz-mtu3.c:264: undefined reference to `rz_mtu3_disable' ld: vmlinux.o: in function `rz_mtu3_pwm_enable': drivers/pwm/pwm-rz-mtu3.c:230: undefined reference to `rz_mtu3_8bit_ch_write' ld: drivers/pwm/pwm-rz-mtu3.c:234: undefined reference to `rz_mtu3_8bit_ch_write' ld: drivers/pwm/pwm-rz-mtu3.c:238: undefined reference to `rz_mtu3_enable' ld: vmlinux.o: in function `rz_mtu3_pwm_is_ch_enabled': drivers/pwm/pwm-rz-mtu3.c:155: undefined reference to `rz_mtu3_is_enabled' ld: drivers/pwm/pwm-rz-mtu3.c:162: undefined reference to `rz_mtu3_8bit_ch_read' ld: vmlinux.o: in function `rz_mtu3_pwm_read_tgr_registers': drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' ld: drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' ld: drivers/pwm/pwm-rz-mtu3.c:103: undefined reference to `rz_mtu3_16bit_ch_read' ld: vmlinux.o: in function `rz_mtu3_pwm_get_state': drivers/pwm/pwm-rz-mtu3.c:296: undefined reference to `rz_mtu3_8bit_ch_read' Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is still allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built but also allow the latter not to be built. Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver") Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com Cc: Biju Das <biju.das.jz@bp.renesas.com> Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Cc: Thierry Reding <thierry.reding@gmail.com> Cc: linux-pwm@vger.kernel.org --- v2: fix typo in Subject; correct my email address while infradead.org is down; drivers/pwm/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Comments
On Mon, Jul 17, 2023 at 11:41:06PM -0700, Randy Dunlap wrote: > From: Randy Dunlap <rd.dunlab@gmail.com> > > When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build errors: > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:374: undefined reference to `rz_mtu3_disable' > ld: drivers/pwm/pwm-rz-mtu3.c:377: undefined reference to `rz_mtu3_8bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:382: undefined reference to `rz_mtu3_8bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:111: undefined reference to `rz_mtu3_16bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:397: undefined reference to `rz_mtu3_enable' > ld: vmlinux.o: in function `rz_mtu3_pwm_disable': > drivers/pwm/pwm-rz-mtu3.c:259: undefined reference to `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:264: undefined reference to `rz_mtu3_disable' > ld: vmlinux.o: in function `rz_mtu3_pwm_enable': > drivers/pwm/pwm-rz-mtu3.c:230: undefined reference to `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:234: undefined reference to `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:238: undefined reference to `rz_mtu3_enable' > ld: vmlinux.o: in function `rz_mtu3_pwm_is_ch_enabled': > drivers/pwm/pwm-rz-mtu3.c:155: undefined reference to `rz_mtu3_is_enabled' > ld: drivers/pwm/pwm-rz-mtu3.c:162: undefined reference to `rz_mtu3_8bit_ch_read' > ld: vmlinux.o: in function `rz_mtu3_pwm_read_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' > ld: drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' > ld: drivers/pwm/pwm-rz-mtu3.c:103: undefined reference to `rz_mtu3_16bit_ch_read' > ld: vmlinux.o: in function `rz_mtu3_pwm_get_state': > drivers/pwm/pwm-rz-mtu3.c:296: undefined reference to `rz_mtu3_8bit_ch_read' > > Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is > still allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built > but also allow the latter not to be built. > > Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver") > Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com > Cc: Biju Das <biju.das.jz@bp.renesas.com> > Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> > Cc: Thierry Reding <thierry.reding@gmail.com> > Cc: linux-pwm@vger.kernel.org I missed this v2 while I still looked at (implicit) v1. The things I said there still apply for v2. I don't repeat my writings, but here is a link to the archive with what I wrote: https://lore.kernel.org/linux-pwm/20230718090023.wo6m6ffzaifgctkj@pengutronix.de/ Best regards Uwe
Hi Randy, > -----Original Message----- > From: Randy Dunlap <rd.dunlab@gmail.com> > Sent: Tuesday, July 18, 2023 7:41 AM > To: linux-kernel@vger.kernel.org; linux-pwm@vger.kernel.org > Cc: Biju Das <biju.das.jz@bp.renesas.com>; Thierry Reding > <thierry.reding@gmail.com>; Uwe Kleine-König <u.kleine- > koenig@pengutronix.de> > Subject: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors > > From: Randy Dunlap <rd.dunlab@gmail.com> > > When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build errors: > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:374: undefined reference to `rz_mtu3_disable' > ld: drivers/pwm/pwm-rz-mtu3.c:377: undefined reference to > `rz_mtu3_8bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to > `rz_mtu3_16bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:382: undefined reference to > `rz_mtu3_8bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to > `rz_mtu3_16bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:111: undefined reference to > `rz_mtu3_16bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:397: undefined reference to `rz_mtu3_enable' > ld: vmlinux.o: in function `rz_mtu3_pwm_disable': > drivers/pwm/pwm-rz-mtu3.c:259: undefined reference to > `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:264: undefined reference to > `rz_mtu3_disable' > ld: vmlinux.o: in function `rz_mtu3_pwm_enable': > drivers/pwm/pwm-rz-mtu3.c:230: undefined reference to > `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:234: undefined reference to > `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:238: undefined reference to `rz_mtu3_enable' > ld: vmlinux.o: in function `rz_mtu3_pwm_is_ch_enabled': > drivers/pwm/pwm-rz-mtu3.c:155: undefined reference to `rz_mtu3_is_enabled' > ld: drivers/pwm/pwm-rz-mtu3.c:162: undefined reference to > `rz_mtu3_8bit_ch_read' > ld: vmlinux.o: in function `rz_mtu3_pwm_read_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to > `rz_mtu3_16bit_ch_read' > ld: drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to > `rz_mtu3_16bit_ch_read' > ld: drivers/pwm/pwm-rz-mtu3.c:103: undefined reference to > `rz_mtu3_16bit_ch_read' > ld: vmlinux.o: in function `rz_mtu3_pwm_get_state': > drivers/pwm/pwm-rz-mtu3.c:296: undefined reference to > `rz_mtu3_8bit_ch_read' > > Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is still > allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built but also > allow the latter not to be built. > > Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver") > Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com > Cc: Biju Das <biju.das.jz@bp.renesas.com> > Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> > Cc: Thierry Reding <thierry.reding@gmail.com> > Cc: linux-pwm@vger.kernel.org > --- > v2: fix typo in Subject; > correct my email address while infradead.org is down; > > drivers/pwm/Kconfig | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff -- a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig > --- a/drivers/pwm/Kconfig > +++ b/drivers/pwm/Kconfig > @@ -505,7 +505,8 @@ config PWM_ROCKCHIP > > config PWM_RZ_MTU3 > tristate "Renesas RZ/G2L MTU3a PWM Timer support" > - depends on RZ_MTU3 || COMPILE_TEST > + depends on COMPILE_TEST > + depends on RZ_MTU3 || RZ_MTU3=n > depends on HAS_IOMEM > help > This driver exposes the MTU3a PWM Timer controller found in The below patch also works fine, diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig index 1c8dbb064ee5..56ab2f4b91fe 100644 --- a/drivers/pwm/Kconfig +++ b/drivers/pwm/Kconfig @@ -505,7 +505,7 @@ config PWM_ROCKCHIP config PWM_RZ_MTU3 tristate "Renesas RZ/G2L MTU3a PWM Timer support" - depends on RZ_MTU3 || COMPILE_TEST + depends on RZ_MTU3 || (COMPILE_TEST && RZ_MTU3) depends on HAS_IOMEM help This driver exposes the MTU3a PWM Timer controller found in Renesas So shall I send this fix instead. Cheers, Biju
On Tue, Jul 18, 2023 at 11:26:28AM +0000, Biju Das wrote: > Hi Randy, > > > -----Original Message----- > > From: Randy Dunlap <rd.dunlab@gmail.com> > > Sent: Tuesday, July 18, 2023 7:41 AM > > To: linux-kernel@vger.kernel.org; linux-pwm@vger.kernel.org > > Cc: Biju Das <biju.das.jz@bp.renesas.com>; Thierry Reding > > <thierry.reding@gmail.com>; Uwe Kleine-König <u.kleine- > > koenig@pengutronix.de> > > Subject: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors > > > > From: Randy Dunlap <rd.dunlab@gmail.com> > > > > When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build errors: > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > drivers/pwm/pwm-rz-mtu3.c:374: undefined reference to `rz_mtu3_disable' > > ld: drivers/pwm/pwm-rz-mtu3.c:377: undefined reference to > > `rz_mtu3_8bit_ch_write' > > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to > > `rz_mtu3_16bit_ch_write' > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > drivers/pwm/pwm-rz-mtu3.c:382: undefined reference to > > `rz_mtu3_8bit_ch_write' > > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to > > `rz_mtu3_16bit_ch_write' > > ld: drivers/pwm/pwm-rz-mtu3.c:111: undefined reference to > > `rz_mtu3_16bit_ch_write' > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > drivers/pwm/pwm-rz-mtu3.c:397: undefined reference to `rz_mtu3_enable' > > ld: vmlinux.o: in function `rz_mtu3_pwm_disable': > > drivers/pwm/pwm-rz-mtu3.c:259: undefined reference to > > `rz_mtu3_8bit_ch_write' > > ld: drivers/pwm/pwm-rz-mtu3.c:264: undefined reference to > > `rz_mtu3_disable' > > ld: vmlinux.o: in function `rz_mtu3_pwm_enable': > > drivers/pwm/pwm-rz-mtu3.c:230: undefined reference to > > `rz_mtu3_8bit_ch_write' > > ld: drivers/pwm/pwm-rz-mtu3.c:234: undefined reference to > > `rz_mtu3_8bit_ch_write' > > ld: drivers/pwm/pwm-rz-mtu3.c:238: undefined reference to `rz_mtu3_enable' > > ld: vmlinux.o: in function `rz_mtu3_pwm_is_ch_enabled': > > drivers/pwm/pwm-rz-mtu3.c:155: undefined reference to `rz_mtu3_is_enabled' > > ld: drivers/pwm/pwm-rz-mtu3.c:162: undefined reference to > > `rz_mtu3_8bit_ch_read' > > ld: vmlinux.o: in function `rz_mtu3_pwm_read_tgr_registers': > > drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to > > `rz_mtu3_16bit_ch_read' > > ld: drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to > > `rz_mtu3_16bit_ch_read' > > ld: drivers/pwm/pwm-rz-mtu3.c:103: undefined reference to > > `rz_mtu3_16bit_ch_read' > > ld: vmlinux.o: in function `rz_mtu3_pwm_get_state': > > drivers/pwm/pwm-rz-mtu3.c:296: undefined reference to > > `rz_mtu3_8bit_ch_read' > > > > Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is still > > allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built but also > > allow the latter not to be built. > > > > Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver") > > Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com > > Cc: Biju Das <biju.das.jz@bp.renesas.com> > > Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> > > Cc: Thierry Reding <thierry.reding@gmail.com> > > Cc: linux-pwm@vger.kernel.org > > --- > > v2: fix typo in Subject; > > correct my email address while infradead.org is down; > > > > drivers/pwm/Kconfig | 3 ++- > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > diff -- a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig > > --- a/drivers/pwm/Kconfig > > +++ b/drivers/pwm/Kconfig > > @@ -505,7 +505,8 @@ config PWM_ROCKCHIP > > > > config PWM_RZ_MTU3 > > tristate "Renesas RZ/G2L MTU3a PWM Timer support" > > - depends on RZ_MTU3 || COMPILE_TEST > > + depends on COMPILE_TEST > > + depends on RZ_MTU3 || RZ_MTU3=n > > depends on HAS_IOMEM > > help > > This driver exposes the MTU3a PWM Timer controller found in > > > The below patch also works fine, > > diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig > index 1c8dbb064ee5..56ab2f4b91fe 100644 > --- a/drivers/pwm/Kconfig > +++ b/drivers/pwm/Kconfig > @@ -505,7 +505,7 @@ config PWM_ROCKCHIP > > config PWM_RZ_MTU3 > tristate "Renesas RZ/G2L MTU3a PWM Timer support" > - depends on RZ_MTU3 || COMPILE_TEST > + depends on RZ_MTU3 || (COMPILE_TEST && RZ_MTU3) That's a bit pointless, isn't it? That effectively reduces to just: depends on RZ_MTU3 Thierry
Hi Randy, On Tue, Jul 18, 2023 at 8:44 AM Randy Dunlap <rd.dunlab@gmail.com> wrote: > From: Randy Dunlap <rd.dunlab@gmail.com> > > When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build errors: > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:374: undefined reference to `rz_mtu3_disable' > ld: drivers/pwm/pwm-rz-mtu3.c:377: undefined reference to `rz_mtu3_8bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:382: undefined reference to `rz_mtu3_8bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:111: undefined reference to `rz_mtu3_16bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:397: undefined reference to `rz_mtu3_enable' > ld: vmlinux.o: in function `rz_mtu3_pwm_disable': > drivers/pwm/pwm-rz-mtu3.c:259: undefined reference to `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:264: undefined reference to `rz_mtu3_disable' > ld: vmlinux.o: in function `rz_mtu3_pwm_enable': > drivers/pwm/pwm-rz-mtu3.c:230: undefined reference to `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:234: undefined reference to `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:238: undefined reference to `rz_mtu3_enable' > ld: vmlinux.o: in function `rz_mtu3_pwm_is_ch_enabled': > drivers/pwm/pwm-rz-mtu3.c:155: undefined reference to `rz_mtu3_is_enabled' > ld: drivers/pwm/pwm-rz-mtu3.c:162: undefined reference to `rz_mtu3_8bit_ch_read' > ld: vmlinux.o: in function `rz_mtu3_pwm_read_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' > ld: drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' > ld: drivers/pwm/pwm-rz-mtu3.c:103: undefined reference to `rz_mtu3_16bit_ch_read' > ld: vmlinux.o: in function `rz_mtu3_pwm_get_state': > drivers/pwm/pwm-rz-mtu3.c:296: undefined reference to `rz_mtu3_8bit_ch_read' > > Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is > still allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built > but also allow the latter not to be built. > > Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver") > Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com Thanks for your patch! > --- a/drivers/pwm/Kconfig > +++ b/drivers/pwm/Kconfig > @@ -505,7 +505,8 @@ config PWM_ROCKCHIP > > config PWM_RZ_MTU3 > tristate "Renesas RZ/G2L MTU3a PWM Timer support" > - depends on RZ_MTU3 || COMPILE_TEST > + depends on COMPILE_TEST This makes the driver always depend on COMPILE_TEST, which is definitely not what we want. > + depends on RZ_MTU3 || RZ_MTU3=n > depends on HAS_IOMEM > help > This driver exposes the MTU3a PWM Timer controller found in Renesas Gr{oetje,eeting}s, Geert
Hi Thierry, Thanks for the feedback. > -----Original Message----- > From: Thierry Reding <thierry.reding@gmail.com> > Sent: Tuesday, July 18, 2023 12:44 PM > To: Biju Das <biju.das.jz@bp.renesas.com> > Cc: Randy Dunlap <rd.dunlab@gmail.com>; linux-kernel@vger.kernel.org; > linux-pwm@vger.kernel.org; Uwe Kleine-König <u.kleine- > koenig@pengutronix.de>; Fabrizio Castro > <fabrizio.castro.jz@renesas.com>; lee.jones@linaro.org; Geert > Uytterhoeven <geert+renesas@glider.be> > Subject: Re: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors > > On Tue, Jul 18, 2023 at 11:26:28AM +0000, Biju Das wrote: > > Hi Randy, > > > > > -----Original Message----- > > > From: Randy Dunlap <rd.dunlab@gmail.com> > > > Sent: Tuesday, July 18, 2023 7:41 AM > > > To: linux-kernel@vger.kernel.org; linux-pwm@vger.kernel.org > > > Cc: Biju Das <biju.das.jz@bp.renesas.com>; Thierry Reding > > > <thierry.reding@gmail.com>; Uwe Kleine-König <u.kleine- > > > koenig@pengutronix.de> > > > Subject: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors > > > > > > From: Randy Dunlap <rd.dunlab@gmail.com> > > > > > > When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build > errors: > > > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > > drivers/pwm/pwm-rz-mtu3.c:374: undefined reference to > `rz_mtu3_disable' > > > ld: drivers/pwm/pwm-rz-mtu3.c:377: undefined reference to > > > `rz_mtu3_8bit_ch_write' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > > > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to > > > `rz_mtu3_16bit_ch_write' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > > drivers/pwm/pwm-rz-mtu3.c:382: undefined reference to > > > `rz_mtu3_8bit_ch_write' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > > > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to > > > `rz_mtu3_16bit_ch_write' > > > ld: drivers/pwm/pwm-rz-mtu3.c:111: undefined reference to > > > `rz_mtu3_16bit_ch_write' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > > drivers/pwm/pwm-rz-mtu3.c:397: undefined reference to > `rz_mtu3_enable' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_disable': > > > drivers/pwm/pwm-rz-mtu3.c:259: undefined reference to > > > `rz_mtu3_8bit_ch_write' > > > ld: drivers/pwm/pwm-rz-mtu3.c:264: undefined reference to > > > `rz_mtu3_disable' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_enable': > > > drivers/pwm/pwm-rz-mtu3.c:230: undefined reference to > > > `rz_mtu3_8bit_ch_write' > > > ld: drivers/pwm/pwm-rz-mtu3.c:234: undefined reference to > > > `rz_mtu3_8bit_ch_write' > > > ld: drivers/pwm/pwm-rz-mtu3.c:238: undefined reference to > `rz_mtu3_enable' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_is_ch_enabled': > > > drivers/pwm/pwm-rz-mtu3.c:155: undefined reference to > `rz_mtu3_is_enabled' > > > ld: drivers/pwm/pwm-rz-mtu3.c:162: undefined reference to > > > `rz_mtu3_8bit_ch_read' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_read_tgr_registers': > > > drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to > > > `rz_mtu3_16bit_ch_read' > > > ld: drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to > > > `rz_mtu3_16bit_ch_read' > > > ld: drivers/pwm/pwm-rz-mtu3.c:103: undefined reference to > > > `rz_mtu3_16bit_ch_read' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_get_state': > > > drivers/pwm/pwm-rz-mtu3.c:296: undefined reference to > > > `rz_mtu3_8bit_ch_read' > > > > > > Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is still > > > allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built but > > > also allow the latter not to be built. > > > > > > Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver") > > > Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com > > > Cc: Biju Das <biju.das.jz@bp.renesas.com> > > > Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> > > > Cc: Thierry Reding <thierry.reding@gmail.com> > > > Cc: linux-pwm@vger.kernel.org > > > --- > > > v2: fix typo in Subject; > > > correct my email address while infradead.org is down; > > > > > > drivers/pwm/Kconfig | 3 ++- > > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > > > diff -- a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig > > > --- a/drivers/pwm/Kconfig > > > +++ b/drivers/pwm/Kconfig > > > @@ -505,7 +505,8 @@ config PWM_ROCKCHIP > > > > > > config PWM_RZ_MTU3 > > > tristate "Renesas RZ/G2L MTU3a PWM Timer support" > > > - depends on RZ_MTU3 || COMPILE_TEST > > > + depends on COMPILE_TEST > > > + depends on RZ_MTU3 || RZ_MTU3=n > > > depends on HAS_IOMEM > > > help > > > This driver exposes the MTU3a PWM Timer controller found in > > > > > > The below patch also works fine, > > > > diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig index > > 1c8dbb064ee5..56ab2f4b91fe 100644 > > --- a/drivers/pwm/Kconfig > > +++ b/drivers/pwm/Kconfig > > @@ -505,7 +505,7 @@ config PWM_ROCKCHIP > > > > config PWM_RZ_MTU3 > > tristate "Renesas RZ/G2L MTU3a PWM Timer support" > > - depends on RZ_MTU3 || COMPILE_TEST > > + depends on RZ_MTU3 || (COMPILE_TEST && RZ_MTU3) > > That's a bit pointless, isn't it? That effectively reduces to just: > > depends on RZ_MTU3 OK, then Uwe's solution is better. ie, use the existing "depends on RZ_MTU3 || COMPILE_TEST" and use -#if IS_ENABLED(CONFIG_RZ_MTU3) +#if IS_REACHABLE(CONFIG_RZ_MTU3) in include/linux/mfd/rz-mtu3.h Cheers, Biju
Hi Randy, > From: Randy Dunlap <rd.dunlab@gmail.com> > Subject: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors > > From: Randy Dunlap <rd.dunlab@gmail.com> > > When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build > errors: > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:374: undefined reference to > `rz_mtu3_disable' > ld: drivers/pwm/pwm-rz-mtu3.c:377: undefined reference to > `rz_mtu3_8bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to > `rz_mtu3_16bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:382: undefined reference to > `rz_mtu3_8bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to > `rz_mtu3_16bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:111: undefined reference to > `rz_mtu3_16bit_ch_write' > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > drivers/pwm/pwm-rz-mtu3.c:397: undefined reference to `rz_mtu3_enable' > ld: vmlinux.o: in function `rz_mtu3_pwm_disable': > drivers/pwm/pwm-rz-mtu3.c:259: undefined reference to > `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:264: undefined reference to > `rz_mtu3_disable' > ld: vmlinux.o: in function `rz_mtu3_pwm_enable': > drivers/pwm/pwm-rz-mtu3.c:230: undefined reference to > `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:234: undefined reference to > `rz_mtu3_8bit_ch_write' > ld: drivers/pwm/pwm-rz-mtu3.c:238: undefined reference to > `rz_mtu3_enable' > ld: vmlinux.o: in function `rz_mtu3_pwm_is_ch_enabled': > drivers/pwm/pwm-rz-mtu3.c:155: undefined reference to > `rz_mtu3_is_enabled' > ld: drivers/pwm/pwm-rz-mtu3.c:162: undefined reference to > `rz_mtu3_8bit_ch_read' > ld: vmlinux.o: in function `rz_mtu3_pwm_read_tgr_registers': > drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to > `rz_mtu3_16bit_ch_read' > ld: drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to > `rz_mtu3_16bit_ch_read' > ld: drivers/pwm/pwm-rz-mtu3.c:103: undefined reference to > `rz_mtu3_16bit_ch_read' > ld: vmlinux.o: in function `rz_mtu3_pwm_get_state': > drivers/pwm/pwm-rz-mtu3.c:296: undefined reference to > `rz_mtu3_8bit_ch_read' > > Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is > still allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built > but also allow the latter not to be built. > > Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver") > Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com > Cc: Biju Das <biju.das.jz@bp.renesas.com> > Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> > Cc: Thierry Reding <thierry.reding@gmail.com> > Cc: linux-pwm@vger.kernel.org > --- > v2: fix typo in Subject; > correct my email address while infradead.org is down; > > drivers/pwm/Kconfig | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff -- a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig > --- a/drivers/pwm/Kconfig > +++ b/drivers/pwm/Kconfig > @@ -505,7 +505,8 @@ config PWM_ROCKCHIP > > config PWM_RZ_MTU3 > tristate "Renesas RZ/G2L MTU3a PWM Timer support" > - depends on RZ_MTU3 || COMPILE_TEST > + depends on COMPILE_TEST > + depends on RZ_MTU3 || RZ_MTU3=n Isn't this a tautology? Cheers, Fab > depends on HAS_IOMEM > help > This driver exposes the MTU3a PWM Timer controller found in > Renesas
On Tue, Jul 18, 2023 at 02:05:42PM +0200, Geert Uytterhoeven wrote: > Hi Randy, > > On Tue, Jul 18, 2023 at 8:44 AM Randy Dunlap <rd.dunlab@gmail.com> wrote: > > From: Randy Dunlap <rd.dunlab@gmail.com> > > > > When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build errors: > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > drivers/pwm/pwm-rz-mtu3.c:374: undefined reference to `rz_mtu3_disable' > > ld: drivers/pwm/pwm-rz-mtu3.c:377: undefined reference to `rz_mtu3_8bit_ch_write' > > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > drivers/pwm/pwm-rz-mtu3.c:382: undefined reference to `rz_mtu3_8bit_ch_write' > > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' > > ld: drivers/pwm/pwm-rz-mtu3.c:111: undefined reference to `rz_mtu3_16bit_ch_write' > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > drivers/pwm/pwm-rz-mtu3.c:397: undefined reference to `rz_mtu3_enable' > > ld: vmlinux.o: in function `rz_mtu3_pwm_disable': > > drivers/pwm/pwm-rz-mtu3.c:259: undefined reference to `rz_mtu3_8bit_ch_write' > > ld: drivers/pwm/pwm-rz-mtu3.c:264: undefined reference to `rz_mtu3_disable' > > ld: vmlinux.o: in function `rz_mtu3_pwm_enable': > > drivers/pwm/pwm-rz-mtu3.c:230: undefined reference to `rz_mtu3_8bit_ch_write' > > ld: drivers/pwm/pwm-rz-mtu3.c:234: undefined reference to `rz_mtu3_8bit_ch_write' > > ld: drivers/pwm/pwm-rz-mtu3.c:238: undefined reference to `rz_mtu3_enable' > > ld: vmlinux.o: in function `rz_mtu3_pwm_is_ch_enabled': > > drivers/pwm/pwm-rz-mtu3.c:155: undefined reference to `rz_mtu3_is_enabled' > > ld: drivers/pwm/pwm-rz-mtu3.c:162: undefined reference to `rz_mtu3_8bit_ch_read' > > ld: vmlinux.o: in function `rz_mtu3_pwm_read_tgr_registers': > > drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' > > ld: drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' > > ld: drivers/pwm/pwm-rz-mtu3.c:103: undefined reference to `rz_mtu3_16bit_ch_read' > > ld: vmlinux.o: in function `rz_mtu3_pwm_get_state': > > drivers/pwm/pwm-rz-mtu3.c:296: undefined reference to `rz_mtu3_8bit_ch_read' > > > > Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is > > still allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built > > but also allow the latter not to be built. > > > > Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver") > > Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com > > Thanks for your patch! > > > --- a/drivers/pwm/Kconfig > > +++ b/drivers/pwm/Kconfig > > @@ -505,7 +505,8 @@ config PWM_ROCKCHIP > > > > config PWM_RZ_MTU3 > > tristate "Renesas RZ/G2L MTU3a PWM Timer support" > > - depends on RZ_MTU3 || COMPILE_TEST > > + depends on COMPILE_TEST > > This makes the driver always depend on COMPILE_TEST, > which is definitely not what we want. Honestly, do we really need all of this complexity? I have specific configurations to test all of the PWM drivers to make sure they build. There's probably edge cases that don't get tested, but sooner or later I expect some build bot will encounter those and then we can rectify things. But in many cases that I've seen COMPILE_TEST just happens to do more harm than good. Thierry
On 7/18/23 05:13, Fabrizio Castro wrote: > Hi Randy, > >> From: Randy Dunlap <rd.dunlab@gmail.com> >> Subject: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors >> >> From: Randy Dunlap <rd.dunlab@gmail.com> >> >> When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build >> errors: >> >> >> Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is >> still allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built >> but also allow the latter not to be built. >> >> drivers/pwm/Kconfig | 3 ++- >> 1 file changed, 2 insertions(+), 1 deletion(-) >> >> diff -- a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig >> --- a/drivers/pwm/Kconfig >> +++ b/drivers/pwm/Kconfig >> @@ -505,7 +505,8 @@ config PWM_ROCKCHIP >> >> config PWM_RZ_MTU3 >> tristate "Renesas RZ/G2L MTU3a PWM Timer support" >> - depends on RZ_MTU3 || COMPILE_TEST >> + depends on COMPILE_TEST >> + depends on RZ_MTU3 || RZ_MTU3=n > > Isn't this a tautology? Not at all. It's used in Kconfig quite a bit. This is tristate logic. It says that if RZ_MTU3 is y/m, PWM_RZ_MTU3 is limited by that. But if RZ_MTU3 is n, PWM_RZ_MTU3 can be y or m. Is that clearer?
Hi Randy, > From: Randy Dunlap <rd.dunlab@gmail.com> > Subject: Re: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors > > On 7/18/23 05:13, Fabrizio Castro wrote: > > Hi Randy, > > > >> From: Randy Dunlap <rd.dunlab@gmail.com> > >> Subject: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors > >> > >> From: Randy Dunlap <rd.dunlab@gmail.com> > >> > >> When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build > >> errors: > >> > >> > >> Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is > >> still allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being > built > >> but also allow the latter not to be built. > >> > >> drivers/pwm/Kconfig | 3 ++- > >> 1 file changed, 2 insertions(+), 1 deletion(-) > >> > >> diff -- a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig > >> --- a/drivers/pwm/Kconfig > >> +++ b/drivers/pwm/Kconfig > >> @@ -505,7 +505,8 @@ config PWM_ROCKCHIP > >> > >> config PWM_RZ_MTU3 > >> tristate "Renesas RZ/G2L MTU3a PWM Timer support" > >> - depends on RZ_MTU3 || COMPILE_TEST > >> + depends on COMPILE_TEST > >> + depends on RZ_MTU3 || RZ_MTU3=n > > > > Isn't this a tautology? > > Not at all. It's used in Kconfig quite a bit. > This is tristate logic. > > It says that if RZ_MTU3 is y/m, PWM_RZ_MTU3 is limited by that. > But if RZ_MTU3 is n, PWM_RZ_MTU3 can be y or m. > > Is that clearer? It is, thanks for the explanation! Cheers, Fab > > -- > ~Randy
On Tue, Jul 18, 2023 at 03:24:58PM +0200, Thierry Reding wrote: > On Tue, Jul 18, 2023 at 02:05:42PM +0200, Geert Uytterhoeven wrote: > > Hi Randy, > > > > On Tue, Jul 18, 2023 at 8:44 AM Randy Dunlap <rd.dunlab@gmail.com> wrote: > > > From: Randy Dunlap <rd.dunlab@gmail.com> > > > > > > When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build errors: > > > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > > drivers/pwm/pwm-rz-mtu3.c:374: undefined reference to `rz_mtu3_disable' > > > ld: drivers/pwm/pwm-rz-mtu3.c:377: undefined reference to `rz_mtu3_8bit_ch_write' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > > > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > > drivers/pwm/pwm-rz-mtu3.c:382: undefined reference to `rz_mtu3_8bit_ch_write' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > > > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' > > > ld: drivers/pwm/pwm-rz-mtu3.c:111: undefined reference to `rz_mtu3_16bit_ch_write' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > > drivers/pwm/pwm-rz-mtu3.c:397: undefined reference to `rz_mtu3_enable' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_disable': > > > drivers/pwm/pwm-rz-mtu3.c:259: undefined reference to `rz_mtu3_8bit_ch_write' > > > ld: drivers/pwm/pwm-rz-mtu3.c:264: undefined reference to `rz_mtu3_disable' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_enable': > > > drivers/pwm/pwm-rz-mtu3.c:230: undefined reference to `rz_mtu3_8bit_ch_write' > > > ld: drivers/pwm/pwm-rz-mtu3.c:234: undefined reference to `rz_mtu3_8bit_ch_write' > > > ld: drivers/pwm/pwm-rz-mtu3.c:238: undefined reference to `rz_mtu3_enable' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_is_ch_enabled': > > > drivers/pwm/pwm-rz-mtu3.c:155: undefined reference to `rz_mtu3_is_enabled' > > > ld: drivers/pwm/pwm-rz-mtu3.c:162: undefined reference to `rz_mtu3_8bit_ch_read' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_read_tgr_registers': > > > drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' > > > ld: drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' > > > ld: drivers/pwm/pwm-rz-mtu3.c:103: undefined reference to `rz_mtu3_16bit_ch_read' > > > ld: vmlinux.o: in function `rz_mtu3_pwm_get_state': > > > drivers/pwm/pwm-rz-mtu3.c:296: undefined reference to `rz_mtu3_8bit_ch_read' > > > > > > Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is > > > still allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built > > > but also allow the latter not to be built. > > > > > > Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver") > > > Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com > > > > Thanks for your patch! > > > > > --- a/drivers/pwm/Kconfig > > > +++ b/drivers/pwm/Kconfig > > > @@ -505,7 +505,8 @@ config PWM_ROCKCHIP > > > > > > config PWM_RZ_MTU3 > > > tristate "Renesas RZ/G2L MTU3a PWM Timer support" > > > - depends on RZ_MTU3 || COMPILE_TEST > > > + depends on COMPILE_TEST > > > > This makes the driver always depend on COMPILE_TEST, > > which is definitely not what we want. > > Honestly, do we really need all of this complexity? I have specific > configurations to test all of the PWM drivers to make sure they build. > There's probably edge cases that don't get tested, but sooner or later I > expect some build bot will encounter those and then we can rectify > things. But in many cases that I've seen COMPILE_TEST just happens to do > more harm than good. Without COMPILE_TEST you'd need to build at least for the following archs to build all pwm drivers: armv4+5 armv7 armv7m arm64 mips riscv shmobile x86 I personally like COMPILE_TEST as it reduces the number of needed test builds to 1 (I think). Best regards Uwe
On Tue, Jul 18, 2023 at 06:57:16PM +0200, Uwe Kleine-König wrote: > On Tue, Jul 18, 2023 at 03:24:58PM +0200, Thierry Reding wrote: > > On Tue, Jul 18, 2023 at 02:05:42PM +0200, Geert Uytterhoeven wrote: > > > Hi Randy, > > > > > > On Tue, Jul 18, 2023 at 8:44 AM Randy Dunlap <rd.dunlab@gmail.com> wrote: > > > > From: Randy Dunlap <rd.dunlab@gmail.com> > > > > > > > > When (MFD) RZ_MTU3=m and PWM_RZ_MTU3=y, there are numerous build errors: > > > > > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > > > drivers/pwm/pwm-rz-mtu3.c:374: undefined reference to `rz_mtu3_disable' > > > > ld: drivers/pwm/pwm-rz-mtu3.c:377: undefined reference to `rz_mtu3_8bit_ch_write' > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > > > > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > > > drivers/pwm/pwm-rz-mtu3.c:382: undefined reference to `rz_mtu3_8bit_ch_write' > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_write_tgr_registers': > > > > drivers/pwm/pwm-rz-mtu3.c:110: undefined reference to `rz_mtu3_16bit_ch_write' > > > > ld: drivers/pwm/pwm-rz-mtu3.c:111: undefined reference to `rz_mtu3_16bit_ch_write' > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_config': > > > > drivers/pwm/pwm-rz-mtu3.c:397: undefined reference to `rz_mtu3_enable' > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_disable': > > > > drivers/pwm/pwm-rz-mtu3.c:259: undefined reference to `rz_mtu3_8bit_ch_write' > > > > ld: drivers/pwm/pwm-rz-mtu3.c:264: undefined reference to `rz_mtu3_disable' > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_enable': > > > > drivers/pwm/pwm-rz-mtu3.c:230: undefined reference to `rz_mtu3_8bit_ch_write' > > > > ld: drivers/pwm/pwm-rz-mtu3.c:234: undefined reference to `rz_mtu3_8bit_ch_write' > > > > ld: drivers/pwm/pwm-rz-mtu3.c:238: undefined reference to `rz_mtu3_enable' > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_is_ch_enabled': > > > > drivers/pwm/pwm-rz-mtu3.c:155: undefined reference to `rz_mtu3_is_enabled' > > > > ld: drivers/pwm/pwm-rz-mtu3.c:162: undefined reference to `rz_mtu3_8bit_ch_read' > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_read_tgr_registers': > > > > drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' > > > > ld: drivers/pwm/pwm-rz-mtu3.c:102: undefined reference to `rz_mtu3_16bit_ch_read' > > > > ld: drivers/pwm/pwm-rz-mtu3.c:103: undefined reference to `rz_mtu3_16bit_ch_read' > > > > ld: vmlinux.o: in function `rz_mtu3_pwm_get_state': > > > > drivers/pwm/pwm-rz-mtu3.c:296: undefined reference to `rz_mtu3_8bit_ch_read' > > > > > > > > Modify the dependencies of PWM_RZ_MTU3 so that COMPILE_TEST is > > > > still allowed but PWM_RZ_MTU3 depends on RZ_MTU3 if it is being built > > > > but also allow the latter not to be built. > > > > > > > > Fixes: 254d3a727421 ("pwm: Add Renesas RZ/G2L MTU3a PWM driver") > > > > Signed-off-by: Randy Dunlap <rd.dunlab@gmail.com > > > > > > Thanks for your patch! > > > > > > > --- a/drivers/pwm/Kconfig > > > > +++ b/drivers/pwm/Kconfig > > > > @@ -505,7 +505,8 @@ config PWM_ROCKCHIP > > > > > > > > config PWM_RZ_MTU3 > > > > tristate "Renesas RZ/G2L MTU3a PWM Timer support" > > > > - depends on RZ_MTU3 || COMPILE_TEST > > > > + depends on COMPILE_TEST > > > > > > This makes the driver always depend on COMPILE_TEST, > > > which is definitely not what we want. > > > > Honestly, do we really need all of this complexity? I have specific > > configurations to test all of the PWM drivers to make sure they build. > > There's probably edge cases that don't get tested, but sooner or later I > > expect some build bot will encounter those and then we can rectify > > things. But in many cases that I've seen COMPILE_TEST just happens to do > > more harm than good. > > Without COMPILE_TEST you'd need to build at least for the following > archs to build all pwm drivers: > > armv4+5 > armv7 > armv7m > arm64 > mips > riscv > shmobile This one is actually ARCH_RENESAS and is armv7. > x86 But yeah, those are the platforms that I build for. It's not terribly complicated to do since all of the above have publicly available cross- compilers that are easy to install. Also, most of the time I do incremental builds, so these are quite quick. > I personally like COMPILE_TEST as it reduces the number of needed test > builds to 1 (I think). Anyway, I wasn't arguing that we should get rid of COMPILE_TEST altogether, just that for cases like this it doesn't seem worth the extra complexity. RZ_MTU3 is an MFD and already || COMPILE_TEST, so we can easily always enable it. Thierry
Hello, On Wed, Jul 19, 2023 at 09:40:22AM +0200, Thierry Reding wrote: > On Tue, Jul 18, 2023 at 06:57:16PM +0200, Uwe Kleine-König wrote: > > On Tue, Jul 18, 2023 at 03:24:58PM +0200, Thierry Reding wrote: > > > Honestly, do we really need all of this complexity? I have specific > > > configurations to test all of the PWM drivers to make sure they build. > > > There's probably edge cases that don't get tested, but sooner or later I > > > expect some build bot will encounter those and then we can rectify > > > things. But in many cases that I've seen COMPILE_TEST just happens to do > > > more harm than good. > > > > Without COMPILE_TEST you'd need to build at least for the following > > archs to build all pwm drivers: > > > > armv4+5 > > armv7 > > armv7m > > arm64 > > mips > > riscv > > shmobile > > This one is actually ARCH_RENESAS and is armv7. Oh indeed. ARCH_RENESAS exists for both arm and shmobile. TIL > > x86 > > But yeah, those are the platforms that I build for. It's not terribly > complicated to do since all of the above have publicly available cross- > compilers that are easy to install. Also, most of the time I do > incremental builds, so these are quite quick. > > > I personally like COMPILE_TEST as it reduces the number of needed test > > builds to 1 (I think). > > Anyway, I wasn't arguing that we should get rid of COMPILE_TEST > altogether, just that for cases like this it doesn't seem worth the > extra complexity. RZ_MTU3 is an MFD and already || COMPILE_TEST, so > we can easily always enable it. Ah, I got that wrong then. I can life with this one. Best regards Uwe
> -----Original Message----- > From: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> > Sent: Wednesday, July 19, 2023 11:14 AM > To: Thierry Reding <thierry.reding@gmail.com> > Cc: Geert Uytterhoeven <geert@linux-m68k.org>; Randy Dunlap > <rd.dunlab@gmail.com>; linux-kernel@vger.kernel.org; linux- > pwm@vger.kernel.org; Biju Das <biju.das.jz@bp.renesas.com> > Subject: Re: [PATCH v2] pwm: fix pwm-rz-mtu3.c build errors > > Hello, > > On Wed, Jul 19, 2023 at 09:40:22AM +0200, Thierry Reding wrote: > > On Tue, Jul 18, 2023 at 06:57:16PM +0200, Uwe Kleine-König wrote: > > > On Tue, Jul 18, 2023 at 03:24:58PM +0200, Thierry Reding wrote: > > > > Honestly, do we really need all of this complexity? I have > > > > specific configurations to test all of the PWM drivers to make > sure they build. > > > > There's probably edge cases that don't get tested, but sooner or > > > > later I expect some build bot will encounter those and then we can > > > > rectify things. But in many cases that I've seen COMPILE_TEST just > > > > happens to do more harm than good. > > > > > > Without COMPILE_TEST you'd need to build at least for the following > > > archs to build all pwm drivers: > > > > > > armv4+5 > > > armv7 > > > armv7m > > > arm64 > > > mips > > > riscv > > > shmobile > > > > This one is actually ARCH_RENESAS and is armv7. > > Oh indeed. ARCH_RENESAS exists for both arm and shmobile. TIL arm64 and risc-v too. This MTU3 driver should work on RISC-V(RZ/Five) as well(need to test at some point). Cheers, Biju > > > > x86 > > > > But yeah, those are the platforms that I build for. It's not terribly > > complicated to do since all of the above have publicly available > > cross- compilers that are easy to install. Also, most of the time I do > > incremental builds, so these are quite quick. > > > > > I personally like COMPILE_TEST as it reduces the number of needed > > > test builds to 1 (I think). > > > > Anyway, I wasn't arguing that we should get rid of COMPILE_TEST > > altogether, just that for cases like this it doesn't seem worth the > > extra complexity. RZ_MTU3 is an MFD and already || COMPILE_TEST, so we > > can easily always enable it. > > Ah, I got that wrong then. I can life with this one. > > Best regards > Uwe > > -- > Pengutronix e.K. | Uwe Kleine-König > | > Industrial Linux Solutions | https://www.pengutronix.de/ > |
Hi Uwe, On Wed, Jul 19, 2023 at 12:13 PM Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote: > On Wed, Jul 19, 2023 at 09:40:22AM +0200, Thierry Reding wrote: > > On Tue, Jul 18, 2023 at 06:57:16PM +0200, Uwe Kleine-König wrote: > > > On Tue, Jul 18, 2023 at 03:24:58PM +0200, Thierry Reding wrote: > > > > Honestly, do we really need all of this complexity? I have specific > > > > configurations to test all of the PWM drivers to make sure they build. > > > > There's probably edge cases that don't get tested, but sooner or later I > > > > expect some build bot will encounter those and then we can rectify > > > > things. But in many cases that I've seen COMPILE_TEST just happens to do > > > > more harm than good. > > > > > > Without COMPILE_TEST you'd need to build at least for the following > > > archs to build all pwm drivers: > > > > > > armv4+5 > > > armv7 > > > armv7m > > > arm64 > > > mips > > > riscv > > > shmobile > > > > This one is actually ARCH_RENESAS and is armv7. > > Oh indeed. ARCH_RENESAS exists for both arm and shmobile. TIL No, SH-Mobile can be either sh, arm, or both ;-) ARCH_SHMOBILE is sh. ARCH_RENESAS is arm, arm64, or riscv. The Renesas/arm defconfig is called shmobile_defconfig for historical reasons. Gr{oetje,eeting}s, Geert
diff -- a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig --- a/drivers/pwm/Kconfig +++ b/drivers/pwm/Kconfig @@ -505,7 +505,8 @@ config PWM_ROCKCHIP config PWM_RZ_MTU3 tristate "Renesas RZ/G2L MTU3a PWM Timer support" - depends on RZ_MTU3 || COMPILE_TEST + depends on COMPILE_TEST + depends on RZ_MTU3 || RZ_MTU3=n depends on HAS_IOMEM help This driver exposes the MTU3a PWM Timer controller found in Renesas