From: Dan Carpenter <dan.carpenter@oracle.com>
To: Aisheng Dong <aisheng.dong@nxp.com>
Cc: BOUGH CHEN <haibo.chen@nxp.com>,
"festevam@gmail.com" <festevam@gmail.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"stefan@agner.ch" <stefan@agner.ch>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] Revert "pinctrl: freescale: imx: Use 'devm_of_iomap()' to avoid a resource leak in case of error in 'imx_pinctrl_probe()'"
Date: Mon, 8 Jun 2020 17:44:31 +0300 [thread overview]
Message-ID: <20200608144431.GS22511@kadam> (raw)
In-Reply-To: <AM6PR04MB496691DDA4447CD5624EE6E680850@AM6PR04MB4966.eurprd04.prod.outlook.com>
On Mon, Jun 08, 2020 at 02:06:35PM +0000, Aisheng Dong wrote:
> > From: haibo.chen@nxp.com <haibo.chen@nxp.com>
> > Sent: Monday, June 8, 2020 6:00 PM
> >
> > This patch block system booting, find on imx7d-sdb board.
> > From the dts we can see, iomux and iomux_lpsr share the memory region
> > [0x30330000-0x3033ffff], so will trigger the following issue:
> >
> > [ 0.179561] imx7d-pinctrl 302c0000.iomuxc-lpsr: initialized IMX pinctrl
> > driver
> > [ 0.191742] imx7d-pinctrl 30330000.pinctrl: can't request region for
> > resource [mem 0x30330000-0x3033ffff]
> > [ 0.191842] imx7d-pinctrl: probe of 30330000.pinctrl failed with error -16
> >
> > This reverts commit ba403242615c2c99e27af7984b1650771a2cc2c9.
>
> Better add your sign-off.
> Otherwise:
> Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com>
>
> Maybe you or Christophe could resubmit another proper fix for the original issue.
I'm really sorry about that. This was largely my fault.
I still don't understand how commit ba403242615c caused a problem.
It sounds like in the original code ipctl->input_sel_base was released
somehow? I do a `git grep input_sel_base` and it doesn't show anything.
What am I missing?
regards,
dan carpenter
next prev parent reply other threads:[~2020-06-08 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 10:00 [PATCH] Revert "pinctrl: freescale: imx: Use 'devm_of_iomap()' to avoid a resource leak in case of error in 'imx_pinctrl_probe()'" haibo.chen
2020-06-08 10:16 ` BOUGH CHEN
2020-06-08 12:10 ` Fabio Estevam
2020-06-08 14:06 ` Aisheng Dong
2020-06-08 14:44 ` Dan Carpenter [this message]
2020-06-09 2:59 ` BOUGH CHEN
2020-06-08 14:48 ` Dan Carpenter
2020-06-09 3:22 ` Aisheng Dong
2020-06-09 9:24 ` Dan Carpenter
2020-06-09 10:46 ` [PATCH] lib: devres: add a comment about the devm_of_iomap() function Dan Carpenter
2020-06-09 14:20 ` Arnd Bergmann
2020-06-09 20:01 ` [PATCH] Revert "pinctrl: freescale: imx: Use 'devm_of_iomap()' to avoid a resource leak in case of error in 'imx_pinctrl_probe()'" Marion & Christophe JAILLET
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=20200608144431.GS22511@kadam \
--to=dan.carpenter@oracle.com \
--cc=aisheng.dong@nxp.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).