From: Leonard Crestez <leonard.crestez@nxp.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Mark Brown <broonie@kernel.org>, Robin Gong <yibin.gong@nxp.com>,
Anson Huang <Anson.Huang@nxp.com>,
Irina Tirdea <irina.tirdea@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Octavian Purdila <octavian.purdila@nxp.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] ARM: imx: gpc: Do not print error message for EPROBE_DEFER
Date: Tue, 4 Apr 2017 13:28:03 +0300 [thread overview]
Message-ID: <1491301683.1654.8.camel@nxp.com> (raw)
In-Reply-To: <1491299184.2367.12.camel@pengutronix.de>
On Tue, 2017-04-04 at 11:46 +0200, Lucas Stach wrote:
> Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> >
> > The pu regulator request will return -EPROBE_DEFER if it has a supply
> > from PMIC and this supply is not yet registered. This does not represent
> > an error since the driver will call probe again later, so only print a
> > warning message in this case.
> >
> > Signed-off-by: Irina Tirdea <irina.tirdea@nxp.com>
> > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
> > ---
> > arch/arm/mach-imx/gpc.c | 6 +++++-
> The driver moved places, together with a large rewrite, to
> drivers/soc/imx/.
>
> This issue isn't present in the new driver, so this patch can just be
> dropped.
Wait, I'm confused. In what tree did that happen? This patch is against
linus's tree as of last week and there is nothing in drivers/soc/imx.
I saw patches for a new gpcv2 driver but that seems to be only for
imx7. This patch is for imx6. Will that driver also support imx6?
Link: https://lkml.org/lkml/2017/3/28/834
--
Regards,
Leonard
WARNING: multiple messages have this Message-ID (diff)
From: leonard.crestez@nxp.com (Leonard Crestez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ARM: imx: gpc: Do not print error message for EPROBE_DEFER
Date: Tue, 4 Apr 2017 13:28:03 +0300 [thread overview]
Message-ID: <1491301683.1654.8.camel@nxp.com> (raw)
In-Reply-To: <1491299184.2367.12.camel@pengutronix.de>
On Tue, 2017-04-04 at 11:46 +0200, Lucas Stach wrote:
> Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> >
> > The pu regulator request will return -EPROBE_DEFER if it has a supply
> > from PMIC and this supply is not yet registered. This does not represent
> > an error since the driver will call probe again later, so only print a
> > warning message in this case.
> >
> > Signed-off-by: Irina Tirdea <irina.tirdea@nxp.com>
> > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
> > ---
> > ?arch/arm/mach-imx/gpc.c | 6 +++++-
> The driver moved places, together with a large rewrite, to
> drivers/soc/imx/.
>
> This issue isn't present in the new driver, so this patch can just be
> dropped.
Wait, I'm confused. In what tree did that happen? This patch is against
linus's tree as of last week and there is nothing in drivers/soc/imx.
I saw patches for a new gpcv2 driver but that seems to be only for
imx7. This patch is for imx6. Will that driver also support imx6?
Link:?https://lkml.org/lkml/2017/3/28/834
--
Regards,
Leonard
WARNING: multiple messages have this Message-ID (diff)
From: Leonard Crestez <leonard.crestez@nxp.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Mark Brown <broonie@kernel.org>, Robin Gong <yibin.gong@nxp.com>,
Anson Huang <Anson.Huang@nxp.com>,
Irina Tirdea <irina.tirdea@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
"Octavian Purdila" <octavian.purdila@nxp.com>,
Liam Girdwood <lgirdwood@gmail.com>, <linux-pm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/5] ARM: imx: gpc: Do not print error message for EPROBE_DEFER
Date: Tue, 4 Apr 2017 13:28:03 +0300 [thread overview]
Message-ID: <1491301683.1654.8.camel@nxp.com> (raw)
In-Reply-To: <1491299184.2367.12.camel@pengutronix.de>
On Tue, 2017-04-04 at 11:46 +0200, Lucas Stach wrote:
> Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> >
> > The pu regulator request will return -EPROBE_DEFER if it has a supply
> > from PMIC and this supply is not yet registered. This does not represent
> > an error since the driver will call probe again later, so only print a
> > warning message in this case.
> >
> > Signed-off-by: Irina Tirdea <irina.tirdea@nxp.com>
> > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
> > ---
> > arch/arm/mach-imx/gpc.c | 6 +++++-
> The driver moved places, together with a large rewrite, to
> drivers/soc/imx/.
>
> This issue isn't present in the new driver, so this patch can just be
> dropped.
Wait, I'm confused. In what tree did that happen? This patch is against
linus's tree as of last week and there is nothing in drivers/soc/imx.
I saw patches for a new gpcv2 driver but that seems to be only for
imx7. This patch is for imx6. Will that driver also support imx6?
Link: https://lkml.org/lkml/2017/3/28/834
--
Regards,
Leonard
next prev parent reply other threads:[~2017-04-04 10:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 19:25 [PATCH 0/5] ARM: imx: Set LDO regulator supply Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-03-31 19:25 ` [PATCH 1/5] ARM: imx: gpc: Do not print error message for EPROBE_DEFER Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-04-04 9:46 ` Lucas Stach
2017-04-04 9:46 ` Lucas Stach
2017-04-04 10:28 ` Leonard Crestez [this message]
2017-04-04 10:28 ` Leonard Crestez
2017-04-04 10:28 ` Leonard Crestez
2017-04-04 10:30 ` Lucas Stach
2017-04-04 10:30 ` Lucas Stach
2017-04-04 10:30 ` Lucas Stach
2017-03-31 19:25 ` [PATCH 2/5] cpufreq: imx6q: Fix handling EPROBE_DEFER from regulator Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-04-04 9:48 ` Lucas Stach
2017-04-04 9:48 ` Lucas Stach
2017-03-31 19:25 ` [PATCH 3/5] cpufreq: imx6q: Set max suspend_freq to avoid changes during suspend Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-04-04 9:51 ` Lucas Stach
2017-04-04 9:51 ` Lucas Stach
2017-04-04 17:04 ` Leonard Crestez
2017-04-04 17:04 ` Leonard Crestez
2017-04-04 17:04 ` Leonard Crestez
2017-03-31 19:25 ` [PATCH 4/5] ARM: dts: imx6qdl-sabresd: Set LDO regulator supply Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-04-04 9:52 ` Lucas Stach
2017-04-04 9:52 ` Lucas Stach
2017-04-04 9:52 ` Lucas Stach
2017-03-31 19:25 ` [PATCH 5/5] ARM: dts: imx6qp-sabresd: Set reg_arm " Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-03-31 19:25 ` Leonard Crestez
2017-04-04 9:53 ` Lucas Stach
2017-04-04 9:53 ` Lucas Stach
2017-04-04 9:53 ` Lucas Stach
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=1491301683.1654.8.camel@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=broonie@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=irina.tirdea@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=octavian.purdila@nxp.com \
--cc=rjw@rjwysocki.net \
--cc=shawnguo@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=yibin.gong@nxp.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.