From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "zhuchangchun@cvte.com" <zhuchangchun@cvte.com>
Cc: "andriy.shevchenko" <andriy.shevchenko@linux.intel.com>,
"linus.walleij" <linus.walleij@linaro.org>,
linux-gpio <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
hendychu <hendychu@aliyun.com>
Subject: Re: Re: [PATCH] pinctrl: intel: Implements gpio free function
Date: Thu, 21 Mar 2019 14:36:37 +0200 [thread overview]
Message-ID: <20190321123637.GJ3622@lahna.fi.intel.com> (raw)
In-Reply-To: <2019032120213955866649@cvte.com>
On Thu, Mar 21, 2019 at 08:22:40PM +0800, zhuchangchun@cvte.com wrote:
> On Thu, Mar 21, 2019 at 07:20:56PM +0800, zhuchangchun@cvte.com wrote:
> > After you unexport GPIO it can go back to any previous mode it
> was. If
> > you need to use it as GPIO then why unexport it in the first
> place?
> > --> because we need use the GPIO for device reset, we want to
> recover
> > the GPIO value after reset done.If we don't unexport it, then
> reboot
> > the
> > intel SOC(not power off), the GPIO's value will stay until the
> GPIO be
> > reinit.
> > I tested the GPIO signal with oscilloscope, if power off the SOC,
> > then
> > power on, the GPIO value can recover its original value. This will
> > infruence
> > the peripheral device working condition.
>
> If I understand correctly you have some peripheral connected to Intel
> based board and one GPIO is used to reset the peripheral.
>
> You say it works fine if you power cycle the board but it does not when
> you issue 'reboot' command. Did I understood the problem correctly?
>
> --> Yes , so I add the -> free callback, it fixes the problem.
OK, so you then write 1 to the sysfs to assert reset, right? And in your
patch you change the mode to input effectively deasserting the reset.
Why not simply do following instead of unexport?
# echo 0 > /sys/class/gpio/gpioXX/value
or even
# echo 0 > /sys/class/gpio/gpioXX/value
# echo in > /sys/class/gpio/gpioXX/direction
Am I missing something?
next prev parent reply other threads:[~2019-03-21 12:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 2:35 [PATCH] pinctrl: intel: Implements gpio free function zhuchangchun
2019-03-21 8:44 ` Mika Westerberg
2019-03-21 9:23 ` Andy Shevchenko
2019-03-22 18:32 ` Enrico Weigelt, metux IT consult
2019-03-22 19:06 ` Andy Shevchenko
2019-03-25 9:36 ` Enrico Weigelt, metux IT consult
2019-03-25 11:45 ` Andy Shevchenko
2019-04-03 4:13 ` Linus Walleij
2019-04-04 10:51 ` Enrico Weigelt, metux IT consult
2019-04-04 11:52 ` Andy Shevchenko
2019-04-04 16:03 ` Linus Walleij
[not found] ` <2019032119195575582546@cvte.com>
2019-03-21 12:03 ` Mika Westerberg
[not found] ` <2019032120213955866649@cvte.com>
2019-03-21 12:36 ` Mika Westerberg [this message]
[not found] ` <2019032121342663125658@cvte.com>
2019-03-21 13:56 ` Mika Westerberg
[not found] ` <2019032211131426883268@cvte.com>
2019-03-22 10:42 ` Mika Westerberg
[not found] ` <2019032314505202825175@cvte.com>
2019-03-23 16:48 ` andriy.shevchenko
[not found] ` <2019032517511048990383@cvte.com>
2019-03-25 11:48 ` andriy.shevchenko
2019-03-22 18:35 ` Enrico Weigelt, metux IT consult
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=20190321123637.GJ3622@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hendychu@aliyun.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhuchangchun@cvte.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