From: Randy Dunlap <rdunlap@infradead.org>
To: Nipun Gupta <nipun.gupta@amd.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
gregkh@linuxfoundation.org, rafael@kernel.org,
eric.auger@redhat.com, alex.williamson@redhat.com,
cohuck@redhat.com, song.bao.hua@hisilicon.com,
mchehab+huawei@kernel.org, maz@kernel.org, f.fainelli@gmail.com,
jeffrey.l.hugo@gmail.com, saravanak@google.com,
Michael.Srba@seznam.cz, mani@kernel.org, yishaih@nvidia.com,
jgg@ziepe.ca, jgg@nvidia.com, robin.murphy@arm.com,
will@kernel.org, joro@8bytes.org, masahiroy@kernel.org,
ndesaulniers@google.com, linux-arm-kernel@lists.infradead.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Cc: okaya@kernel.org, harpreet.anand@amd.com, nikhil.agarwal@amd.com,
michal.simek@amd.com, git@amd.com
Subject: Re: [PATCH v6 7/7] cdx: add device attributes
Date: Thu, 26 Jan 2023 08:55:36 -0800 [thread overview]
Message-ID: <97a939cd-3898-3d54-e496-a8f33a62856a@infradead.org> (raw)
In-Reply-To: <20230126104630.15493-8-nipun.gupta@amd.com>
Hi--
On 1/26/23 02:46, Nipun Gupta wrote:
> diff --git a/Documentation/ABI/testing/sysfs-bus-cdx b/Documentation/ABI/testing/sysfs-bus-cdx
> index 8c2425fdb6d9..69bdbc891743 100644
> --- a/Documentation/ABI/testing/sysfs-bus-cdx
> +++ b/Documentation/ABI/testing/sysfs-bus-cdx
> @@ -10,3 +10,47 @@ Description:
> For example::
>
> # echo 1 > /sys/bus/cdx/rescan
> +
> +What: /sys/bus/cdx/devices/.../vendor
> +Date: January 2023
> +Contact: nipun.gupta@amd.com
> +Description:
> + Vendor ID for this CDX device. Vendor ID is 16 bit
> + identifier which is specific to the device manufacturer.
> + Combination of Vendor ID and Device ID identifies a device.
> +
> +What: /sys/bus/cdx/devices/.../device
> +Date: January 2023
> +Contact: nipun.gupta@amd.com
> +Description:
> + Device ID for this CDX device. Device ID is a 16 bit
> + identifier to identify a device type within the range
> + of a device manufacturer.
> + Combination of Vendor ID and Device ID identifies a device.
> +
> +What: /sys/bus/cdx/devices/.../reset
> +Date: January 2023
> +Contact: nipun.gupta@amd.com
> +Description:
Reads better without "would":
> + Writing a non-zero value to this file would reset the CDX> + device. On resetting the device, the corresponding driver
> + would be notified twice, once before the device is being
> + reset, and again after the reset has been complete.
Writing a non-zero value to this file resets the CDX
device. On resetting the device, the corresponding driver
is notified twice, once before the device is being
reset, and again after the reset has been complete.
> +
> + For example::
> +
> + # echo 1 > /sys/bus/cdx/.../reset
> +
> +What: /sys/bus/cdx/devices/.../remove
> +Date: January 2023
> +Contact: tarak.reddy@amd.com
> +Description:
> + Writing a non-zero value to this file would remove the
> + corrosponding device from the CDX bus. If the device is
> + to be reconfigured in the Hardware, the device can be
> + removed, so that the device driver does not access the
> + device while it is being reconfigured.
and: (also fix typo of corresponding)
Writing a non-zero value to this file removes the
corresponding device from the CDX bus. If the device is
to be reconfigured in the Hardware, the device can be
removed, so that the device driver does not access the
device while it is being reconfigured.
> +
> + For example::
> +
> + # echo 1 > /sys/bus/cdx/devices/.../remove
--
~Randy
next prev parent reply other threads:[~2023-01-26 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 10:46 [PATCH v6 0/7] add support for CDX bus Nipun Gupta
2023-01-26 10:46 ` [PATCH v6 1/7] cdx: add the cdx bus driver Nipun Gupta
2023-01-26 16:58 ` Randy Dunlap
2023-01-26 10:46 ` [PATCH v6 2/7] iommu/arm-smmu-v3: support ops registration for CDX bus Nipun Gupta
2023-01-26 10:46 ` [PATCH v6 3/7] dt-bindings: bus: add CDX bus controller for versal net Nipun Gupta
2023-01-26 10:46 ` [PATCH v6 4/7] cdx: add MCDI protocol interface for firmware interaction Nipun Gupta
2023-01-28 13:15 ` kernel test robot
2023-01-26 10:46 ` [PATCH v6 5/7] cdx: add cdx controller Nipun Gupta
2023-01-28 12:44 ` kernel test robot
2023-01-28 18:26 ` kernel test robot
2023-01-26 10:46 ` [PATCH v6 6/7] cdx: add rpmsg communication channel for CDX Nipun Gupta
2023-01-26 10:46 ` [PATCH v6 7/7] cdx: add device attributes Nipun Gupta
2023-01-26 16:55 ` Randy Dunlap [this message]
2023-01-27 11:17 ` Nipun Gupta
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=97a939cd-3898-3d54-e496-a8f33a62856a@infradead.org \
--to=rdunlap@infradead.org \
--cc=Michael.Srba@seznam.cz \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=eric.auger@redhat.com \
--cc=f.fainelli@gmail.com \
--cc=git@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=harpreet.anand@amd.com \
--cc=jeffrey.l.hugo@gmail.com \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=masahiroy@kernel.org \
--cc=maz@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=michal.simek@amd.com \
--cc=ndesaulniers@google.com \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=okaya@kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=saravanak@google.com \
--cc=song.bao.hua@hisilicon.com \
--cc=will@kernel.org \
--cc=yishaih@nvidia.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).