linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	Patrick Venture <venture@google.com>
Cc: linux-aspeed <linux-aspeed@lists.ozlabs.org>,
	Andrew Jeffery <andrew@aj.id.au>,
	Eddie James <eajames@linux.ibm.com>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>,
	SoC Team <soc@kernel.org>, arm <arm@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] ARM: aspeed: soc changes for 5.10
Date: Wed, 7 Oct 2020 11:18:22 +0000	[thread overview]
Message-ID: <CACPK8XcLOopkx0k14k25puD3YkwHzZS0+3TLcEL43xbxCZBphA@mail.gmail.com> (raw)
In-Reply-To: <20201003201352.GI8203@lx2k>

On Sat, 3 Oct 2020 at 20:31, Olof Johansson <olof@lixom.net> wrote:
>
> Hi Joel,
>
> On Fri, Sep 25, 2020 at 06:31:28AM +0000, Joel Stanley wrote:
> > Hello Soc maintainers,
> >
> > Here are some ASPEED changes for the 5.10 merge window.
> >
> > The following changes since commit e55f541e51b5136fc0ced0bdf2b33ee3cca3bc96:
> >
> >   soc: aspeed: xdma: Add reset ioctl (2020-09-25 15:32:57 +0930)
> >
> > are available in the Git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git
> > tags/aspeed-5.10-soc
> >
> > for you to fetch changes up to e55f541e51b5136fc0ced0bdf2b33ee3cca3bc96:
> >
> >   soc: aspeed: xdma: Add reset ioctl (2020-09-25 15:32:57 +0930)
> >
> > ----------------------------------------------------------------
> > ASPEED soc driver updates for 5.10
> >
> > New drivers:
> >
> >  - XDMA driver for the BMC to host PCIe DMA device
>
> I don't think this driver belongs in drivers/soc, it's not "soc glue
> logic", and it has a userspace interface. Some of the commits even
> references it as a "misc driver". Mind resubmitting it for drivers/misc
> instead?

(Argh I missed this mail)

We used to have the various little drivers in drivers/misc, but
somewhere along the line we decided to move them to drivers/soc. I
think that was Arnd asking Patrick Venture?

https://lore.kernel.org/linux-arm-kernel/CAK8P3a3CK4o8KnD6M084ULEmm+6_CtNFqYHjSqE5vp+U9YAmkA@mail.gmail.com/

The existing drivers have userspace interfaces for misc parts of the
aspeed chip, mostly relating to the strange (from a traditional
Linux/host perspective) interfaces it exposes to the host. This XDMA
driver should go alongside those other drivers.

With that context, how would you like to proceed?

Cheers,

Joel

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-10-07 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  6:31 [GIT PULL] ARM: aspeed: soc changes for 5.10 Joel Stanley
2020-10-03 20:13 ` Olof Johansson
2020-10-07 11:18   ` Joel Stanley [this message]
2020-10-28  6:10     ` Joel Stanley

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=CACPK8XcLOopkx0k14k25puD3YkwHzZS0+3TLcEL43xbxCZBphA@mail.gmail.com \
    --to=joel@jms.id.au \
    --cc=andrew@aj.id.au \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=eajames@linux.ibm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=olof@lixom.net \
    --cc=soc@kernel.org \
    --cc=venture@google.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).