linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "andriy.shevchenko" <andriy.shevchenko@linux.intel.com>
To: "zhuchangchun@cvte.com" <zhuchangchun@cvte.com>
Cc: Mika Westerberg <mika.westerberg@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: Mon, 25 Mar 2019 13:48:12 +0200	[thread overview]
Message-ID: <20190325114812.GO9224@smile.fi.intel.com> (raw)
In-Reply-To: <2019032517511048990383@cvte.com>

On Mon, Mar 25, 2019 at 05:52:10PM +0800, zhuchangchun@cvte.com wrote:
> On Sat, Mar 23, 2019 at 02:51:52PM +0800, zhuchangchun@cvte.com wrote:
> > On Fri, Mar 22, 2019 at 11:14:14AM +0800, zhuchangchun@cvte.com wrote:
>  
> > >    From above,you can kown when you export a GPIO ,it will do request,
> > >
> > >    and there will set TX and RX register at the time same time.
> > >
> > >    when you try to set direction in and set value, TX register value can
> > >    roll back
> > >
> > >    the value,but RX register was not set, so who will set RX value back??
> > 
> > I think you are looking at some older code. There is now function
> > __intel_gpio_set_direction() that is supposed to set both buffers
> > depending on the direction. It was introduced with commit 17fab473693e
> > ("pinctrl: intel: Set pin direction properly").
> >
> >
> > --> Yes ,I see the latest master branch, the __intel_gpio_set_direction will
> > set RX and TX, but I still think we need to implement free function,cause
> > it will help many other engineers,especailly for some manufactories use some
> > module,and this modules embeded its own driver but not can be modified,
> > if they want use the gpio control the module, they may meet the same problem.
>  
> What problem?
> Is it reproducible on latest vanilla kernel?
> 
> --> Not yet, I mean if someone use export GPIO ,then forget to set direction in, 
> and then set GPIO unexport directly, the GPIO buffer status may influence 
> the device work flow.

If you would like to return pin back to the previous state, it should be done
in generic way in the pin control subsystem.

Since there is no problem, nothing to fix then.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2019-03-25 11:48 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
     [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 [this message]
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=20190325114812.GO9224@smile.fi.intel.com \
    --to=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=mika.westerberg@linux.intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).