All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew Jeffery" <andrew@aj.id.au>
To: www <ouyangxuan10@163.com>
Cc: openbmc@lists.ozlabs.org, "Ryan Chen" <ryan_chen@aspeedtech.com>,
	"Bills, Jason M" <jason.m.bills@linux.intel.com>
Subject: Re: [openbmc-kernel]: How to make pinctrl not affect pass-through function?
Date: Mon, 25 Nov 2019 08:40:37 +1030	[thread overview]
Message-ID: <eed376e8-445f-4a2f-8184-de2c3800f953@www.fastmail.com> (raw)
In-Reply-To: <5d3da051.585b.16e91e043b7.Coremail.ouyangxuan10@163.com>



On Fri, 22 Nov 2019, at 17:20, www wrote:
> Dear Andrew,
> 
> Thank you. I got it.
> Pass-through function is only a small and special part of GPIO 
> function. 
> If the entire pinctrl and ****/sys/class/gpio **** are changed due to 
> this function, I am not sure whether it is appropriate.
> 

I'm not suggesting you change pinctrl at all, so I'm not sure where you
got the idea that we'd need something so drastic as changing entire
subsystems. What I'm proposing should boil down to a new
configuration option to pass through the gpio userspace interface,
then adding appropriate support to the GPIO driver. We might need
to tinker with pinctrl a little to get the interfaces right, but nothing more.

Andrew

  reply	other threads:[~2019-11-24 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1b4dacbd.8278.16e6e6c2234.Coremail.ouyangxuan10@163.com>
     [not found] ` <a06a7845-cf16-4e37-8674-acd0950d6245@www.fastmail.com>
     [not found]   ` <42def251.79a4.16e87d7a3a7.Coremail.ouyangxuan10@163.com>
2019-11-22  0:31     ` [openbmc-kernel]: How to make pinctrl not affect pass-through function? Andrew Jeffery
2019-11-22  4:25       ` www
2019-11-22  6:32         ` Andrew Jeffery
2019-11-22  6:50           ` www
2019-11-24 22:10             ` Andrew Jeffery [this message]
2019-11-26  1:00               ` www
2019-11-27 23:17                 ` Andrew Jeffery

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=eed376e8-445f-4a2f-8184-de2c3800f953@www.fastmail.com \
    --to=andrew@aj.id.au \
    --cc=jason.m.bills@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ouyangxuan10@163.com \
    --cc=ryan_chen@aspeedtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.