From: Florian Vaussard <florian.vaussard@epfl.ch>
To: Tony Lindgren <tony@atomide.com>
Cc: Afzal Mohammed <afzal@ti.com>,
paul@pwsan.com, jon-hunter@ti.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 0/3] GPMC driver conversion
Date: Mon, 10 Sep 2012 10:30:14 +0200 [thread overview]
Message-ID: <504DA516.1020405@epfl.ch> (raw)
In-Reply-To: <20120907221034.GP1303@atomide.com>
Hello,
Le 08/09/2012 00:10, Tony Lindgren a écrit :
> * Afzal Mohammed <afzal@ti.com> [120905 05:37]:
>> Hi,
>>
>> Basic gpmc driver conversion series. Driver that is now created out of
>> gpmc code is a simple one, it handles tasks that were earlier executed
>> by gpmc_init. Now instead of relying on cpu_is_* checks, it obtains
>> resources and clk handle in the standard Linux way. The existing gpmc
>> interface works as was without this series.
>>
>> HWMOD patch also has been brought into this series back with v7 series
>>
>> As this creates only a basic driver, further gpmc driver work can be
>> based over this, while having a driver first in place.
>>
>> This series is based on l-o/testing-cleanup as on 5-Sep-12,
>> i.e. over commit,
>>
>> e3a5c14 ARM: OMAP1: Move SoC specific headers from plat to mach for omap1
>>
>> per Tony's suggestion.
>>
>> It is available
>> @git://gitorious.org/x0148406-public/linux-kernel.git gpmc-drv-v8
> Great, this all looks good to me. I suggest that on top of this
> we add minimal devicetree binding that does not even attempt to
> deal with the timings yet.
>
> Then once the minimal devicetree binding is in place, we can
> call the current GPMC timing functions using the compatible flags
> and auxdata in the gpmc.c driver.
>
> That way we get all the legacy boards booting with GPMC support
> for smsc911x etc, and can even remove some less used board-*.c
> files.
This would be great. If you happen to have DT bindings for GPMC,
I would be happy to test them with my Overo board, as well as
with my CAN chips on a custom board.
Regards,
Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: florian.vaussard@epfl.ch (Florian Vaussard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/3] GPMC driver conversion
Date: Mon, 10 Sep 2012 10:30:14 +0200 [thread overview]
Message-ID: <504DA516.1020405@epfl.ch> (raw)
In-Reply-To: <20120907221034.GP1303@atomide.com>
Hello,
Le 08/09/2012 00:10, Tony Lindgren a ?crit :
> * Afzal Mohammed <afzal@ti.com> [120905 05:37]:
>> Hi,
>>
>> Basic gpmc driver conversion series. Driver that is now created out of
>> gpmc code is a simple one, it handles tasks that were earlier executed
>> by gpmc_init. Now instead of relying on cpu_is_* checks, it obtains
>> resources and clk handle in the standard Linux way. The existing gpmc
>> interface works as was without this series.
>>
>> HWMOD patch also has been brought into this series back with v7 series
>>
>> As this creates only a basic driver, further gpmc driver work can be
>> based over this, while having a driver first in place.
>>
>> This series is based on l-o/testing-cleanup as on 5-Sep-12,
>> i.e. over commit,
>>
>> e3a5c14 ARM: OMAP1: Move SoC specific headers from plat to mach for omap1
>>
>> per Tony's suggestion.
>>
>> It is available
>> @git://gitorious.org/x0148406-public/linux-kernel.git gpmc-drv-v8
> Great, this all looks good to me. I suggest that on top of this
> we add minimal devicetree binding that does not even attempt to
> deal with the timings yet.
>
> Then once the minimal devicetree binding is in place, we can
> call the current GPMC timing functions using the compatible flags
> and auxdata in the gpmc.c driver.
>
> That way we get all the legacy boards booting with GPMC support
> for smsc911x etc, and can even remove some less used board-*.c
> files.
This would be great. If you happen to have DT bindings for GPMC,
I would be happy to test them with my Overo board, as well as
with my CAN chips on a custom board.
Regards,
Florian
next prev parent reply other threads:[~2012-09-10 8:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 12:36 [PATCH v8 0/3] GPMC driver conversion Afzal Mohammed
2012-09-05 12:36 ` Afzal Mohammed
2012-09-05 12:37 ` [PATCH v8 1/3] ARM: OMAP2/3: hwmod data: add gpmc Afzal Mohammed
2012-09-05 12:37 ` Afzal Mohammed
2012-09-05 19:47 ` Jon Hunter
2012-09-05 19:47 ` Jon Hunter
2012-09-05 19:47 ` Jon Hunter
2012-09-05 19:47 ` Jon Hunter
2012-09-05 23:27 ` Tony Lindgren
2012-09-05 23:27 ` Tony Lindgren
2012-09-05 12:37 ` [PATCH v8 2/3] ARM: OMAP2+: gpmc: Adapt to HWMOD Afzal Mohammed
2012-09-05 12:37 ` Afzal Mohammed
2012-09-05 19:55 ` Jon Hunter
2012-09-05 19:55 ` Jon Hunter
2012-09-11 10:16 ` Mohammed, Afzal
2012-09-11 10:16 ` Mohammed, Afzal
2012-09-05 12:37 ` [PATCH v8 3/3] ARM: OMAP2+: gpmc: minimal driver support Afzal Mohammed
2012-09-05 12:37 ` Afzal Mohammed
2012-09-05 20:41 ` Jon Hunter
2012-09-05 20:41 ` Jon Hunter
2012-09-07 22:10 ` [PATCH v8 0/3] GPMC driver conversion Tony Lindgren
2012-09-07 22:10 ` Tony Lindgren
2012-09-10 8:30 ` Florian Vaussard [this message]
2012-09-10 8:30 ` Florian Vaussard
2012-09-11 10:53 ` Mohammed, Afzal
2012-09-11 10:53 ` Mohammed, Afzal
2012-09-11 16:31 ` Tony Lindgren
2012-09-11 16:31 ` Tony Lindgren
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=504DA516.1020405@epfl.ch \
--to=florian.vaussard@epfl.ch \
--cc=afzal@ti.com \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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.