[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20231121075155.16078-1-bagasdotme@gmail.com>
Date: Tue, 21 Nov 2023 14:51:55 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Staging Drivers <linux-staging@...ts.linux.dev>
Cc: Martyn Welch <martyn@...chs.me.uk>,
Manohar Vanga <manohar.vanga@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Soumya Negi <soumya.negi97@...il.com>,
Alexon Oliveira <alexondunkan@...il.com>,
Andi Shyti <andi.shyti@...ux.intel.com>,
Jinjie Ruan <ruanjinjie@...wei.com>,
Menna Mahmoud <eng.mennamahmoud.mm@...il.com>,
Gaosheng Cui <cuigaosheng1@...wei.com>,
Matt Jan <zoo868e@...il.com>,
Michael Straube <straube.linux@...il.com>,
Dorine Tipo <dorine.a.tipo@...il.com>,
Julia Lawall <julia.lawall@...ia.fr>,
Charles Han <hanchunchao@...pur.com>,
Bagas Sanjaya <bagasdotme@...il.com>
Subject: [PATCH RESEND] drivers: staging: vme_user: Describe VME_BUS and VME_TSI148
Help description for both options only tells users to enable them
without description of what VME bridge and TSI148 device are.
Briefly describe them.
Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
---
This is a wording alternative to Dorine's patch [1]. The wording is
inspired by [2] and [3].
[1]: https://lore.kernel.org/outreachy/20231029180346.8570-1-dorine.a.tipo@gmail.com/
[2]: https://ohwr.org/project/vme-sbc-a25-pcie-vme-bridge/wikis/home
[3]: https://www.slac.stanford.edu/grp/lcls/controls/global/hw/users_guides/cpu/pci-bridge/Tsi148.pdf
drivers/staging/vme_user/Kconfig | 22 ++++++++++++++++++----
1 file changed, 18 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/vme_user/Kconfig b/drivers/staging/vme_user/Kconfig
index d65cc5510649e9..8e5df6ce36e8f9 100644
--- a/drivers/staging/vme_user/Kconfig
+++ b/drivers/staging/vme_user/Kconfig
@@ -3,18 +3,32 @@ menuconfig VME_BUS
bool "VME bridge support"
depends on PCI
help
- If you say Y here you get support for the VME bridge Framework.
+ Enable support for VME (VersaModular Eurocard bus) bridge modules.
+ The bridge allows connecting VME devices to systems with existing
+ interfaces (like USB or PCI) by means of translating VME protocol
+ operations.
+
+ Note that this only enables the bridge framework. You'll also
+ likely want to enable driver for specific bridge device you have
+ to actually use it. If unsure, say N.
if VME_BUS
comment "VME Bridge Drivers"
config VME_TSI148
- tristate "Tempe"
+ tristate "Tundra TSI148 VME bridge support"
depends on HAS_DMA
help
- If you say Y here you get support for the Tundra TSI148 VME bridge
- chip.
+ If you say Y here you get support for the Tundra TSI148 VME-to-PCI/X
+ bridge chip (and pin-compatible clones).
+
+ TSI148 is a high-performant, 2eSST and VME64-compliant VME-to-PCI/X
+ interconnect bridge with support for PCI and PCI-X bus interface.
+ It is primarily used in industrial and embedded systems.
+
+ To compile this driver as a module, say M - the module will be
+ called vme_tsi148. If unsure, say N.
config VME_FAKE
tristate "Fake"
base-commit: 98b1cc82c4affc16f5598d4fa14b1858671b2263
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists