From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: shmobile: use common platform header for HPB-DMAC
Date: Fri, 19 Jul 2013 02:02:34 +0400 [thread overview]
Message-ID: <51E865FA.9000706@cogentembedded.com> (raw)
In-Reply-To: <CANqRtoTCaJfbECSpX7nMZoV8SPeQqs-xrJQ0-+-smA+bx3QG=w@mail.gmail.com>
Hello.
On 07/02/2013 08:59 AM, Magnus Damm wrote:
>> From: Max Filippov <max.filippov@cogentembedded.com>
>> Use previously empty <mach/dma.h> to declare HPB-DMA slave IDs.
>> Signed-off-by: Max Filippov <max.filippov@cogentembedded.com>
>> [Sergei: changed the guard macro name, fixed comment, extended copyright.]
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> ---
>> arch/arm/mach-shmobile/include/mach/dma.h | 25 ++++++++++++++++++++++++-
>> 1 file changed, 24 insertions(+), 1 deletion(-)
> Thanks for your patch. Can you please explain the reason why you put
> this shared information under mach/?
I'm afraid that's more a question to the original author, Phil Edworthy.
He put this stuff into <mach/hpb-dmae.h>.
> From my point of view we should really have as few special things as
> possible under mach/. Starting to share DMA stuff here looks special.
> I would like mach-shmobile to be as standard as possible (basically
> only ARM code in the future), and in the case we have I/O devices or
> other IOMMUs or DMA controllers then we should use include/linux or
> that recently added platform data directory if needed. We need to make
> sure that our headers stay compatible with multiplatform support.
> I realize you may want to share this header between multiple SoCs, but
> I really want to avoid creating local common code under arch/arm/ that
> has nothing to do with ARM. Also, this is IMO a total non-issue,
> instead of merging code and making back porting more difficult for any
> particular SoC, then how about spending effort on the ling term
> instead, like DMA DT?
> So my recommendation is to keep this information together with each
> SoC. And also work on DT. In between have a coffee or work on DT, but
> please do not spend time on merging short term per-SoC information and
> making back porting more difficult.
OK. DT would be a next step I guess.
> Thanks,
> / magnus
WBR, Sergei
next prev parent reply other threads:[~2013-07-18 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 22:43 [PATCH 0/3] R8A7778/BOCK-W: HPB-DMAC support for SDHI0 Sergei Shtylyov
2013-06-29 22:45 ` [PATCH 1/3] ARM: shmobile: use common platform header for HPB-DMAC Sergei Shtylyov
2013-07-01 4:11 ` Kuninori Morimoto
2013-07-01 12:11 ` Sergei Shtylyov
2013-07-18 21:56 ` Sergei Shtylyov
2013-07-02 4:59 ` Magnus Damm
2013-07-18 22:02 ` Sergei Shtylyov [this message]
2013-07-19 0:16 ` Kuninori Morimoto
2013-07-19 11:17 ` Sergei Shtylyov
2013-07-19 11:32 ` Sergei Shtylyov
2013-06-29 22:48 ` [PATCH 2/3] ARM: shmobile: r8a7778: add HPB-DMAC support Sergei Shtylyov
2013-07-01 4:12 ` Kuninori Morimoto
2013-07-18 22:04 ` Sergei Shtylyov
2013-06-29 22:50 ` [PATCH 3/3] ARM: shmobile: BOCK-W: enable DMA for SDHI0 Sergei Shtylyov
2013-07-01 1:30 ` [PATCH 0/3] R8A7778/BOCK-W: HPB-DMAC support " Simon Horman
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=51E865FA.9000706@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@lists.infradead.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).