From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Ioana Ciornei <ciorneiioana@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: Re: [PATCH 0/5] bus: fsl-mc: add userspace support
Date: Wed, 27 Jan 2021 16:06:56 +0200 [thread overview]
Message-ID: <439f17ab-bd7d-6415-bc02-d570c1288f11@nxp.com> (raw)
In-Reply-To: <YBFyiQJLklTuQH7z@kroah.com>
On 1/27/2021 4:02 PM, Greg KH wrote:
> On Thu, Jan 14, 2021 at 07:07:47PM +0200, Ioana Ciornei wrote:
>> From: Ioana Ciornei <ioana.ciornei@nxp.com>
>>
>> This patch set adds userspace support in the fsl-mc bus along with a
>> rescan attribute to the root DPRC container. An earlier discussion on
>> this functionality can be found at the link below. I didn't continue
>> with the versioning scheme since quite some time has passed since the
>> last discussion.
>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flkml.org%2Flkml%2F2018%2F11%2F20%2F1162&data=04%7C01%7Claurentiu.tudor%40nxp.com%7C8d74c7b04f864d17419508d8c2cc3e10%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637473529759283328%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=kDWLNqq91k5LW74jgZ%2Blu%2FZJfCmeLUZm5DccUiS4m94%3D&reserved=0
>>
>> The FSL_MC_SEND_MC_COMMAND ioctl acts as a direct passthrough to the
>> Management Complex (or MC) by passing fixed-length command/response
>> pairs. Keeping in mind that the MC manages DPAA2 hardware resources and
>> provides and object-based abstraction for sofware drivers, the proposed
>> ioctl interface enables userspace tools to do the following:
>> - Get layout information about the available resources abstracted and
>> exported by the Management Complex firmware. This is especially
>> useful to generate a complete description of the current hardware
>> resource partitioning.
>> - Manage DPAA2 objects lifecycle (create, destroy) and establish
>> connection between different components as needed.
>>
>> The ioctl interface is intended for dynamic usecases where DPAA2 objects
>> need to be created on demand or destroyed so that the underlying
>> hardware resources can be further repurposed. In static usecases,
>> depending on the requirements, a firmware configuration file can be used
>> to describe the needed DPAA2 objects, their attributes or any link
>> between them.
>>
>> Each command received through the ioctl interface is first checked
>> against a list of accepted MC commands. Also, commands which would alter
>> the hardware resource management require CAP_NET_ADMIN. The command is
>> also check so that it does not contain garbage beyond the maximum size
>> expected for that command id.
>
> I need an ack from the maintainers here before I can take this series.
>
Sorry, got caught with other things and forgot about it. Done.
---
Thanks & Best Regards, Laurentiu
next prev parent reply other threads:[~2021-01-27 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 17:07 Ioana Ciornei
2021-01-14 17:07 ` [PATCH 1/5] bus: fsl-mc: move fsl_mc_command struct in a uapi header Ioana Ciornei
2021-01-14 17:07 ` [PATCH 2/5] bus: fsl-mc: export mc_cmd_hdr_read_cmdid() to the fsl-mc bus Ioana Ciornei
2021-01-14 17:07 ` [PATCH 3/5] bus: fsl-mc: add fsl-mc userspace support Ioana Ciornei
2021-01-14 17:07 ` [PATCH 4/5] bus: fsl-mc: add bus rescan attribute Ioana Ciornei
2021-01-14 17:07 ` [PATCH 5/5] bus: fsl-mc: add autorescan sysfs Ioana Ciornei
2021-01-27 14:02 ` [PATCH 0/5] bus: fsl-mc: add userspace support Greg KH
2021-01-27 14:06 ` Laurentiu Tudor [this message]
2021-01-27 14:05 ` Laurentiu Tudor
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=439f17ab-bd7d-6415-bc02-d570c1288f11@nxp.com \
--to=laurentiu.tudor@nxp.com \
--cc=ciorneiioana@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ioana.ciornei@nxp.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®