public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] pinctrl: sunxi: Start to enforce the strict mode
Date: Wed, 25 Oct 2017 14:40:27 +0200	[thread overview]
Message-ID: <20171025124027.oosswpymrwkvcvxx@flea> (raw)
In-Reply-To: <cover.3e8ef5cb08d0164375d7644df0548e5f39b0fe66.1507582414.git-series.maxime.ripard@free-electrons.com>

Hi Linus,

On Mon, Oct 09, 2017 at 10:53:36PM +0200, Maxime Ripard wrote:
> Hi,
> 
> Here is an attempt to enable pinctrl's strict mode on our pinctrl drivers.
> Indeed, our controllers should have had that mode enabled since its
> introduction.
> 
> However, there's a number of issues with old device trees that prevent from
> just enabling it for all the devices. There's basically two of them:
> 
>   - Most of our old DTs have a pinctrl node for GPIOs, which will result in
>     an error when the driver is going to request the gpio because it would
>     already be requested automatically by pinctrl. We cannot break those.
> 
>   - Some of these GPIOs also need to change their pin configuration to add
>     a bias or change the current output, and there isn't a migration path.
> 
> Let's just keep the old behaviour for the old SoCs, and enforce it on the
> new one, and enabled it by default so that the situation at least doesn't
> get worse.
> 
> This has been tested on an A83t (strict on) and an H3 (strict off) board.

Did you have some time to look at this?

The earlier we merge it the better, so ideally I'd really like to get
this into 4.15.

Thanks!
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171025/b282be95/attachment.sig>

  parent reply	other threads:[~2017-10-25 12:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 20:53 [PATCH v2 0/3] pinctrl: sunxi: Start to enforce the strict mode Maxime Ripard
2017-10-09 20:53 ` [PATCH v2 1/3] pinctrl: sunxi: Introduce the strict flag Maxime Ripard
2017-10-31  8:44   ` Linus Walleij
2017-10-09 20:53 ` [PATCH v2 2/3] pinctrl: sunxi: Disable strict mode for old pinctrl drivers Maxime Ripard
2017-10-31  8:45   ` Linus Walleij
2017-10-09 20:53 ` [PATCH v2 3/3] pinctrl: sunxi: Enforce the strict mode by default Maxime Ripard
2017-10-31  8:46   ` Linus Walleij
2017-10-10  2:36 ` [PATCH v2 0/3] pinctrl: sunxi: Start to enforce the strict mode Chen-Yu Tsai
2017-10-25 12:40 ` Maxime Ripard [this message]
2017-10-31  8:46   ` Linus Walleij
2017-10-31  8:52     ` Maxime Ripard

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=20171025124027.oosswpymrwkvcvxx@flea \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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