From: Baruch Siach <baruch@tkos.co.il>
To: Marc Gauthier <marc@cadence.com>
Cc: David Cohen <david.a.cohen@linux.intel.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>
Subject: Re: [Linux-Xtensa] [PATCH v3] gpio: driver for Xtensa GPIO32
Date: Mon, 16 Dec 2013 08:40:29 +0200 [thread overview]
Message-ID: <20131216064029.GC3807@tarshish> (raw)
In-Reply-To: <8CA974F497CA064FA9926E10ABCC061F047C83D8C3@MAILSJ4.global.cadence.com>
Hi Marc,
On Sun, Dec 15, 2013 at 10:11:06PM -0800, Marc Gauthier wrote:
> Baruch Siach wrote:
> [...]
> > We could depend on, say HAVE_XTENSA_GPIO32, and select it
> > from arch/xtensa/Kconfig for the appropriate xtensa variants.
> > The problem is that no current mainline xtensa variant
> > supports GPIO32. So, at some future point one of those who are
> > looking for unreferenced Kconfig symbols will just remove the
> > whole driver.
>
> The Diamond 233L core has GPIO32.
> The GPIO32 option is not mentioned in the variant core.h, however.
Thanks, your are right. The fsf and 232c variants also support GPIO32
according to their tie.h. I should have used grep earlier. A patch is on the
way.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2013-12-16 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 9:18 [PATCH v3] gpio: driver for Xtensa GPIO32 Baruch Siach
2013-12-12 13:35 ` Linus Walleij
2013-12-12 18:15 ` David Cohen
2013-12-12 18:24 ` Baruch Siach
2013-12-12 19:23 ` David Cohen
2013-12-16 5:50 ` Baruch Siach
2013-12-16 6:11 ` [Linux-Xtensa] " Marc Gauthier
2013-12-16 6:40 ` Baruch Siach [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=20131216064029.GC3807@tarshish \
--to=baruch@tkos.co.il \
--cc=david.a.cohen@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=marc@cadence.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