From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: "open list:MIPS" <linux-mips@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev
Subject: Re: Some doubts about mt7621-pci mainline place
Date: Wed, 12 May 2021 06:11:25 +0200 [thread overview]
Message-ID: <CAMhs-H_4YPevS5KuuTrhXAzMVfPrTiosg88Ch8s=iXYrkJ2biw@mail.gmail.com> (raw)
In-Reply-To: <20210511204758.GD18185@alpha.franken.de>
Hi Thomas,
On Tue, May 11, 2021 at 10:48 PM Thomas Bogendoerfer
<tsbogend@alpha.franken.de> wrote:
>
> On Mon, May 10, 2021 at 08:43:51AM +0200, Sergio Paracuellos wrote:
> > in staging and is properly using the pci generic APIs instead of the
> > PCI_LEGACY which seems that all other drivers in 'arch/mips/pci' are
> > using. The driver is generic enough but it needs mips iocu region
> > configuration that is done in the driver itself. So here it is where
> > my questions come. Is 'arch/mips/pci' the place to move this driver?
>
> moving to arch/mips/pci would work for me. Could you look at converting
> the driver to PCI_DRIVERS_GENERIC instead of LEGACY ? I want to
> get rid of PCI_LEGACY...
Driver is already using PCI_DRIVERS_GENERIC, so as soon as I get
bindings validated I will send patches to move into 'arch/mips/pci'.
>
> > Is the driver the correct place to configure the iocu related with
> > pci?
>
> I see no problem with this at the moment.
Ok, good to know :).
>
> Thomas.
>
Thanks,
Sergio Paracuellos
> --
> Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
> good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-05-12 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 6:43 Some doubts about mt7621-pci mainline place Sergio Paracuellos
2021-05-11 20:47 ` Thomas Bogendoerfer
2021-05-12 4:11 ` Sergio Paracuellos [this message]
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='CAMhs-H_4YPevS5KuuTrhXAzMVfPrTiosg88Ch8s=iXYrkJ2biw@mail.gmail.com' \
--to=sergio.paracuellos@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=tsbogend@alpha.franken.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;
as well as URLs for NNTP newsgroup(s).