From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: David Cohen <david.a.cohen@linux.intel.com>
Cc: Alex Courbot <acourbot@nvidia.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v1 3/3] gpiolib: append SFI helpers for GPIO API
Date: Tue, 10 Dec 2013 17:31:25 +0200 [thread overview]
Message-ID: <1386689485.1871.171.camel@smile> (raw)
In-Reply-To: <52A7318F.6040901@linux.intel.com>
On Tue, 2013-12-10 at 07:21 -0800, David Cohen wrote:
> Hi,
>
> [snip]
>
> >> I don't know anything about SFI GPIOs, how they are defined, where their
> >> name comes from, and how they are used so my vision may be incomplete.
> >> But AFAICT it all comes down to one of these two scenarios:
> >>
> >> 1) SFI GPIOs are only used in platform code -> using their pin name is
> >> ok, device argument should be assumed to be NULL for their matching
> > Let's stick to this.
> >
> >> 2) SFI GPIOs are also consumed by device drivers -> you need a way to
> >> match a (device, con_id) pair to your SFI GPIOs so they can be matched
> >> exactly and through the names drivers will request.
> > Mostly unlikely we go this way. It would mean we don't need SFI at all.
>
> I'm currently upstreaming Intel-MID's SFI users. This is a forbidden
> situation which I'd change before submit the patch.
I'm sorry I didn't get this. You mean we have to have another mapping,
or you agree with system-global GPIOs in SFI case?
>
> Br, David Cohen
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2013-12-10 15:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 16:36 [PATCH v1 0/3] Andy Shevchenko
2013-12-05 16:36 ` [PATCH v1 1/3] SFI: fix compiler warnings Andy Shevchenko
2013-12-05 22:48 ` David Cohen
2013-12-09 8:52 ` Andy Shevchenko
2013-12-05 16:36 ` [PATCH v1 2/3] SFI: store GPIO table and export lookup function Andy Shevchenko
2013-12-05 23:07 ` David Cohen
2013-12-09 9:59 ` Andy Shevchenko
2013-12-06 1:51 ` Alex Courbot
2013-12-09 9:23 ` Andy Shevchenko
2013-12-05 16:36 ` [PATCH v1 3/3] gpiolib: append SFI helpers for GPIO API Andy Shevchenko
2013-12-05 23:20 ` David Cohen
2013-12-09 10:13 ` Andy Shevchenko
2013-12-06 1:52 ` Alex Courbot
2013-12-09 10:11 ` Andy Shevchenko
2013-12-10 3:00 ` Alex Courbot
2013-12-10 13:15 ` Andy Shevchenko
2013-12-10 15:21 ` David Cohen
2013-12-10 15:31 ` Andy Shevchenko [this message]
2013-12-11 2:47 ` Alex Courbot
2013-12-12 0:45 ` David Cohen
2013-12-12 1:46 ` Alex Courbot
2013-12-05 22:46 ` [PATCH v1 0/3] David Cohen
2013-12-09 9:19 ` Andy Shevchenko
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=1386689485.1871.171.camel@smile \
--to=andriy.shevchenko@linux.intel.com \
--cc=acourbot@nvidia.com \
--cc=david.a.cohen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=sathyanarayanan.kuppuswamy@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