- Aug 11, 2022
-
-
Dave Stevenson authored
commit 7291e7d6 upstream. There's no reason why 2 Raspberry Pi DSI displays can't be attached to a Pi Compute Module, so the backlight names need to be unique. Use the parent dev_name. It's not as readable, but is unique. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.com> Signed-off-by:
Detlev Casanova <detlev.casanova@collabora.com> Link: https://lore.kernel.org/r/20220124220129.158891-2-detlev.casanova@collabora.com Signed-off-by:
Mark Brown <broonie@kernel.org> Signed-off-by:
Rahul T R <r-ravikumar@ti.com>
-
Robert Nelson authored
Signed-off-by:Robert Nelson <robertcnelson@gmail.com>
-
Matthijs van Duin authored
"uio" for generic use "ti,pruss-shmem" for backwards compatibility the of_id module parameter is still supported to add another id
-
Matthijs van Duin authored
-
Jason Kridner authored -
Ming zq authored
-
Robert Nelson authored
Signed-off-by: -
Kishon Vijay Abraham I authored
Lets drive Sierra clock output and workaround a TIFS/DM bug for now. Signed-off-by:Kishon Vijay Abraham I <kishon@ti.com>
-
Jason Kridner authored
Signed-off-by:Jason Kridner <jkridner@beagleboard.org>
-
Vaishnav Achath authored
split the rename changes across two separate patches to work around the buildroot apply-patch issue. Signed-off-by:Vaishnav M A <vaishnav@beagleboard.org>
-
Vaishnav Achath authored
Tested on PocketBeagle + ATUSB + CC1352R SensorTag: debian@beaglebone:~$ uname -a Linux beaglebone 5.8.18-bone23 #1xross PREEMPT Tue Dec 15 15:41:20 IST 2020 armv7l GNU/Linux All drivers probed correctly as per manifest, but a kernel panic occurs after sometime: debian@beaglebone:~$ dmesg [ 218.793223] greybus 1-svc: no primary interface detected on module 2 [ 218.876678] greybus 1-2.2: Interface added (greybus) [ 218.876707] greybus 1-2.2: GMP VID=0x00000126, PID=0x00000126 [ 218.876739] greybus 1-2.2: DDBL1 Manufacturer=0x00000126, Product=0x00000126 [ 219.296368] greybus 1-2.2: excess descriptors in interface manifest [ 220.922786] mikrobus:mikrobus_port_gb_register: mikrobus gb_probe , num cports= 3 [ 220.922793] mikrobus:mikrobus_port_gb_register: protocol added 11 [ 220.922824] mikrobus:mikrobus_port_gb_register: protocol added 3 [ 220.922829] mikrobus:mikrobus_port_gb_register: protocol added 2 [ 220.922896] mikrobus:mikrobus_port_register: registering p...
-
Vaishnav Achath authored
Add Greybus Netlink driver for Greybus Copyright (c) 2017 BayLibre SAS Signed-off-by:Alexandre Bailon <abailon@baylibre.com>
-
Vaishnav Achath authored
Signed-off-by: -
Vaishnav Achath authored
change of_property_read_u32 for the current-speed property to use the device_property_read_u32 offered by the Unified Device Properties Interface, this helps passing the properties over a suitably populated struct property_entry. Signed-off-by: -
Vaishnav Achath authored
currently if there is more than one device with the same ROM ID, there will be a conflict even if the devices are on different w1 master. Signed-off-by: -
Vaishnav Achath authored
export serdev id table to the module header. Signed-off-by: -
Vaishnav Achath authored
add of_find_serdev_controller_by_node to obtain a serdev_controller from the device_node, which can help if the serdev_device is not described over device tree and instantiation of the device happens from a different driver, for the same purpose an option to not delete an empty serdev controller is added. Signed-off-by: -
Vaishnav Achath authored
Signed-off-by: -
Vaishnav Achath authored
Signed-off-by: -
Ricardo Ribalda authored
This patch allows file2alias to generate the proper module headers to support serdev modalias drivers. Eg: root@qt5022:~# modinfo serdev:ttydev | grep alias alias: serdev:ttydev_serdev alias: serdev:ttydev root@qt5022:~# cat /lib/modules/4.16.0-qtec-standard/modules.alias | grep serdev alias serdev:ttydev_serdev serdev_ttydev alias serdev:ttydev serdev_ttydev Signed-off-by:Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
-
Ricardo Ribalda authored
Currently,a serdev device driver can only be used with devices that are nodes of a device tree, or are part of the ACPI table.id_table will be used for devices that are not part of the device tree nor the ACPI table (example: device on greybus gbphy created uart). corresponding modalias field is introduced to name the driver to be used with the device, required device(s) that are neither described by device tree nor ACPI table. serdev_device_uevent is also extended for modalias devices. Signed-off-by: -
Vaishnav Achath authored
This Patch series is an update to the mikroBUS driver with support for serdev devices and fixed regulator. RFC v1 Patch : https://lkml.org/lkml/2020/7/24/518 . The mikrobus driver is updated to add mikrobus ports from device-tree overlays, the debug interfaces for adding mikrobus ports through sysFS is removed, and the driver considers the extended usage of mikrobus port pins from their standard purposes. change log: v2: support for adding mikroBUS ports from DT overlays, remove debug sysFS interface for adding mikrobus ports, consider extended pin usage/deviations from mikrobus standard specifications, use greybus CPort protocol enum instead of new protcol enums Fix cases of wrong indendation, ignoring return values, freeing allocated resources in case of errors and other style suggestions in v1 review. Signed-off-by:
-
Jason Kridner authored
-
Robert Nelson authored
This reverts commit 956b200a . Signed-off-by:
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Reference: v5.15.60 Signed-off-by: -
Robert Nelson authored
Reference: v5.15.60 Signed-off-by: -
Robert Nelson authored
Reference: v5.10.136 Signed-off-by: -
-
-
Robert Nelson authored
Signed-off-by: -
-
Robert Nelson authored
Signed-off-by: -
-
Jason Kridner authored
From https://github.com/statropy/wpanusb
-
-
Robert Nelson authored
Signed-off-by: -
-
Robert Nelson authored
Signed-off-by:
-
