linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1 2/2] pinctrl: intel: Move npins closer to pin_base in struct intel_community
Date: Wed, 22 Apr 2020 14:13:46 +0300	[thread overview]
Message-ID: <20200422111346.GA185537@smile.fi.intel.com> (raw)
In-Reply-To: <20200422094526.GY185537@smile.fi.intel.com>

On Wed, Apr 22, 2020 at 12:45:26PM +0300, Andy Shevchenko wrote:
> On Wed, Apr 22, 2020 at 11:50:56AM +0300, Mika Westerberg wrote:
> > On Tue, Apr 21, 2020 at 10:00:49PM +0300, Andy Shevchenko wrote:
> > > It's common across the drivers to use the (pin_base, npins) pair to describe
> > > community characteristics. Thus, move them in the struct intel_community
> > > to be closer to each other.
> > > 
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > ---
> > >  drivers/pinctrl/intel/pinctrl-intel.h | 5 +++--
> > >  1 file changed, 3 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/drivers/pinctrl/intel/pinctrl-intel.h b/drivers/pinctrl/intel/pinctrl-intel.h
> > > index 058bf2b6d9f0e..bd653f2a07382 100644
> > > --- a/drivers/pinctrl/intel/pinctrl-intel.h
> > > +++ b/drivers/pinctrl/intel/pinctrl-intel.h
> > > @@ -94,12 +94,12 @@ enum {
> > >   * @ie_offset: Register offset of GPI_IE from @regs.
> > >   * @features: Additional features supported by the hardware
> > >   * @pin_base: Starting pin of pins in this community
> > > + * @npins: Number of pins in this community
> > >   * @gpp_size: Maximum number of pads in each group, such as GPI_IS, GPI_IE,
> > >   *            PADCFGLOCK, HOSTSW_OWN. Used when @gpps is %NULL.
> > >   * @gpp_num_padown_regs: Number of pad registers each pad group consumes at
> > >   *			 minimum. Use %0 if the number of registers can be
> > >   *			 determined by the size of the group.
> > > - * @npins: Number of pins in this community
> > >   * @gpps: Pad groups if the controller has variable size pad groups
> > >   * @ngpps: Number of pad groups in this community
> > >   * @pad_map: Optional non-linear mapping of the pads
> > > @@ -121,12 +121,13 @@ struct intel_community {
> > >  	unsigned int ie_offset;
> > >  	unsigned int features;
> > >  	unsigned int pin_base;
> > > +	size_t npins;
> > >  	unsigned int gpp_size;
> > >  	unsigned int gpp_num_padown_regs;
> > > -	size_t npins;
> > >  	const struct intel_padgroup *gpps;
> > >  	size_t ngpps;
> > >  	const unsigned int *pad_map;
> > > +
> > 
> > Unrelated whitespace change?
> 
> Not so. I can add justification to commit message.
> 
> > In any case,
> > 
> > Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> 
> Thanks.


Both pushed to my review and testing queue, thanks!

Second one with slightly updated commit message to reflect blank line change.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2020-04-22 11:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 19:00 [PATCH v1 1/2] pinctrl: intel: Update description in struct intel_community Andy Shevchenko
2020-04-21 19:00 ` [PATCH v1 2/2] pinctrl: intel: Move npins closer to pin_base " Andy Shevchenko
2020-04-22  8:50   ` Mika Westerberg
2020-04-22  9:45     ` Andy Shevchenko
2020-04-22 11:13       ` Andy Shevchenko [this message]
2020-04-22  8:49 ` [PATCH v1 1/2] pinctrl: intel: Update description " Mika Westerberg

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=20200422111346.GA185537@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.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 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).