All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fenghua Yu <fenghua.yu@intel.com>
To: "Vinod Koul" <vkoul@kernel.org>, "Dave Jiang" <dave.jiang@intel.com>
Cc: "Fenghua Yu" <fenghua.yu@intel.com>,
	dmaengine@vger.kernel.org,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] Expose IAA 2.0 device capabilities
Date: Tue,  3 Jan 2023 08:53:35 -0800	[thread overview]
Message-ID: <20230103165337.1570238-1-fenghua.yu@intel.com> (raw)

In-memory Analytics Accelerator (IAA) 2.0 [1] introduces General
Capabilities Register (GENCAP). Add a sysfs attribute to expose the
register to applications.

This series is applied cleanly on top of DSA 2.0 Event Log and Completion
Record Faulting series: 
https://lore.kernel.org/dmaengine/20230103163505.1569356-1-fenghua.yu@intel.com/T/#m13ba6167994f3add6446d2d7e242ecb637c54426

[1] IAA 2.0 spec: https://cdrdv2-public.intel.com/721858/350295-iaa-specification.pdf

Dave Jiang (2):
  dmaengine: idxd: reformat swerror output to standard Linux bitmap
    output
  dmaengine: idxd: expose IAA CAP register via sysfs knob

 .../ABI/stable/sysfs-driver-dma-idxd          |  8 +++++
 drivers/dma/idxd/idxd.h                       |  2 ++
 drivers/dma/idxd/init.c                       |  6 +++-
 drivers/dma/idxd/registers.h                  | 21 ++++++++++++
 drivers/dma/idxd/sysfs.c                      | 34 +++++++++++++++----
 5 files changed, 64 insertions(+), 7 deletions(-)

-- 
2.32.0


             reply	other threads:[~2023-01-03 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 16:53 Fenghua Yu [this message]
2023-01-03 16:53 ` [PATCH 1/2] dmaengine: idxd: reformat swerror output to standard Linux bitmap output Fenghua Yu
2023-01-18 12:02   ` Vinod Koul
2023-01-03 16:53 ` [PATCH 2/2] dmaengine: idxd: expose IAA CAP register via sysfs knob Fenghua Yu

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=20230103165337.1570238-1-fenghua.yu@intel.com \
    --to=fenghua.yu@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.