All of lore.kernel.org
 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 1/4] pinctrl: intel: Introduce common flags for GPIO mapping scheme
Date: Wed, 1 Apr 2020 15:56:57 +0300	[thread overview]
Message-ID: <20200401125657.GT1922688@smile.fi.intel.com> (raw)
In-Reply-To: <20200401095142.GS2564@lahna.fi.intel.com>

On Wed, Apr 01, 2020 at 12:51:42PM +0300, Mika Westerberg wrote:
> On Tue, Mar 31, 2020 at 06:25:44PM +0300, Andy Shevchenko wrote:
> > Few drivers are using the same flag to tell Intel pin control core
> > how to interpret GPIO base.
> > 
> > Provide a generic flags so all drivers can use.

...

> > - * @gpio_base: Starting GPIO base of this group (%0 if matches with @base,
> > - *	       and %-1 if no GPIO mapping should be created)
> > + * @gpio_base: Starting GPIO base of this group

> > @@ -64,6 +63,8 @@ struct intel_padgroup {
> >  	unsigned int reg_num;
> >  	unsigned int base;
> >  	unsigned int size;
> > +#define INTEL_GPIO_BASE_MATCH	0	/* matches with @base */
> > +#define INTEL_GPIO_BASE_NOMAP	(-1)	/* no GPIO mapping should be created */
> 
> Maybe use enum and add kernel-doc there?
> 
> >  	int gpio_base;

Will do it in v2, thanks!

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2020-04-01 12:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 15:25 [PATCH v1 1/4] pinctrl: intel: Introduce common flags for GPIO mapping scheme Andy Shevchenko
2020-03-31 15:25 ` [PATCH v1 2/4] pinctrl: cannonlake: Use generic flag for special GPIO base treatment Andy Shevchenko
2020-03-31 15:25 ` [PATCH v1 3/4] pinctrl: icelake: " Andy Shevchenko
2020-03-31 15:25 ` [PATCH v1 4/4] pinctrl: tigerlake: " Andy Shevchenko
2020-04-01  9:51 ` [PATCH v1 1/4] pinctrl: intel: Introduce common flags for GPIO mapping scheme Mika Westerberg
2020-04-01 12:56   ` Andy Shevchenko [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=20200401125657.GT1922688@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 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.