From: Olof Johansson <olof@lixom.net>
To: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Cc: soc@kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org, khilman@kernel.org,
arnd@arndb.de, linux-kernel@vger.kernel.org, vkoul@kernel.org
Subject: Re: [GIT_PULL] SOC: TI Keystone Ring Accelerator driver for v5.6
Date: Thu, 16 Jan 2020 16:03:58 -0800 [thread overview]
Message-ID: <20200117000358.fe7ew4vvnz4yxbzj@localhost> (raw)
In-Reply-To: <1579205259-4845-1-git-send-email-santosh.shilimkar@oracle.com>
Hi,
On Thu, Jan 16, 2020 at 12:07:39PM -0800, Santosh Shilimkar wrote:
> Its bit late for pull request, but if possible, please pull it to
> soc drivers tree.
>
> The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
>
> Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/drivers_soc_for_5.6
>
> for you to fetch changes up to 3277e8aa2504d97e022ecb9777d784ac1a439d36:
>
> soc: ti: k3: add navss ringacc driver (2020-01-15 10:07:27 -0800)
>
> ----------------------------------------------------------------
> SOC: TI Keystone Ring Accelerator driver
>
> The Ring Accelerator (RINGACC or RA) provides hardware acceleration to
> enable straightforward passing of work between a producer and a consumer.
> There is one RINGACC module per NAVSS on TI AM65x SoCs.
This driver doesn't seem to have exported symbols, and no in-kernel
users. So how will it be used?
Usually we ask to hold off until the consuming side/drivers are also ready.
Also, is there a reason this is under drivers/soc/ instead of somewhere more
suitable in the drivers subsystem? It's not "soc glue code" in the same way as
drivers/soc was intended originally.
-Olof
next prev parent reply other threads:[~2020-01-17 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 20:07 [GIT_PULL] SOC: TI Keystone Ring Accelerator driver for v5.6 Santosh Shilimkar
2020-01-17 0:03 ` Olof Johansson [this message]
2020-01-17 5:05 ` santosh.shilimkar
2020-01-17 5:29 ` Vinod Koul
2020-01-17 18:11 ` Olof Johansson
2020-01-17 18:20 ` santosh.shilimkar
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=20200117000358.fe7ew4vvnz4yxbzj@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=soc@kernel.org \
--cc=vkoul@kernel.org \
/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).