All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Haojian Zhuang <haojian.zhuang@linaro.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Nishanth Menon <nm@ti.com>,
	linux-gpio@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] pinctrl: single: Remove invalid message
Date: Sun, 17 Dec 2017 08:07:40 -0800	[thread overview]
Message-ID: <20171217160740.GJ3875@atomide.com> (raw)
In-Reply-To: <c51cd2c7-3d36-3dc5-11f8-06c162ca3639@linaro.org>

* Haojian Zhuang <haojian.zhuang@linaro.org> [171217 05:43]:
> On 2017/12/15 0:51, Tony Lindgren wrote:
> > Pinctrl single should just show how many pins were found, the physical
> > address is already in the dev information. So let's remove the wrong
> > information that claims to show the physical address but really prints
> > a virtual address that is now hashed.
> > 
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
> > ---
> >   drivers/pinctrl/pinctrl-single.c | 3 +--
> >   1 file changed, 1 insertion(+), 2 deletions(-)
> > 
> > diff --git a/drivers/pinctrl/pinctrl-single.c b/drivers/pinctrl/pinctrl-single.c
> > --- a/drivers/pinctrl/pinctrl-single.c
> > +++ b/drivers/pinctrl/pinctrl-single.c
> > @@ -1774,8 +1774,7 @@ static int pcs_probe(struct platform_device *pdev)
> >   			dev_warn(pcs->dev, "initialized with no interrupts\n");
> >   	}
> > -	dev_info(pcs->dev, "%i pins at pa %p size %u\n",
> > -		 pcs->desc.npins, pcs->base, pcs->size);
> > +	dev_info(pcs->dev, "%i pins, size %u\n", pcs->desc.npins, pcs->size);
> >   	return pinctrl_enable(pcs->pctl);
> > 
> Hi Tony,
> 
> If there's only one pinctrl region in SoC, it's fine to remove the pa part.
> But there're always multiple pinctrl regions in Hisilicon SoCs. It causes
> multiple pinctrl register bases are used. Will it cause debug information
> harder to read when pa parts are removed?

I doubt as for years now we've been printing out the va instead of pa
and so far nobody noticed :) We still get the real device pa with the
dev_info, size and number of pins.

Regards,

Tony

  reply	other threads:[~2017-12-17 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 16:51 [PATCH] pinctrl: single: Remove invalid message Tony Lindgren
2017-12-17  5:25 ` Haojian Zhuang
2017-12-17 16:07   ` Tony Lindgren [this message]
2017-12-18  0:21     ` Haojian Zhuang
2017-12-20 11:39 ` Linus Walleij

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=20171217160740.GJ3875@atomide.com \
    --to=tony@atomide.com \
    --cc=grygorii.strashko@ti.com \
    --cc=haojian.zhuang@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.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.