Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CACmrr9gHucWaWtz07kQms6AsquLKAHbK+_Q0kF=92RGo6HmAFA@mail.gmail.com>
 <20190111004337.7223-1-thirtythreeforty@gmail.com> <874laggf9y.fsf@notabene.neil.brown.name>
In-Reply-To: <874laggf9y.fsf@notabene.neil.brown.name>
From:   George Hilliard <thirtythreeforty@gmail.com>
Date:   Thu, 10 Jan 2019 19:13:29 -0700
Message-ID: <CACmrr9hiU2rwncd9sTrh0WVznybJaTP_JMXCaNMzOKDUTJwGEQ@mail.gmail.com>
Subject: Re: [PATCH v2 1/2] Move ralink-gdma to its own directory
To:     NeilBrown <neil@brown.name>
Cc:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Jan 10, 2019, 6:21 PM NeilBrown <neil@brown.name wrote:
>
> On Thu, Jan 10 2019, thirtythreeforty@gmail.com wrote:
>
> > From: George Hilliard <thirtythreeforty@gmail.com>
> >
> > This is in preparation to allow it and the mt7621-dma drivers to be
> > built separately.  They are completely independent pieces of software,
> > and the Kconfig specifies very different requirements.
> >
> > Cc: linux-kernel@vger.kernel.org
> > Cc: devel@driverdev.osuosl.org
> > Cc: Neil Brown <neil@brown.name>
> > Signed-off-by: George Hilliard <thirtythreeforty@gmail.com>
>
> Hi,
>  thanks for taking an interest in these drivers.
>  I original submitted this code because I though I needed it for my
>  mt7621 hardware, but I've subsequently realized that neither of these
>  dma drivers are used in this hardware.
>  Consequently I cannot test any changes you make.
>  But maybe you can - which would be excellent!
>
>  So this is just letting you and Greg know that despite my stated
>  interest, I cannot actually review or test this.
>
> Thanks,
> NeilBrown
>
>

Thanks for the heads up. Honestly I am not sure to what extent I can
test code changes either, at least with the DMA driver. I'm working
with the MT7688, and official docs for it and its cousin the MT7628
are pretty sparse, so I'm currently not even certain that the ralink
gdma driver works for my SoC.

Onion lists these drivers in their OpenWRT device trees' compatible
strings, so they're related. The SPI driver works out of the box at
least. The MMC driver wants to work but needs debugging. All the
drivers need to be better documented. etc. I hope I can improve them,
and I'll make sure I test any actual kernel code I change!

George