From: Andy Shevchenko <andy.shevchenko@gmail.com> To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net> Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, Linus Walleij <linus.walleij@linaro.org>, Rob Herring <robh+dt@kernel.org>, "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>, Tomer Maimon <tmaimon77@gmail.com>, Joel Stanley <joel@jms.id.au>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v2 5/8] pinctrl: nuvoton: Add driver for WPCM450 Date: Wed, 8 Dec 2021 16:14:38 +0200 [thread overview] Message-ID: <CAHp75VdYtLbCLi7iD0UT7MrPi9oxJLWA9ZCBo7uGbWxNCBdGyw@mail.gmail.com> (raw) In-Reply-To: <YbC6Bv2teZ5CFhFQ@latitude> On Wed, Dec 8, 2021 at 3:58 PM Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote: > On Wed, Dec 08, 2021 at 01:24:18PM +0200, Andy Shevchenko wrote: > > On Tuesday, December 7, 2021, Jonathan Neuschäfer <j.neuschaefer@gmx.net> > > wrote: ... > > > + ours = ((1UL << gpio->num_irqs) - 1) << gpio->first_irq_bit; > > > > BIT() > > I'll use it, but in this case, I think it doesn't simplify much the > whole expression all that much. It is still better to use in my opinion. > Is there perhaps a macro that > constructs a continuous bitmask of N bits, perhaps additionally > left-shifted by M bits? > Maybe somewhere in the bitmap_* API... Maybe, I dunno since I haven't clearly got this code anyway, so up to you to check and see what to do about it. ... > > > + struct fwnode_handle *np; > > > > Either be fully OF, or don’t name ‘np' here. We usually use fwnode or > > ‘child’ in this case. > > Ah, I thought "np" (= node pointer) was still appropriate because I'm > dealing with firmware _nodes_. My intention was indeed to switch fully > to the fwnode API. Just a convention "de facto". ... > > > + ret = gpiochip_add_pin_range(&gpio->gc, > > > dev_name(pctrl->dev), > > > + 0, bank->base, bank->length); > > > + if (ret) { > > > + dev_err(pctrl->dev, "Failed to add pin range for > > > GPIO bank %u\n", reg); > > > + return ret; > > > + } > > > > Please move it to the corresponding callback. > > What's the corresponding callback? https://elixir.bootlin.com/linux/latest/source/include/linux/gpio/driver.h#L400 -- With Best Regards, Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andy.shevchenko@gmail.com> To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net> Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, Tomer Maimon <tmaimon77@gmail.com>, Linus Walleij <linus.walleij@linaro.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>, "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org> Subject: Re: [PATCH v2 5/8] pinctrl: nuvoton: Add driver for WPCM450 Date: Wed, 8 Dec 2021 16:14:38 +0200 [thread overview] Message-ID: <CAHp75VdYtLbCLi7iD0UT7MrPi9oxJLWA9ZCBo7uGbWxNCBdGyw@mail.gmail.com> (raw) In-Reply-To: <YbC6Bv2teZ5CFhFQ@latitude> On Wed, Dec 8, 2021 at 3:58 PM Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote: > On Wed, Dec 08, 2021 at 01:24:18PM +0200, Andy Shevchenko wrote: > > On Tuesday, December 7, 2021, Jonathan Neuschäfer <j.neuschaefer@gmx.net> > > wrote: ... > > > + ours = ((1UL << gpio->num_irqs) - 1) << gpio->first_irq_bit; > > > > BIT() > > I'll use it, but in this case, I think it doesn't simplify much the > whole expression all that much. It is still better to use in my opinion. > Is there perhaps a macro that > constructs a continuous bitmask of N bits, perhaps additionally > left-shifted by M bits? > Maybe somewhere in the bitmap_* API... Maybe, I dunno since I haven't clearly got this code anyway, so up to you to check and see what to do about it. ... > > > + struct fwnode_handle *np; > > > > Either be fully OF, or don’t name ‘np' here. We usually use fwnode or > > ‘child’ in this case. > > Ah, I thought "np" (= node pointer) was still appropriate because I'm > dealing with firmware _nodes_. My intention was indeed to switch fully > to the fwnode API. Just a convention "de facto". ... > > > + ret = gpiochip_add_pin_range(&gpio->gc, > > > dev_name(pctrl->dev), > > > + 0, bank->base, bank->length); > > > + if (ret) { > > > + dev_err(pctrl->dev, "Failed to add pin range for > > > GPIO bank %u\n", reg); > > > + return ret; > > > + } > > > > Please move it to the corresponding callback. > > What's the corresponding callback? https://elixir.bootlin.com/linux/latest/source/include/linux/gpio/driver.h#L400 -- With Best Regards, Andy Shevchenko
next prev parent reply other threads:[~2021-12-08 14:16 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-07 21:08 [PATCH v2 0/8] Nuvoton WPCM450 pinctrl and GPIO driver Jonathan Neuschäfer 2021-12-07 21:08 ` Jonathan Neuschäfer 2021-12-07 21:08 ` [PATCH v2 1/8] dt-bindings: arm/npcm: Add binding for global control registers (GCR) Jonathan Neuschäfer 2021-12-07 21:08 ` Jonathan Neuschäfer 2021-12-08 13:44 ` Rob Herring 2021-12-08 13:44 ` Rob Herring 2021-12-10 14:54 ` Rob Herring 2021-12-10 14:54 ` Rob Herring 2021-12-12 23:12 ` Jonathan Neuschäfer 2021-12-12 23:12 ` Jonathan Neuschäfer 2021-12-07 21:08 ` [PATCH v2 2/8] MAINTAINERS: Match all of bindings/arm/npcm/ as part of NPCM architecture Jonathan Neuschäfer 2021-12-07 21:08 ` Jonathan Neuschäfer 2021-12-07 21:08 ` [PATCH v2 3/8] ARM: dts: wpcm450: Add global control registers (GCR) node Jonathan Neuschäfer 2021-12-07 21:08 ` Jonathan Neuschäfer 2021-12-07 21:08 ` [PATCH v2 4/8] dt-bindings: pinctrl: Add Nuvoton WPCM450 Jonathan Neuschäfer 2021-12-07 21:08 ` Jonathan Neuschäfer 2021-12-08 13:44 ` Rob Herring 2021-12-08 13:44 ` Rob Herring 2021-12-10 15:18 ` Rob Herring 2021-12-10 15:18 ` Rob Herring 2021-12-12 23:38 ` Jonathan Neuschäfer 2021-12-12 23:38 ` Jonathan Neuschäfer 2021-12-07 21:08 ` [PATCH v2 5/8] pinctrl: nuvoton: Add driver for WPCM450 Jonathan Neuschäfer 2021-12-07 21:08 ` Jonathan Neuschäfer 2021-12-08 0:51 ` kernel test robot 2021-12-08 0:51 ` kernel test robot 2021-12-08 0:51 ` kernel test robot 2021-12-08 2:34 ` kernel test robot 2021-12-08 2:34 ` kernel test robot 2021-12-08 2:34 ` kernel test robot 2021-12-08 11:24 ` Andy Shevchenko 2021-12-08 13:58 ` Jonathan Neuschäfer 2021-12-08 13:58 ` Jonathan Neuschäfer 2021-12-08 14:14 ` Andy Shevchenko [this message] 2021-12-08 14:14 ` Andy Shevchenko 2021-12-12 23:02 ` Jonathan Neuschäfer 2021-12-12 23:02 ` Jonathan Neuschäfer 2021-12-09 8:26 ` Zev Weiss 2021-12-09 8:26 ` Zev Weiss 2021-12-10 1:41 ` Linus Walleij 2021-12-10 1:41 ` Linus Walleij 2021-12-12 23:03 ` Jonathan Neuschäfer 2021-12-12 23:03 ` Jonathan Neuschäfer 2021-12-07 21:08 ` [PATCH v2 6/8] ARM: dts: wpcm450: Add pinctrl and GPIO nodes Jonathan Neuschäfer 2021-12-07 21:08 ` Jonathan Neuschäfer 2021-12-10 1:42 ` Linus Walleij 2021-12-10 1:42 ` Linus Walleij 2021-12-07 21:08 ` [PATCH v2 7/8] ARM: dts: wpcm450: Add pin functions Jonathan Neuschäfer 2021-12-07 21:08 ` Jonathan Neuschäfer 2021-12-07 21:08 ` [PATCH v2 8/8] ARM: dts: wpcm450-supermicro-x9sci-ln4f: Add GPIO LEDs and buttons Jonathan Neuschäfer 2021-12-07 21:08 ` Jonathan Neuschäfer 2021-12-09 18:40 [PATCH v2 5/8] pinctrl: nuvoton: Add driver for WPCM450 kernel test robot 2021-12-19 1:24 kernel test robot
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=CAHp75VdYtLbCLi7iD0UT7MrPi9oxJLWA9ZCBo7uGbWxNCBdGyw@mail.gmail.com \ --to=andy.shevchenko@gmail.com \ --cc=devicetree@vger.kernel.org \ --cc=j.neuschaefer@gmx.net \ --cc=joel@jms.id.au \ --cc=linus.walleij@linaro.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=openbmc@lists.ozlabs.org \ --cc=robh+dt@kernel.org \ --cc=tmaimon77@gmail.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.