Changes in Kconfig

6f660ffc - usb: gadget: midi2: Reverse-select at the right place

Wed, 01 Jan 2025 13:11:19 +0000

usb: gadget: midi2: Reverse-select at the right placeWe should do reverse selection of other components fromCONFIG_USB_F_MIDI2 which is tristate, instead ofCONFIG_USB_CONFIGFS_F_MIDI2 which is bool, for satisfying subtlemodule dependencies.Fixes: 8b645922b223 ("usb: gadget: Add support for USB MIDI 2.0 function driver")Cc: stable Signed-off-by: Takashi Iwai Link: https://lore.kernel.org/r/20250101131124.27599-1-tiwai@suse.deSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/gadget/Kconfig

7b07a2a7 - usb: gadget: functionfs: Add DMABUF import interface

Tue, 30 Jan 2024 12:23:39 +0000

usb: gadget: functionfs: Add DMABUF import interfaceThis patch introduces three new ioctls. They all should be called on adata endpoint (ie. not ep0). They are:- FUNCTIONFS_DMABUF_ATTACH, which takes the file descriptor of a DMABUF object to attach to the endpoint.- FUNCTIONFS_DMABUF_DETACH, which takes the file descriptor of the DMABUF to detach from the endpoint. Note that closing the endpoint's file descriptor will automatically detach all attached DMABUFs.- FUNCTIONFS_DMABUF_TRANSFER, which requests a data transfer from / to the given DMABUF. Its argument is a structure that packs the DMABUF's file descriptor, the size in bytes to transfer (which should generally be set to the size of the DMABUF), and a 'flags' field which is unused for now. Before this ioctl can be used, the related DMABUF must be attached with FUNCTIONFS_DMABUF_ATTACH.These three ioctls enable the FunctionFS code to transfer data betweenthe USB stack and a DMABUF object, which can be provided by a driverfrom a completely different subsystem, in a zero-copy fashion.Signed-off-by: Paul Cercueil Acked-by: Daniel Vetter Acked-by: Christian König Link: https://lore.kernel.org/r/20240130122340.54813-4-paul@crapouillou.netSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/gadget/Kconfig

8b645922 - usb: gadget: Add support for USB MIDI 2.0 function driver

Tue, 25 Jul 2023 06:22:00 +0000

usb: gadget: Add support for USB MIDI 2.0 function driverThis patch adds the support for USB MIDI 2.0 gadget function driver.The driver emulates a USB MIDI 2.0 interface with one or more UMPEndpoints, where each of UMP Endpoint is a pair of MIDI Endpoints forhandling MIDI 2.0 UMP packets. When the function driver is bound, thedriver creates an ALSA card object with UMP rawmidi devices. This isa kind of loop-back where the incoming and upcoming UMP packetsfrom/to the MIDI 2.0 UMP Endpoints are transferred as-is. Inaddition, legacy (MIDI 1.0) rawmidi devices are created, so thatlegacy applications can work in the gadget side, too.When a USB MIDI 2.0 gadget interface appears, the connected host canuse it with the snd-usb-audio driver where MIDI 2.0 support isenabled. Both gadget and connected hosts will have the similar UMPEndpoint and Function Block (or Group Terminal Block) information.Slight differences are the direction and UI-hint bits; it's due to thenature of gadget driver, and the input/output direction is swapped inboth sides (the input for gadget is the output for host, and viceversa).The driver supports the brand-new UMP v1.1 feature, including the UMPStream message handling for providing UMP Endpoint and Function Blockinformation as well as dealing with the MIDI protocol switch. Thedriver responds to UMP Stream messages by itself. OTOH, MIDI-CImessage handling isn't implemented in the kernel driver; it should beprocessed in the user-space through the loopback UMP device.As of this patch, the whole configuration is fixed, providing only onebidirectional UMP Endpoint containing a single FB/GTB with a singleUMP Group. The configuration will be dynamically changeable in thefollowing patches.The traditional MIDI 1.0 is still provided in the altset 0 (which ismandatory per spec). But it's only about the configuration, and noactual I/O will be running for the altset 0 as of this patch. Theproper support MIDI 1.0 altset will follow in later patches, too.Signed-off-by: Takashi Iwai Link: https://lore.kernel.org/r/20230725062206.9674-2-tiwai@suse.deSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/gadget/Kconfig

466be4c9 - usb: uvc: move uvc_fmts and uvc_format_by_guid to own compile unit

Thu, 26 Jan 2023 23:14:54 +0000

usb: uvc: move uvc_fmts and uvc_format_by_guid to own compile unitThe media driver USB_VIDEO_CLASS and USB_F_UVC are using the samefunction uvc_format_by_guid. Since the function is inline, every userwill get a copy of the used uvc_fmts array and the function. This patchmoves the code to an own compile unit and add this dependency asUVC_COMMON to both users.Reviewed-by: Laurent Pinchart Reviewed-by: Daniel Scally Tested-by: Daniel Scally Signed-off-by: Michael Grzeschik Link: https://lore.kernel.org/r/20230126231456.3402323-4-m.grzeschik@pengutronix.deSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/gadget/Kconfig

9958d30f - media: Kconfig: cleanup VIDEO_DEV dependencies

Sun, 13 Mar 2022 06:25:46 +0000

media: Kconfig: cleanup VIDEO_DEV dependenciesmedia Kconfig has two entries associated to V4L API:VIDEO_DEV and VIDEO_V4L2.On Kernel 2.6.x, there were two V4L APIs, each one with its own flag.VIDEO_DEV were meant to: 1) enable Video4Linux and make its Kconfig options to appear; 2) it makes the Kernel build the V4L core.while VIDEO_V4L2 where used to distinguish between drivers thatimplement the newer API and drivers that implemented the former one.With time, such meaning changed, specially after the removal ofall V4L version 1 drivers.At the current implementation, VIDEO_DEV only does (1): it enablesthe media options related to V4L, that now has: menu "Video4Linux options" visible if VIDEO_DEV source "drivers/media/v4l2-core/Kconfig" endmenubut it doesn't affect anymore the V4L core drivers.The rationale is that the V4L2 core has a "soft" dependencyat the I2C bus, and now requires to select a number of otherKconfig options: config VIDEO_V4L2 tristate depends on (I2C || I2C=n) && VIDEO_DEV select RATIONAL select VIDEOBUF2_V4L2 if VIDEOBUF2_CORE default (I2C || I2C=n) && VIDEO_DEVIn the past, merging them would be tricky, but it seems that it is nowpossible to merge those symbols, in order to simplify V4L dependencies.Let's keep VIDEO_DEV, as this one is used on some make *defconfigconfigurations.Suggested-by: Laurent Pinchart Reviewed-by: Laurent Pinchart Reviewed-by: Jacopo Mondi Reviewed-by: Neil Armstrong # for meson-vdec & meson-ge2dAcked-by: Andrzej Pietrasiewicz Acked-by: Łukasz Stelmach Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/usb/gadget/Kconfig

e81e7f9a - usb: gadget: uvc: add scatter gather support

Mon, 28 Jun 2021 15:53:10 +0000

usb: gadget: uvc: add scatter gather supportThis patch adds support for scatter gather transfers. If the underlyinggadgets sg_supported == true, then the videeobuf2-dma-sg is used and theencode routine maps all scatter entries to separate scatterlists for theusb gadget.When streaming 1080p with request size of 1024 times 3 bytes top shows adifference of about 6.4% CPU load applying this patch: PID USER PR NI VIRT RES %CPU %MEM TIME+ S COMMAND 64 root 0 -20 0.0m 0.0m 7.7 0.0 0:01.25 I [kworker/u5:0-uvcvideo] 83 root 0 -20 0.0m 0.0m 4.5 0.0 0:03.71 I [kworker/u5:3-uvcvideo] 307 root -51 0 0.0m 0.0m 3.8 0.0 0:01.05 S [irq/51-dwc3]vs. 64 root 0 -20 0.0m 0.0m 5.8 0.0 0:01.79 I [kworker/u5:0-uvcvideo] 306 root -51 0 0.0m 0.0m 3.2 0.0 0:01.97 S [irq/51-dwc3] 82 root 0 -20 0.0m 0.0m 0.6 0.0 0:01.86 I [kworker/u5:1-uvcvideo]Signed-off-by: Michael Grzeschik Link: https://lore.kernel.org/r/20210628155311.16762-5-m.grzeschik@pengutronix.deSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/gadget/Kconfig

d7889c20 - usb: gadget: select CONFIG_CRC32

Sun, 03 Jan 2021 21:42:17 +0000

usb: gadget: select CONFIG_CRC32Without crc32 support, this driver fails to link:arm-linux-gnueabi-ld: drivers/usb/gadget/function/f_eem.o: in function `eem_unwrap':f_eem.c:(.text+0x11cc): undefined reference to `crc32_le'arm-linux-gnueabi-ld: drivers/usb/gadget/function/f_ncm.o:f_ncm.c:(.text+0x1e40):more undefined references to `crc32_le' followFixes: 6d3865f9d41f ("usb: gadget: NCM: Add transmit multi-frame.")Signed-off-by: Arnd Bergmann Cc: stable Link: https://lore.kernel.org/r/20210103214224.1996535-1-arnd@kernel.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/gadget/Kconfig

b9b70170 - USB: Fix up terminology

Tue, 30 Jun 2020 17:41:23 +0000

USB: Fix up terminologyUSB is a HOST/DEVICE protocol, as per the specification and alldocumentation. Fix up terms that are not applicable to make thingsmatch up with the terms used through the rest of the USB stack.Signed-off-by: Greg Kroah-Hartman Acked-by: Felipe Balbi Link: https://lore.kernel.org/r/20200630174123.GA1906678@kroah.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/gadget/Kconfig

10e5e6c2 - usb: gadget: move choice ... endchoice to legacy/Kconfig

Wed, 11 Dec 2019 07:38:57 +0000

usb: gadget: move choice ... endchoice to legacy/Kconfigdrivers/usb/gadget/Kconfig includes drivers/usb/gadget/legacy/Kconfiginside the 'choice' block. The current Kconfig allows this, but I'dlike to discourage this usage.People tend to mess up the structure without noticing that entiredrivers/usb/gadget/legacy/Kconfig is placed in the choice context.In fact, legacy/Kconfig mixes up bool and tristate in the choice,and creates nested choice, etc.This commit does not change the behavior, but it will help peoplenotice how badly this Kconfig file is written.Signed-off-by: Masahiro Yamada Link: https://lore.kernel.org/r/20191211073857.16780-1-masahiroy@kernel.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/gadget/Kconfig

ecefae6d - docs: usb: rename files to .rst and add them to drivers-api

Tue, 18 Jun 2019 21:05:38 +0000

docs: usb: rename files to .rst and add them to drivers-apiWhile there are a mix of things here, most of the stuffwere written from Kernel developer's PoV. So, add them tothe driver-api book.A follow up for this patch would be to move documents fromthere that are specific to sysadmins, adding them to theadmin-guide.Signed-off-by: Mauro Carvalho Chehab Acked-by: Johan Hovold Acked-by: Felipe Balbi Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/gadget/Kconfig

cae8dc3b - USB: add missing SPDX lines to Kconfig and Makefiles

Thu, 17 Jan 2019 08:23:50 +0000

USB: add missing SPDX lines to Kconfig and MakefilesThere are a few remaining drivers/usb/ files that do not have SPDXidentifiers in them, all of these are either Kconfig or Makefiles. Addthe correct GPL-2.0 identifier to them to make scanning tools happy.Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/gadget/Kconfig

9dbe416b - Revert "usb: gadget: allow to enable legacy drivers without USB_ETH"

Tue, 12 Dec 2017 10:44:40 +0000

Revert "usb: gadget: allow to enable legacy drivers without USB_ETH"This reverts commit 7a9618a22aadffb55027d665491adf466bced61a.Romain Izard recently reported that commit 7a9618a22aad ended upallowing every legacy gadget driver to statically linked to thekernel, however that doesn't work, since only one legacy gadget can bebound to a controller. Because of that, let's revert the original commitand fix the problem.Reported-by: Romain Izard Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/gadget/Kconfig

7a9618a2 - usb: gadget: allow to enable legacy drivers without USB_ETH

Tue, 31 Oct 2017 18:03:19 +0000

usb: gadget: allow to enable legacy drivers without USB_ETHConsiderable time ago the legacy gadget menu was added inside theUSB_ETH choice. I think this was a mistake and that the legacygadget menu should have been added after "endchoice" instead ofbefore. Hence this patch.Fixes: commit 8443f2d2b778 ("usb: gadget: Gadget directory cleanup - group legacy gadgets")Signed-off-by: Bart Van Assche Reviewed-by: Hannes Reinecke Cc: Nicholas Bellinger Cc: Andrzej Pietrasiewicz Cc: linux-usb@vger.kernel.orgSigned-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/gadget/Kconfig

f8faa3bf - usb: gadget: allow serial gadget console on other configs

Fri, 11 Aug 2017 11:33:23 +0000

usb: gadget: allow serial gadget console on other configsUSB gadget serial console works on functions other than the legacyconfigurations. Let the user enable it when using any function thatuses the serial utilities.Signed-off-by: Thadeu Lima de Souza Cascardo Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/gadget/Kconfig

0591bc23 - usb: gadget: add f_uac1 variant based on a new u_audio api

Sun, 18 Jun 2017 13:23:54 +0000

usb: gadget: add f_uac1 variant based on a new u_audio apiThis patch adds a new function 'f_uac1'(f_uac1 with virtual "ALSA card") thatuses recently created u_audio API. Comparingto legacy f_uac1 function implementation itdoesn't require any real Audio codec to bepresent on the device. In f_uac1 audiostreams are simply sinked to and sourcedfrom a virtual ALSA sound card createdusing u_audio API.Legacy f_uac1 approach is to write audiosamples directly to existing ALSA soundcardf_uac1 approach is more generic/flexibleone - create an ALSA sound card thatrepresents USB Audio function and allows tobe used by userspace application thatmay choose to do whatever it wants with thedata received from the USB Host and chooseto provide whatever it wants as audio datato the USB Host.f_uac1 also has capture support (gadget->host)thanks to easy implementation via u_audio.By default, capture interface has 48000kHz/2chconfiguration, same as playback channel has.f_uac1 descriptors naming conventionuses f_uac2 driver naming convention thatmakes it more common and meaningful.Comparing to f_uac1_legacy, the f_uac1 doesn'thave volume/mute functionality. This is becausethe f_uac1 volume/mute feature unit was dummyimplementation since that driver creation (2009)and never had any real volume control or mutefunctionality, so there is no any differencehere.Since f_uac1 functionality, exposedinterface to userspace (virtual ALSA card),input parameters are so different comparingto f_uac1_legacy, that there is no anyreason to keep them in the same file/module,and separate function was created.g_audio can be built using one of existingUAC functions (f_uac1, f_uac1_legacy or f_uac2)Signed-off-by: Ruslan Bilovol Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/gadget/Kconfig

d355339e - usb: gadget: function: make current f_uac1 implementation legacy

Sun, 18 Jun 2017 13:23:53 +0000

usb: gadget: function: make current f_uac1 implementation legacyBefore introducing new f_uac1 function (with virtualALSA card) make current implementation legacy.This includes renaming of existing files, somevariables, config options and documentationSigned-off-by: Ruslan Bilovol Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/gadget/Kconfig

eb9fecb9 - usb: gadget: f_uac2: split out audio core

Sun, 18 Jun 2017 13:23:52 +0000

usb: gadget: f_uac2: split out audio coreAbstract the peripheral side ALSA sound card code fromthe f_uac2 function into a component that can be calledby various functions, so the various flavors can be splitapart and selectively reused.Visible changes: - add uac_params structure to pass audio paramteres for g_audio_setup - make ALSA sound card's name configurable - add [in/out]_ep_maxpsize - allocate snd_uac_chip structure during g_audio_setup - add u_audio_[start/stop]_[capture/playback] functionsSigned-off-by: Ruslan Bilovol Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/gadget/Kconfig

05853ad6 - usb: fix the comment with regards to DocBook

Tue, 16 May 2017 18:11:58 +0000

usb: fix the comment with regards to DocBookThe USB gadget documentation is not at DocBook anymore.The main file was converted to ReST, and stored atDocumentation/driver-api/usb/gadget.rst, but there arestill several plain text files related to gadget underDocumentation/usb.So, be generic and just mention documentationwithout specifying where it is.Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/gadget/Kconfig

ce4a23cc - usb: fix the comment with regards to DocBook

Sun, 14 May 2017 15:08:25 +0000

usb: fix the comment with regards to DocBookThe USB gadget documentation is not at DocBook anymore.The main file was converted to ReST, and stored atDocumentation/driver-api/usb/gadget.rst, but there arestill several plain text files related to gadget underDocumentation/usb.So, be generic and just mention documentationwithout specifying where it is.Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/usb/gadget/Kconfig

bc27f66e - usb: gadget: reword configuration choices

Fri, 10 Mar 2017 13:11:42 +0000

usb: gadget: reword configuration choicesAs USB_CONFIGFS is not a part of the "USB Gadget Drivers" choiceanymore, the name for the option and its attached description needs tobe more descriptive. It appears one level higher in the configurationmenu, and without the context provided by the comments for the choiceentry, it needs to make sense on its own.Conversely, the "USB Gadget Drivers" entry now only introduces thelegacy drivers, where one or more functions are combined in a singledriver. As the configfs option can be used as a full-fledgedalternative, rename the choice entry to show that it is not the onlyway to provice service as an USB gadget.Signed-off-by: Romain Izard Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/gadget/Kconfig