From: "Richard Röjfors" <richard.rojfors.ext@mocean-labs.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: Added timbgpio
Date: Thu, 04 Jun 2009 14:53:04 +0200 [thread overview]
Message-ID: <4A27C3B0.5000605@mocean-labs.com> (raw)
In-Reply-To: <20090604005119.6b4f80e0.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 03 Jun 2009 10:07:48 +0200 Richard R____jfors <richard.rojfors.ext@mocean-labs.com> wrote:
>
>> Supplied is a GPIO driver for the Timberdale FPGA found on the
>> Intel Atom board Russellville.
>>
>> ...
>>
>> +EXPORT_SYMBOL(timbgpio_gpio_flnk_lvl_ctrl);
>> +EXPORT_SYMBOL(timbgpio_gpio_int_ctrl);
>> +EXPORT_SYMBOL(timbgpio_gpio_lvl_ctrl);
>> +EXPORT_SYMBOL(timbgpio_gpio_int_clr);
>
> Why all these module exports?
Internal stuff, I will remove it.
>> ...
>>
>> +config GPIO_TIMBERDALE
>> + tristate "Support for timberdale GPIO"
>> + depends on MFD_TIMBERDALE && GPIOLIB
>> + ---help---
>> + Add support for GPIO usage of some pins of the timberdale FPGA.
>> +
>
> I cannot find anything which sets MFD_TIMBERDALE anywhere?
Sorry, I realize I have to come back with a bigger patch set.
Timberdale is the MFD driver for the FPGA which among other expose this GPIO device.
This patch set will depend on patches in i2c-ocores and xilinx_spi which I have posted
earlier on the corresponding mailinglists.
Shall I repost those driver changes within this patch set, or can I leave them out?
--Richard
next prev parent reply other threads:[~2009-06-04 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 8:07 [PATCH] gpio: Added timbgpio Richard Röjfors
2009-06-04 7:51 ` Andrew Morton
2009-06-04 12:53 ` Richard Röjfors [this message]
2009-06-04 18:53 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2009-10-06 14:16 Richard Röjfors
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=4A27C3B0.5000605@mocean-labs.com \
--to=richard.rojfors.ext@mocean-labs.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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).