From: Arnd Bergmann <arnd@arndb.de>
To: Sunil Kovvuri <sunil.kovvuri@gmail.com>
Cc: Networking <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
linux-soc@vger.kernel.org, sgoutham@marvell.com
Subject: Re: [PATCH v8 01/15] octeontx2-af: Add Marvell OcteonTX2 RVU AF driver
Date: Mon, 8 Oct 2018 16:29:11 +0200 [thread overview]
Message-ID: <CAK8P3a0W3N-bhBSc-nuyPXtcMnMK-8UdMGOw7gxoH3HXrfjAQg@mail.gmail.com> (raw)
In-Reply-To: <CA+sq2Cdi2VqoycE9Z37sToro=q-mrX5jqq+HyL_bFKn+-DHoyA@mail.gmail.com>
On Mon, Oct 8, 2018 at 3:50 PM Sunil Kovvuri <sunil.kovvuri@gmail.com> wrote:
>
> On Mon, Oct 8, 2018 at 5:52 PM Arnd Bergmann <arnd@arndb.de> wrote:
> >
> > On Sun, Oct 7, 2018 at 4:59 PM <sunil.kovvuri@gmail.com> wrote:
> >
> > > --- /dev/null
> > > +++ b/drivers/net/ethernet/marvell/octeontx2/Kconfig
> > > @@ -0,0 +1,12 @@
> > > +#
> > > +# Marvell OcteonTX2 drivers configuration
> > > +#
> > > +
> > > +config OCTEONTX2_AF
> > > + tristate "Marvell OcteonTX2 RVU Admin Function driver"
> > > + depends on ARM64 && PCI
> >
> > You should try to allow building it on x86 and other architectures, even though
> > the driver won't be used there this helps get reports from static
> > build infrastructure.
> > You could use e.g.
> >
> > depends on (64BIT && COMPILE_TEST) || ARM64
> > depends on PCI
> >
> > Arnd
>
> Thanks for the suggestion.
> But going forward we will have few arm64 assembly instructions used in
> the driver.
What is those inline assembly for? Is there a chance they can
be abstracted through some other interface?
Arnd
next prev parent reply other threads:[~2018-10-08 21:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 14:59 [PATCH v8 00/15] octeontx2-af: Add RVU Admin Function driver sunil.kovvuri
2018-10-07 14:59 ` [PATCH v8 01/15] octeontx2-af: Add Marvell OcteonTX2 RVU AF driver sunil.kovvuri
2018-10-08 12:22 ` Arnd Bergmann
2018-10-08 13:50 ` Sunil Kovvuri
2018-10-08 14:29 ` Arnd Bergmann [this message]
2018-10-07 14:59 ` [PATCH v8 02/15] octeontx2-af: Reset all RVU blocks sunil.kovvuri
2018-10-08 12:16 ` Arnd Bergmann
2018-10-09 7:10 ` Sunil Kovvuri
2018-10-07 14:59 ` [PATCH v8 03/15] octeontx2-af: Gather RVU blocks HW info sunil.kovvuri
2018-10-07 14:59 ` [PATCH v8 04/15] octeontx2-af: Add mailbox support infra sunil.kovvuri
2018-10-07 14:59 ` [PATCH v8 05/15] octeontx2-af: Add mailbox IRQ and msg handlers sunil.kovvuri
2018-10-08 4:11 ` David Miller
2018-10-07 14:59 ` [PATCH v8 06/15] octeontx2-af: Convert mbox msg id check to a macro sunil.kovvuri
2018-10-07 14:59 ` [PATCH v8 07/15] octeontx2-af: Scan blocks for LFs provisioned to PF/VF sunil.kovvuri
2018-10-07 14:59 ` [PATCH v8 08/15] octeontx2-af: Add RVU block LF provisioning support sunil.kovvuri
2018-10-08 12:11 ` Arnd Bergmann
2018-10-08 13:59 ` Sunil Kovvuri
2018-10-08 14:29 ` Arnd Bergmann
2018-10-07 14:59 ` [PATCH v8 09/15] octeontx2-af: Configure block LF's MSIX vector offset sunil.kovvuri
2018-10-07 14:59 ` [PATCH v8 10/15] octeontx2-af: Reconfig MSIX base with IOVA sunil.kovvuri
2018-10-08 12:08 ` Arnd Bergmann
2018-10-09 7:02 ` Sunil Kovvuri
2018-10-09 7:57 ` Arnd Bergmann
2018-10-09 9:20 ` Sunil Kovvuri
2018-10-09 12:00 ` Arnd Bergmann
2018-10-10 7:35 ` Sunil Kovvuri
2018-10-10 7:58 ` Arnd Bergmann
2018-10-07 14:59 ` [PATCH v8 11/15] octeontx2-af: Add Marvell OcteonTX2 CGX driver sunil.kovvuri
2018-10-07 14:59 ` [PATCH v8 12/15] octeontx2-af: Set RVU PFs to CGX LMACs mapping sunil.kovvuri
2018-10-07 14:59 ` [PATCH v8 13/15] octeontx2-af: Add support for CGX link management sunil.kovvuri
2018-10-07 14:59 ` [PATCH v8 14/15] octeontx2-af: Register for CGX lmac events sunil.kovvuri
2018-10-07 14:59 ` [PATCH v8 15/15] MAINTAINERS: Add entry for Marvell OcteonTX2 Admin Function driver sunil.kovvuri
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=CAK8P3a0W3N-bhBSc-nuyPXtcMnMK-8UdMGOw7gxoH3HXrfjAQg@mail.gmail.com \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgoutham@marvell.com \
--cc=sunil.kovvuri@gmail.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 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).