From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Chris Chiu <chiu@endlessm.com>,
heikki.krogerus@linux.intel.com, drake@endlessm.com,
linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@endlessm.com
Subject: Re: [PATCH] pinctrl:intel: Retain HOSTSW_OWN for requested gpio pin
Date: Mon, 8 Apr 2019 13:09:47 +0300 [thread overview]
Message-ID: <20190408100947.GI9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190408074106.GC3622@lahna.fi.intel.com>
On Mon, Apr 08, 2019 at 10:41:06AM +0300, Mika Westerberg wrote:
> On Mon, Apr 08, 2019 at 12:21:03PM +0800, Chris Chiu wrote:
> > +static void
static u32
(see below why)
> > +intel_gpio_update_pad_mode(void __iomem *hostown, u32 mask, u32 value)
> > +{
> > + u32 curr = readl(hostown);
> > + u32 updated = (curr & ~mask) | (value & mask);
>
> I think here we should first complain if the expected ownership is not
> correct. Warning or info level probably enough.
It is easy to achieve, something like
if ((value ^ saved) & requeted)
dev_warn(...);
See also below.
(I had mentioned this earlier)
> > + return writel(updated, hostown);
writel() is a void function, this is wrong. We need to return curr instead to
make above working to issue a warning message.
> Also if the pin is not requested and not changed we should not touch the
> register.
I don't think it brings any value here, if mask is 0 we will write back the
same value we read.
> Otherwise this looks good to me.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2019-04-08 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 4:21 [PATCH] pinctrl:intel: Retain HOSTSW_OWN for requested gpio pin Chris Chiu
2019-04-08 7:41 ` Mika Westerberg
2019-04-08 10:09 ` Andy Shevchenko [this message]
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=20190408100947.GI9224@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=chiu@endlessm.com \
--cc=drake@endlessm.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=mika.westerberg@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox