From: Grant Likely <grant.likely@secretlab.ca>
To: Sergey Temerkhanov <temerkhanov@yandex.ru>
Cc: microblaze-uclinux@itee.uq.edu.au,
Sergey Temerkhanov <temerkhanov@cifronik.ru>,
linuxppc-dev@lists.ozlabs.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
steve@digidescorp.com
Subject: Re: [PATCH] [RFC] Xilinx MPMC SDMA subsystem
Date: Mon, 29 Mar 2010 14:20:31 -0600 [thread overview]
Message-ID: <fa686aa41003291320o76b88ca3vd98bdef5ff592277@mail.gmail.com> (raw)
In-Reply-To: <201003292304.39657.temerkhanov@yandex.ru>
On Mon, Mar 29, 2010 at 1:04 PM, Sergey Temerkhanov
<temerkhanov@yandex.ru> wrote:
> On Monday 29 March 2010 19:56:15 Grant Likely wrote:
>> On Mon, Mar 29, 2010 at 9:42 AM, Steven J. Magnani
>>
>> <steve@digidescorp.com> wrote:
>> > On Fri, 2010-03-26 at 17:53 -0600, Grant Likely wrote:
>> >> I've not got time to review this patch right now, but Sergey and
>> >> Steven, you both posted MPMC drivers on the same day; Steven on the
>> >> microblaze list and Sergey on the powerpc list. =9ACan you two please
>> >> coordinate and figure out how to mork toward a single driver that wil=
l
>> >> meet both your needs? =9AI don't want to have 2 drivers (3 if you cou=
nt
>> >> the ll_temac driver) in mainline for the same hardware interface.
>> >
>> > I don't think we'll end up with a single driver. A MPMC DMA Engine
>> > driver is useful only on "loopback" SDMA ports. Sergey's code looks li=
ke
>> > a nice generic interface to Xilinx SDMA HW that could be used by the
>> > xlldma and ll_temac drivers, for instance. Both of those will get
>> > smaller, but won't go away.
>
> Yes, it's like having IBM EMAC driver and MAL layer or something
>
>> >
>> > For this to be useful to me, it would need to be located somewhere mor=
e
>> > accessible than arch/powerpc and it would need to have initialization
>> > methods that don't depend on OF. In my build I would have platform cod=
e
>> > that binds to the xlldma platform attachment, which would call Sergey'=
s
>> > SDMA code to assign it the proper resources.
>>
>> That should be fine.
>
> Well, I'll look at my old code for the platform interface bindings. I rem=
ember
> it worked well on arch/ppc with my other drivers.
Don't get too caught up in this aspect. of_platform_bus_type is being
merged with platform_bus_type. One driver can be written to handle
both use cases. However, it may not make any sense for the DMA
library layer to have a bus binding since it is mostly a set of shared
routines. I'm fine if the bindings are only at the SDMA driver and
ll_temac driver level.
g.
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2010-03-29 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 18:18 [PATCH] [RFC] Xilinx MPMC SDMA subsystem Sergey Temerkhanov
2010-03-26 23:53 ` Grant Likely
2010-03-29 15:42 ` Steven J. Magnani
2010-03-29 15:56 ` Grant Likely
2010-03-29 19:04 ` Sergey Temerkhanov
2010-03-29 20:20 ` Grant Likely [this message]
2010-04-20 16:29 ` Steven J. Magnani
2010-04-27 16:09 ` Sergey Temerkhanov
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=fa686aa41003291320o76b88ca3vd98bdef5ff592277@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=steve@digidescorp.com \
--cc=temerkhanov@cifronik.ru \
--cc=temerkhanov@yandex.ru \
/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).