From: Cristina Ciocan <cristina.ciocan@intel.com>
To: mathias.nyman@linux.intel.com, mika.westerberg@linux.intel.com,
heikki.krogerus@linux.intel.com, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, irina.tirdea@intel.com,
octavian.purdila@intel.com
Subject: Re: [PATCH v4 0/6] Add pinctrl support for Baytrail
Date: Fri, 1 Apr 2016 14:01:08 +0300 [thread overview]
Message-ID: <56FE54F4.7010101@intel.com> (raw)
In-Reply-To: <1459508183-21843-1-git-send-email-cristina.ciocan@intel.com>
On 01.04.2016 13:56, Cristina Ciocan wrote:
> Add support for pin control (pin muxing and pin configuration) for Baytrail
> platform.
>
> It follows the design in pinctrl-intel.c, but could not use the
> implementation in pinctrl-intel since there were significant differences:
> - gpio pin pads are not ordered
> - per group functions: for setting a certain mode, there are groups
> that need setting pins with different values; for instance, for
> setting USB ULPI pins to GPIO function, pin 2 (GPIO_SUS1) needs
> to be set to function 1, wihle all other from the group need to be
> set to 0
> - communities only need pin base and count as specific data
> - irq set type only clears all flags, while the actual type setting
> is made in the byt_irq_unmask function, which does not comply with
> the intel pinctrl implementation
>
> Changes from v3:
> - fix GPIO_* pin names to match naming conventions used in other
> Intel pinctrl drivers
>
> Changes from v2:
> - remove comment for each enumerated pin
> - apply pin naming conventions used in other Intel drivers
>
> Changes from v1:
> - fix reg, reg_val and byt_soc_data not used variables warnings
>
> Cristina Ciocan (6):
> pinctrl: baytrail: Add pin control data structures
> pinctrl: baytrail: Add pin control operations
> pinctrl: baytrail: Update gpio chip operations
> pinctrl: baytrail: Update irq chip operations
> pinctrl: baytrail: Register pin control handling
> pinctrl: baytrail: Add debounce configuration
>
> drivers/pinctrl/intel/Kconfig | 3 +
> drivers/pinctrl/intel/pinctrl-baytrail.c | 1690 +++++++++++++++++++++++++-----
> 2 files changed, 1444 insertions(+), 249 deletions(-)
>
> --
> 1.9.1
>
Sorry, sent double set of patches by mistache. Resent the good series
afterwards.
next prev parent reply other threads:[~2016-04-01 11:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 10:56 [PATCH v4 0/6] Add pinctrl support for Baytrail Cristina Ciocan
2016-04-01 10:56 ` Cristina Ciocan
2016-04-01 10:56 ` [PATCH v4 1/6] pinctrl: baytrail: Add pin control data structures Cristina Ciocan
2016-04-01 10:56 ` [PATCH 2/7] " Cristina Ciocan
2016-04-01 10:56 ` [PATCH v4 2/6] pinctrl: baytrail: Add pin control operations Cristina Ciocan
2016-04-01 10:56 ` [PATCH 3/7] " Cristina Ciocan
2016-04-01 10:56 ` [PATCH v4 3/6] pinctrl: baytrail: Update gpio chip operations Cristina Ciocan
2016-04-01 10:56 ` [PATCH 4/7] " Cristina Ciocan
2016-04-01 10:56 ` [PATCH v4 4/6] pinctrl: baytrail: Update irq " Cristina Ciocan
2016-04-01 10:56 ` [PATCH v4 5/6] pinctrl: baytrail: Register pin control handling Cristina Ciocan
2016-04-01 10:56 ` [PATCH 5/7] pinctrl: baytrail: Update irq chip operations Cristina Ciocan
2016-04-01 10:56 ` [PATCH v4 6/6] pinctrl: baytrail: Add debounce configuration Cristina Ciocan
2016-04-01 10:56 ` [PATCH 6/7] pinctrl: baytrail: Register pin control handling Cristina Ciocan
2016-04-01 10:56 ` [PATCH 7/7] pinctrl: baytrail: Add debounce configuration Cristina Ciocan
2016-04-01 11:01 ` Cristina Ciocan [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-01 11:00 [PATCH v4 0/6] Add pinctrl support for Baytrail Cristina Ciocan
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=56FE54F4.7010101@intel.com \
--to=cristina.ciocan@intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=irina.tirdea@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=octavian.purdila@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.