From: Fabio Estevam <festevam@gmail.com>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
NXP Linux Team <Linux-imx@nxp.com>
Subject: Re: [PATCH V2] gpio: mxc: add power management support
Date: Tue, 17 Jul 2018 10:52:03 -0300 [thread overview]
Message-ID: <CAOMZO5D9MBOwQtKVqSD8XUtDBf9RH5+soV2jreBYHZrXzLWm6A@mail.gmail.com> (raw)
In-Reply-To: <1531721186-19417-1-git-send-email-Anson.Huang@nxp.com>
Hi Anson,
[Next time please put the i.mx maintainers on Cc]
On Mon, Jul 16, 2018 at 3:06 AM, Anson Huang <Anson.Huang@nxp.com> wrote:
> GPIO registers could lose context on i.MX7D,
> when enter LPSR mode, the whole SoC will be
> powered off except LPSR domain, GPIO banks
> will lose context in this case, need to restore
> the context after resume from LPSR mode.
>
> This patch adds GPIO save/restore for those necessary
> registers, and put the save/restore operations in noirq
> suspend/resume phase, since GPIO is fundamental module
> which could be used by other peripherals' resume phase.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> static struct mxc_gpio_hwdata imx1_imx21_gpio_hwdata = {
> @@ -434,6 +445,9 @@ static int mxc_gpio_probe(struct platform_device *pdev)
> return err;
> }
>
> + if (of_machine_is_compatible("fsl,imx7d"))
> + port->support_power_off = true;
This does not scale well as we need to support mx8 soon.
Like I replied in my last message the best solution here is to add a
"fsl,imx7d-gpio" compatible entry in this driver.
Then you can set a flag in the "fsl,imx7d-gpio" case to handle the
'power_off' feature.
With this method there will be no need to touch this driver again for
adding mx8 support.
next prev parent reply other threads:[~2018-07-17 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 6:06 [PATCH V2] gpio: mxc: add power management support Anson Huang
2018-07-17 13:52 ` Fabio Estevam [this message]
2018-07-18 0:54 ` Anson Huang
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=CAOMZO5D9MBOwQtKVqSD8XUtDBf9RH5+soV2jreBYHZrXzLWm6A@mail.gmail.com \
--to=festevam@gmail.com \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).