* [PATCH] pinctrl: single: Remove invalid message
@ 2017-12-14 16:51 Tony Lindgren
2017-12-17 5:25 ` Haojian Zhuang
2017-12-20 11:39 ` Linus Walleij
0 siblings, 2 replies; 5+ messages in thread
From: Tony Lindgren @ 2017-12-14 16:51 UTC (permalink / raw)
To: Linus Walleij
Cc: Haojian Zhuang, Grygorii Strashko, Nishanth Menon, linux-gpio,
linux-omap
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);
--
2.15.0
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] pinctrl: single: Remove invalid message
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
2017-12-20 11:39 ` Linus Walleij
1 sibling, 1 reply; 5+ messages in thread
From: Haojian Zhuang @ 2017-12-17 5:25 UTC (permalink / raw)
To: Tony Lindgren, Linus Walleij
Cc: Grygorii Strashko, Nishanth Menon, linux-gpio, linux-omap
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?
Best Regards
Haojian
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] pinctrl: single: Remove invalid message
2017-12-17 5:25 ` Haojian Zhuang
@ 2017-12-17 16:07 ` Tony Lindgren
2017-12-18 0:21 ` Haojian Zhuang
0 siblings, 1 reply; 5+ messages in thread
From: Tony Lindgren @ 2017-12-17 16:07 UTC (permalink / raw)
To: Haojian Zhuang
Cc: Linus Walleij, Grygorii Strashko, Nishanth Menon, linux-gpio,
linux-omap
* 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] pinctrl: single: Remove invalid message
2017-12-17 16:07 ` Tony Lindgren
@ 2017-12-18 0:21 ` Haojian Zhuang
0 siblings, 0 replies; 5+ messages in thread
From: Haojian Zhuang @ 2017-12-18 0:21 UTC (permalink / raw)
To: Tony Lindgren
Cc: Linus Walleij, Grygorii Strashko, Nishanth Menon, linux-gpio,
linux-omap
On 2017/12/18 0:07, Tony Lindgren wrote:
> * 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.
>
OK
Regards
Haojian
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] pinctrl: single: Remove invalid message
2017-12-14 16:51 [PATCH] pinctrl: single: Remove invalid message Tony Lindgren
2017-12-17 5:25 ` Haojian Zhuang
@ 2017-12-20 11:39 ` Linus Walleij
1 sibling, 0 replies; 5+ messages in thread
From: Linus Walleij @ 2017-12-20 11:39 UTC (permalink / raw)
To: Tony Lindgren
Cc: Haojian Zhuang, Grygorii Strashko, Nishanth Menon, linux-gpio,
Linux-OMAP
On Thu, Dec 14, 2017 at 5:51 PM, Tony Lindgren <tony@atomide.com> 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>
Patch applied.
Yours,
Linus Walleij
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-12-20 11:39 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2017-12-18 0:21 ` Haojian Zhuang
2017-12-20 11:39 ` Linus Walleij
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).