From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: Shyam-sundar.S-k@amd.com, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org, mika.westerberg@linux.intel.com
Subject: Re: [PATCH v3 1/6] pinctrl: Add pingroup and define PINCTRL_GRP
Date: Tue, 31 May 2022 12:19:30 +0300 [thread overview]
Message-ID: <YpXdooVIYNQGoQMt@smile.fi.intel.com> (raw)
In-Reply-To: <20220531084322.1310250-2-Basavaraj.Natikar@amd.com>
On Tue, May 31, 2022 at 02:13:17PM +0530, Basavaraj Natikar wrote:
> Add 'struct pingroup' to represent pingroup and 'PINCTRL_GRP' macro for
> inline use. Both are used to manage and represent larger number
> of pingroups.
Thanks! My comments below.
...
> +/**
> + * struct pingroups - provides information on pingroup
Try `make W=1` against each of your patches from the series. Here is the kernel
doc issue.
> + * @name: a name for pingroup
> + * @pins: an array of pins in the pingroup
> + * @npins: number of pins in the pingroup
> + */
> +struct pingroup {
> + const char *name;
> + const unsigned int *pins;
> + unsigned int npins;
size_t probably would be better.
> +};
> +
> +/* Convenience macro to define a single named or anonymous pingroup */
> +#define PINCTRL_GRP(_name, _pins, _npins) \
I think PINCTRL_PINGROUP would be more precise.
> +((struct pingroup) { \
No need to have space before { and compound literal means that it's not a GCC
expression, i.e. drop outer parentheses ().
> + .name = _name, \
> + .pins = _pins, \
> + .npins = _npins, \
> +})
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-05-31 9:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 8:43 [PATCH v3 0/6] Enhancements to AMD pinctrl and implementation of AMD pinmux Basavaraj Natikar
2022-05-31 8:43 ` [PATCH v3 1/6] pinctrl: Add pingroup and define PINCTRL_GRP Basavaraj Natikar
2022-05-31 9:19 ` Andy Shevchenko [this message]
2022-05-31 14:05 ` Basavaraj Natikar
2022-05-31 18:47 ` Andy Shevchenko
2022-05-31 8:43 ` [PATCH v3 2/6] pinctrl: amd: Remove amd_pingroup and use pingroup Basavaraj Natikar
2022-05-31 10:21 ` Andy Shevchenko
2022-05-31 8:43 ` [PATCH v3 3/6] pinctrl: amd: Use PINCTRL_GRP to manage pingroups Basavaraj Natikar
2022-05-31 10:22 ` Andy Shevchenko
2022-05-31 8:43 ` [PATCH v3 4/6] pinctrl: amd: Define and use AMD_PINS macro Basavaraj Natikar
2022-05-31 10:23 ` Andy Shevchenko
2022-05-31 13:58 ` Basavaraj Natikar
2022-05-31 15:47 ` Andy Shevchenko
2022-05-31 8:43 ` [PATCH v3 5/6] pinctrl: amd: Add amd_get_iomux_res function Basavaraj Natikar
2022-05-31 10:26 ` Andy Shevchenko
2022-05-31 8:43 ` [PATCH v3 6/6] pinctrl: amd: Implement pinmux functionality Basavaraj Natikar
2022-05-31 10:32 ` Andy Shevchenko
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=YpXdooVIYNQGoQMt@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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: link
Be 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.