mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] gpio: Add designware gpio controller support
Date: Thu, 17 Oct 2013 10:24:11 +0200	[thread overview]
Message-ID: <525F9EAB.50104@gmail.com> (raw)
In-Reply-To: <20131017080434.GL14042@pengutronix.de>

On 10/17/2013 10:04 AM, Steffen Trumtrar wrote:
> On Mon, Sep 09, 2013 at 06:28:48PM +0200, Sebastian Hesselbarth wrote:
>> On 09/09/13 16:54, Sascha Hauer wrote:
>>> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>>> ---
>>>   drivers/gpio/Kconfig   |   6 ++
>>>   drivers/gpio/Makefile  |   1 +
>>>   drivers/gpio/gpio-dw.c | 151 +++++++++++++++++++++++++++++++++++++++++++++++++
>>>   3 files changed, 158 insertions(+)
>>>   create mode 100644 drivers/gpio/gpio-dw.c
>>>
>>> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
>>> index d5ac532..18d3135 100644
>>> --- a/drivers/gpio/Kconfig
>>> +++ b/drivers/gpio/Kconfig
>>> @@ -54,6 +54,12 @@ config GPIO_TEGRA
>>>   	help
>>>   	  Say yes here to include the driver for the GPIO controller found on the
>>>   	  Tegra line of SoCs.
>>> +
>>> +config GPIO_DESIGNWARE
>>> +	tristate "Synopsys DesignWare GPIO driver"
>>
>> Sascha,
>>
>> I know DW's GPIO is also used on Armada 1500 which I currently work on.
>> Precisely, the IP is named dw-apb-gpio. Maybe the above should also
>> reflect APB.
>>
>> [...]
>>
>> Please add "snps,dw-apb-gpio", that's what the linux driver
>> will look for if make to pick it up for Armada 1500.
>>
>
> Are you talking about the 'old' linux driver that was posted sometime around
> January 2012 or are you working on your own?

Cannot recall the actual version or time posted. I didn't find time to
work on a linux driver for dw-apb-gpio, yet. My idea was to pick up the
latest driver posted plus make it more general. IIRC the one posted was
very limited to socfpga.

> Do you have a working pre-release version somewhere?

Sorry, nothing started, yet.

Are you going to work on it? If so, feel free to involve me in patches
and reviews.

Sebastian


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-10-17  8:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 14:54 Sascha Hauer
2013-09-09 16:28 ` Sebastian Hesselbarth
2013-09-10  7:48   ` Sascha Hauer
2013-09-10  8:56     ` Sebastian Hesselbarth
2013-09-11  6:35       ` Sascha Hauer
2013-10-17  8:04   ` Steffen Trumtrar
2013-10-17  8:24     ` Sebastian Hesselbarth [this message]
2013-10-17  8:38       ` Steffen Trumtrar

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=525F9EAB.50104@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.trumtrar@pengutronix.de \
    /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