From: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Fenglin Wu <fenglinw-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Kiran Gunda <kgunda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Abhijeet Dharmapurikar
<adharmap-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
David Collins <collinsd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-msm-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V2] spmi: pmic-arb: Enforce the ownership check optionally
Date: Mon, 28 Aug 2017 22:47:20 +0800 [thread overview]
Message-ID: <20170828144718.GD3525@dragon> (raw)
In-Reply-To: <93b8935e-061f-ba3a-ee36-8ffbc8230bcc-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
On Mon, Aug 28, 2017 at 04:27:54PM +0800, Fenglin Wu wrote:
> On 8/22/2017 4:55 PM, Shawn Guo wrote:
> >On Mon, Aug 21, 2017 at 04:18:58PM -0700, Stephen Boyd wrote:
> >>On 08/18/2017 08:28 AM, Kiran Gunda wrote:
> >>>The peripheral ownership check is not necessary on single master
> >>>platforms. Hence, enforce the peripheral ownership check optionally.
> >>>
> >>>Signed-off-by: Kiran Gunda <kgunda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
> >>>Tested-by: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> >>>---
> >>
> >>This sounds like a band-aid. Isn't the gpio driver going to keep probing
> >>all the pins that are not supposed to be accessed due to security
> >>constraints? What exactly is failing in the gpio case?
> >
> >There is a platform_irq_count() call in pinctrl-spmi-gpio probe
> >function. Due to the owner check in spmi-pmic-arb IRQ domain
> >qpnpint_irq_domain_dt_translate() function, the call will return irq
> >number as zero and cause pmic_gpio_probe() fail with -EINVAL error.
> >
> >[ 1.608516] [<ffff00000860e51c>] qpnpint_irq_domain_dt_translate+0x168/0x194
> >[ 1.613557] [<ffff000008117040>] irq_create_fwspec_mapping+0x17c/0x2d8
> >[ 1.620672] [<ffff000008117200>] irq_create_of_mapping+0x64/0x74
> >[ 1.627008] [<ffff0000087b4fac>] of_irq_get+0x54/0x64
> >[ 1.633169] [<ffff00000856b824>] platform_get_irq+0x20/0x150
> >[ 1.638117] [<ffff00000856b97c>] platform_irq_count+0x28/0x44
> >[ 1.643850] [<ffff0000083cf12c>] pmic_gpio_probe+0x50/0x544
> >
> >ShawnI just realize this patch is trying to fix this issue from spmi driver
> level. Actually I had submitted a change in spmi-gpio driver to fix
> this by ignoring the GPIOs which the IRQ is not owned by APPS
> processor. The maintainer hasn't reviewed it yet:
> https://www.spinics.net/lists/linux-arm-msm/msg28849.html
> I am trying to understand if my patch is still needed if Kiran's patch
> get merged, the intention for my patch originally is for fixing the same
> probe failure, but it could hide the GPIOs which are not allowed to use
> from the pinctrl driver level. Please help to suggest.
As I just replied to Greg, this patch is obsolete and replaced by 'spmi:
pmic-arb: Move the ownership check to irq_chip callback' [1].
With the patch applied, we can get rid of the spmi-gpio probe failure.
So from the point of fixing the issue, your patch is not needed. But I
would like to discuss your patch a bit, and will reply to your patch
with my comments.
Shawn
[1] https://lkml.org/lkml/2017/8/23/325
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-28 14:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 15:28 [PATCH V2] spmi: pmic-arb: Enforce the ownership check optionally Kiran Gunda
[not found] ` <1503070110-15018-1-git-send-email-kgunda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-08-21 23:18 ` Stephen Boyd
2017-08-22 8:55 ` Shawn Guo
2017-08-22 20:31 ` Stephen Boyd
2017-08-23 12:57 ` kgunda
2017-08-24 12:18 ` Shawn Guo
2017-08-24 18:37 ` Stephen Boyd
2017-08-25 7:47 ` Shawn Guo
2017-08-25 23:18 ` Stephen Boyd
[not found] ` <20170825231818.GP21656-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-08-26 3:46 ` Shawn Guo
2017-08-30 21:02 ` Stephen Boyd
2017-08-31 8:37 ` Shawn Guo
2017-09-01 1:30 ` Stephen Boyd
[not found] ` <20170901013048.GK21656-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-09-01 3:00 ` Shawn Guo
2017-08-28 8:27 ` Fenglin Wu
[not found] ` <93b8935e-061f-ba3a-ee36-8ffbc8230bcc-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-08-28 14:47 ` Shawn Guo [this message]
2017-08-22 9:01 ` Shawn Guo
2017-08-28 11:53 ` Greg KH
2017-08-28 14:08 ` Shawn Guo
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=20170828144718.GD3525@dragon \
--to=shawnguo-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=adharmap-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=collinsd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=fenglinw-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=kgunda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=linux-arm-msm-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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).