Changes in Makefile

c9a57edd - staging: greybus: audio: Enable GB codec, audio module compilation.

Thu, 09 Jul 2020 10:27:22 +0000

staging: greybus: audio: Enable GB codec, audio module compilation.Currently you can't enable the Gey Bus Audio Codec because there is noentry for it in the Kconfig file. Originally the config name was goingto be AUDIO_MSM8994 but that's not correct because other types ofhardware are supported now. I have chosen the name AUDIO_APB_CODECinstead. Also I had to update the dependencies for GREYBUS_AUDIO tomake the compile work.Signed-off-by: Vaibhav Agarwal Reviewed-by: Dan Carpenter Link: https://lore.kernel.org/r/2b50959ccffe5a4372880d27e79ef3be1873372c.1594290158.git.vaibhav.sr@gmail.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

510e340e - staging: greybus: audio: Add helper APIs for dynamic audio modules

Thu, 09 Jul 2020 10:27:21 +0000

staging: greybus: audio: Add helper APIs for dynamic audio modulesGreybus Codec driver allows modules to be dynamically added and removed,which further requires updating the DAPM configurations as well.With current snd_soc architecture, dynamic audio modules is not yetsupported. This patch provides helper APIs to update DAPM configurationsin response to modules which are dynamically added or removed. Thesource is primarily based on snd_dapm.cSigned-off-by: Vaibhav Agarwal Reviewed-by: Dan Carpenter Link: https://lore.kernel.org/r/35e1baaae10a3f2162e71be4c2f75a701584f0e6.1594290158.git.vaibhav.sr@gmail.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

b81beec9 - staging: greybus: move es2 to drivers/greybus/

Sun, 25 Aug 2019 05:54:29 +0000

staging: greybus: move es2 to drivers/greybus/The es2 Greybus host controller has long been stable, so move it out ofdrivers/staging/ to drivers/greybus/Cc: Johan Hovold Cc: greybus-dev@lists.linaro.orgCc: linux-kernel@vger.kernel.orgAcked-by: Viresh Kumar Acked-by: Alex Elder Link: https://lore.kernel.org/r/20190825055429.18547-10-gregkh@linuxfoundation.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

8465def4 - staging: greybus: move the greybus core to drivers/greybus

Sun, 25 Aug 2019 05:54:28 +0000

staging: greybus: move the greybus core to drivers/greybusThe Greybus core code has been stable for a long time, and has beenshipping for many years in millions of phones. With the advent of arecent Google Summer of Code project, and a number of new devices in theworks from various companies, it is time to get the core greybus codeout of staging as it really is going to be with us for a while.Cc: Johan Hovold Cc: linux-kernel@vger.kernel.orgCc: greybus-dev@lists.linaro.orgAcked-by: Viresh Kumar Acked-by: Alex Elder Link: https://lore.kernel.org/r/20190825055429.18547-9-gregkh@linuxfoundation.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

2eccd4aa - staging: greybus: enable compile testing of arche driver

Tue, 16 May 2017 08:01:39 +0000

staging: greybus: enable compile testing of arche driverAdd Arche platform-driver config option and allow the driver to becompile tested also without the out-of-tree usb3613 driver.Signed-off-by: Johan Hovold Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

bdfb95c4 - staging: greybus: remove timesync protocol support

Thu, 05 Jan 2017 17:39:12 +0000

staging: greybus: remove timesync protocol supportWhile the timesync protocol was a great idea, it never ended up gettingimplemented by any known hardware devices. It's also a bit"interesting" in how it ties into the platform controller.So, just remove it for now. It's not needed, no one uses it, and it's astumbling block in getting the greybus core code merged out of thestaging tree. If anyone wants it in the future, reverting this patch isa great place to start from.Signed-off-by: Greg Kroah-Hartman Reviewed-by: Johan Hovold Reviewed-by: Alex Elder Acked-by: Bryan O'Donoghue Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

b04f56c6 - staging: greybus: makefile: fix dependency of spi to spilib

Thu, 08 Sep 2016 16:17:51 +0000

staging: greybus: makefile: fix dependency of spi to spilibGreybus SPI driver depends on gb-spilib and we need to state that atmakefile to make it link correctly.Signed-off-by: Rui Miguel Silva Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

d4f56b47 - staging: greybus: Add drivers/staging/greybus to the build

Mon, 19 Sep 2016 13:46:40 +0000

staging: greybus: Add drivers/staging/greybus to the buildThis adds a proper Kconfig file for drivers/staging/greybus and fixes upthe Makefile to work correctly within the kernel build system (modulesdepend on the .config options, etc.)Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

e3eda54d - greybus: Add Component Authentication Protocol support

Thu, 30 Jun 2016 15:54:00 +0000

greybus: Add Component Authentication Protocol supportThis patch adds Component Authentication Protocol support in greybus.The purpose of the CAP protocol is to authenticate the Module hardware,and it can only be used when it is present as part of thefirmware-management bundle, on a separate CPort.Compile tested only.Signed-off-by: Viresh Kumar Reviewed-by: Jun Li Tested-by: Jun Li Signed-off-by: Alex Elder List of files: /linux-6.15/drivers/staging/greybus/Makefile

c0e65d02 - greybus: add support for the log protocol

Fri, 24 Jun 2016 21:41:36 +0000

greybus: add support for the log protocolAdd support for the new Log class/protocol. This protocol allows modulesto send their internal logging messages to the AP in order to makemodule debugging easier.The protocol is, for now, composed a single module-initiated request.This request contains a message and associated length. The message isintegrated in the kernel log with dev_dbg(). In order to be displayedwith 'dmesg', the following command needs to be entered first:$ echo "file log.c +p" > /sys/kernel/debug/dynamic_debug/controlThe major portion of this file was initially written by Greg KH.Signed-off-by: Joel Porquet Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

aa62b5e4 - greybus: bootrom: Compile as a separate module

Thu, 09 Jun 2016 11:04:35 +0000

greybus: bootrom: Compile as a separate moduleUser space doesn't break anymore with new greybus modules and its timeto make bootrom a separate module.Signed-off-by: Viresh Kumar Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

970dc85b - greybus: timesync: Add timesync core driver

Sun, 05 Jun 2016 13:03:26 +0000

greybus: timesync: Add timesync core driverThis patch adds the core timesync functionality.0. arche-platform.c/arche-apb-ctrl.c Modifies the platform layer to hook the incoming TIME_SYNC signal up to the timesync strobe IRQ handler. If the arche-platform driver can't satisfy the request for the wake-detect line, it will return -EAGAIN and the calling work-queue must reschedule the attempt to get exclusive access to the wake-detect pin logic. A private data field is added to the arche-platform driver to enable passing of a timesync pointer to the ISR responsible for synchronizing time.1. timesync.c A new file added which contains all of the logic associated with sending greybus commands to SVC, APBx or Interfaces to enable, disable and disseminate timing information.2. timesync_platform.c Any platform/arch specific code goes into timesync_platform.c. Originally the idea was to keep the x86 and ARM arch dependencies in a timesync_platform_arch.c file - however with further refinement that's currently not necessary however just-in-case it becomes necessary to resuscitate arch or platform specific methods for accessing timer resources that access shouldn't be part of the core timesync.c logic and so for the moment we access these timer resources through a thin access layer in timesync_platform.c. Expect this to go away long term ideally.Signed-off-by: Bryan O'Donoghue Acked-by: Alex Elder Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

038405db - greybus: legacy: remove protocol.o from the makefile

Sat, 21 May 2016 01:37:02 +0000

greybus: legacy: remove protocol.o from the makefileCommit 0917cba11 ("legacy: remove legacy driver support")removed protocol.c, however, the corresponding target in the Makefilewas not removed therefore broken the build.Testing Done:- Build & boot on EVT1.5Signed-off-by: David Lin Reviewed-by: Viresh Kumar Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

428888a2 - greybus: legacy: remove legacy driver support

Fri, 20 May 2016 11:33:36 +0000

greybus: legacy: remove legacy driver supportThis patch removes the greybus legacy driver supportSigned-off-by: David Lin Signed-off-by: Laurent Pinchart Reviewed-by: Viresh Kumar Reviewed-by: Johan Hovold Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

e54b106d - greybus: gpbridge: rename 'gpbridge' to 'gbphy' everywhere

Thu, 19 May 2016 15:52:39 +0000

greybus: gpbridge: rename 'gpbridge' to 'gbphy' everywhereThe 'gpbridge' name didn't relaly reflect what the bus is; whichis a bus for bridged-phy devices. So, rename all instancesof 'gpbridge' to more appropriate 'gbphy'Testing Done:Build and boot tested. 'lsgb' will stop displaying 'GPBridge' devicesuntil I change the library to reflect this change.Signed-off-by: Sandeep Patil Suggested-by: Greg Kroah-Hartman Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

013e6653 - greybus: fw-management: Add firmware-management protocol driver

Sat, 14 May 2016 18:12:21 +0000

greybus: fw-management: Add firmware-management protocol driverThis patch adds Firmware Management Protocol support to firmware core,which allows the AP to manage firmware on an Interface.Signed-off-by: Viresh Kumar Reviewed-by: Jun Li Tested-by: Karthik Ravi Shankar Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

8888b963 - greybus: spi: Separate out spilib from spi bridged PHY bundle driver

Sat, 14 May 2016 18:12:20 +0000

greybus: spi: Separate out spilib from spi bridged PHY bundle driverspilib can be used by multiple bridge drivers implementing differentbundle classes. Separate out bridged PHY bundle drivers parts.Signed-off-by: Viresh Kumar Reviewed-by: Rui Miguel Silva Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

4c412921 - greybus: spi: Restructure spi.c to share it with other bundle drivers

Sat, 14 May 2016 18:12:19 +0000

greybus: spi: Restructure spi.c to share it with other bundle driversThis patch restructures spi.c as spilib core, so that the same logic canbe reused for SPI connections implemented as part of different bundletypes. This is required for Firmware Management Bundle.Note that the 'struct gb_protocol' and its callback aren't moved toa separate file in this commit to make its reviews easier. That will bedone by a following patch.Signed-off-by: Viresh Kumar Reviewed-by: Rui Miguel Silva Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile

a4b9a098 - greybus: gpbridge: Rename gb-phy.ko module

Mon, 09 May 2016 12:45:13 +0000

greybus: gpbridge: Rename gb-phy.ko moduleRename gb-phy.ko module as gb-gpbridge.ko.Tested on EVT 1.5 by inserting GP test module, all the devices wereenumerated correctly.Signed-off-by: Viresh Kumar Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/greybus/Makefile