greybus-dev

greybus-dev@lists.linaro.org

2 participants
593 discussions

[PATCH 0/2] staging: fix W=1 format-truncation warnings

by Masaharu Noguchi

- This series fixes -Wformat-truncation warnings in staging drivers found with W=1 builds: - greybus: prefix device id to widget/control names safely - vc04_services/bcm2835-camera: compose V4L2 bus_info safely Both changes use scnprintf() for the prefix and strscpy() for the remainder. No functional change intended. Masaharu Noguchi (2): staging: greybus: audio_topology: avoid -Wformat-truncation staging: vc04_services: bcm2835-camera: avoid -Wformat-truncation drivers/staging/greybus/audio_topology.c | 11 ++++++----- .../vc04_services/bcm2835-camera/bcm2835-camera.c | 5 +++-- 2 files changed, 9 insertions(+), 7 deletions(-) -- 2.39.5

22 hours, 25 minutes

f did you have a chance to look at the email we sent last week?

by High Performance

3 days, 17 hours

q did you have a chance to look at the email we sent last week?

by High Performance

3 days, 18 hours

lists.linaro.org Version 19.0 now avaliable for upgrade.

by Mail Solutions on lists.linaro.org

3 days, 19 hours

[PATCH 6.15 088/480] staging: greybus: gbphy: fix up const issue with the match callback

by Greg Kroah-Hartman

6.15-stable review patch. If anyone has any objections, please let me know. ------------------ From: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> [ Upstream commit ce32eff1cf3ae8ac2596171dd0af1657634c83eb ] gbphy_dev_match_id() should be taking a const pointer, as the pointer passed to it from the container_of() call was const to start with (it was accidentally cast away with the call.) Fix this all up by correctly marking the pointer types. Cc: Alex Elder <elder(a)kernel.org> Cc: greybus-dev(a)lists.linaro.org Fixes: d69d80484598 ("driver core: have match() callback in struct bus_type take a const *") Reviewed-by: Johan Hovold <johan(a)kernel.org> Link: https://lore.kernel.org/r/2025070115-reoccupy-showy-e2ad@gregkh Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> Signed-off-by: Sasha Levin <sashal(a)kernel.org> --- drivers/staging/greybus/gbphy.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/greybus/gbphy.c b/drivers/staging/greybus/gbphy.c index 6adcad286633..60cf09a302a7 100644 --- a/drivers/staging/greybus/gbphy.c +++ b/drivers/staging/greybus/gbphy.c @@ -102,8 +102,8 @@ static int gbphy_dev_uevent(const struct device *dev, struct kobj_uevent_env *en } static const struct gbphy_device_id * -gbphy_dev_match_id(struct gbphy_device *gbphy_dev, - struct gbphy_driver *gbphy_drv) +gbphy_dev_match_id(const struct gbphy_device *gbphy_dev, + const struct gbphy_driver *gbphy_drv) { const struct gbphy_device_id *id = gbphy_drv->id_table; @@ -119,7 +119,7 @@ gbphy_dev_match_id(struct gbphy_device *gbphy_dev, static int gbphy_dev_match(struct device *dev, const struct device_driver *drv) { - struct gbphy_driver *gbphy_drv = to_gbphy_driver(drv); + const struct gbphy_driver *gbphy_drv = to_gbphy_driver(drv); struct gbphy_device *gbphy_dev = to_gbphy_dev(dev); const struct gbphy_device_id *id; -- 2.39.5

2 weeks, 6 days

[PATCH 6.16 115/627] staging: greybus: gbphy: fix up const issue with the match callback

by Greg Kroah-Hartman

6.16-stable review patch. If anyone has any objections, please let me know. ------------------ From: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> [ Upstream commit ce32eff1cf3ae8ac2596171dd0af1657634c83eb ] gbphy_dev_match_id() should be taking a const pointer, as the pointer passed to it from the container_of() call was const to start with (it was accidentally cast away with the call.) Fix this all up by correctly marking the pointer types. Cc: Alex Elder <elder(a)kernel.org> Cc: greybus-dev(a)lists.linaro.org Fixes: d69d80484598 ("driver core: have match() callback in struct bus_type take a const *") Reviewed-by: Johan Hovold <johan(a)kernel.org> Link: https://lore.kernel.org/r/2025070115-reoccupy-showy-e2ad@gregkh Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> Signed-off-by: Sasha Levin <sashal(a)kernel.org> --- drivers/staging/greybus/gbphy.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/greybus/gbphy.c b/drivers/staging/greybus/gbphy.c index 6adcad286633..60cf09a302a7 100644 --- a/drivers/staging/greybus/gbphy.c +++ b/drivers/staging/greybus/gbphy.c @@ -102,8 +102,8 @@ static int gbphy_dev_uevent(const struct device *dev, struct kobj_uevent_env *en } static const struct gbphy_device_id * -gbphy_dev_match_id(struct gbphy_device *gbphy_dev, - struct gbphy_driver *gbphy_drv) +gbphy_dev_match_id(const struct gbphy_device *gbphy_dev, + const struct gbphy_driver *gbphy_drv) { const struct gbphy_device_id *id = gbphy_drv->id_table; @@ -119,7 +119,7 @@ gbphy_dev_match_id(struct gbphy_device *gbphy_dev, static int gbphy_dev_match(struct device *dev, const struct device_driver *drv) { - struct gbphy_driver *gbphy_drv = to_gbphy_driver(drv); + const struct gbphy_driver *gbphy_drv = to_gbphy_driver(drv); struct gbphy_device *gbphy_dev = to_gbphy_dev(dev); const struct gbphy_device_id *id; -- 2.39.5

2 weeks, 6 days

[PATCH 6.12 060/369] staging: greybus: gbphy: fix up const issue with the match callback

by Greg Kroah-Hartman

6.12-stable review patch. If anyone has any objections, please let me know. ------------------ From: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> [ Upstream commit ce32eff1cf3ae8ac2596171dd0af1657634c83eb ] gbphy_dev_match_id() should be taking a const pointer, as the pointer passed to it from the container_of() call was const to start with (it was accidentally cast away with the call.) Fix this all up by correctly marking the pointer types. Cc: Alex Elder <elder(a)kernel.org> Cc: greybus-dev(a)lists.linaro.org Fixes: d69d80484598 ("driver core: have match() callback in struct bus_type take a const *") Reviewed-by: Johan Hovold <johan(a)kernel.org> Link: https://lore.kernel.org/r/2025070115-reoccupy-showy-e2ad@gregkh Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> Signed-off-by: Sasha Levin <sashal(a)kernel.org> --- drivers/staging/greybus/gbphy.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/greybus/gbphy.c b/drivers/staging/greybus/gbphy.c index 6adcad286633..60cf09a302a7 100644 --- a/drivers/staging/greybus/gbphy.c +++ b/drivers/staging/greybus/gbphy.c @@ -102,8 +102,8 @@ static int gbphy_dev_uevent(const struct device *dev, struct kobj_uevent_env *en } static const struct gbphy_device_id * -gbphy_dev_match_id(struct gbphy_device *gbphy_dev, - struct gbphy_driver *gbphy_drv) +gbphy_dev_match_id(const struct gbphy_device *gbphy_dev, + const struct gbphy_driver *gbphy_drv) { const struct gbphy_device_id *id = gbphy_drv->id_table; @@ -119,7 +119,7 @@ gbphy_dev_match_id(struct gbphy_device *gbphy_dev, static int gbphy_dev_match(struct device *dev, const struct device_driver *drv) { - struct gbphy_driver *gbphy_drv = to_gbphy_driver(drv); + const struct gbphy_driver *gbphy_drv = to_gbphy_driver(drv); struct gbphy_device *gbphy_dev = to_gbphy_dev(dev); const struct gbphy_device_id *id; -- 2.39.5

2 weeks, 6 days

[PATCH] greybus: svc: use string choice helpers instead of ternary operator

by Nai-Chen Cheng

Replace ternary operator with str_enabled_disabled() helper to improve code readability and consistency. Generated using Coccinelle semantic patch. Signed-off-by: Nai-Chen Cheng <bleach1827(a)gmail.com> --- drivers/greybus/svc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/greybus/svc.c b/drivers/greybus/svc.c index 4256467fcd35..35ea7147dca6 100644 --- a/drivers/greybus/svc.c +++ b/drivers/greybus/svc.c @@ -10,6 +10,7 @@ #include <linux/kstrtox.h> #include <linux/workqueue.h> #include <linux/greybus.h> +#include <linux/string_choices.h> #define SVC_INTF_EJECT_TIMEOUT 9000 #define SVC_INTF_ACTIVATE_TIMEOUT 6000 @@ -73,7 +74,7 @@ static ssize_t watchdog_show(struct device *dev, struct device_attribute *attr, struct gb_svc *svc = to_gb_svc(dev); return sprintf(buf, "%s\n", - gb_svc_watchdog_enabled(svc) ? "enabled" : "disabled"); + str_enabled_disabled(gb_svc_watchdog_enabled(svc))); } static ssize_t watchdog_store(struct device *dev, --- base-commit: 7881cd6886a89eda848192d3f5759ce08672e084 change-id: 20250806-greybus-string-choices-e6d53d2382a6 Best regards, -- Nai-Chen Cheng <bleach1827(a)gmail.com>

3 weeks, 4 days

[RFC 0/6] Introducing CPC support in Greybus

by Damien Riégel

Hi, This patchset brings support for Silicon Labs' CPC protocol as transport layer for Greybus. As an example, a SPI driver is added as physical layer and everything is bundled as a big kernel module. In the future, as we plan to support other physical layers like SDIO, CPC core will be its own module, and each physical layer CPC driver will be its own module as well. CPC implements some of the features of Unipro that Greybus relies upon, like reliable transmission. CPC takes care of detecting transmission errors and retransmit frames if necessary. There's also a flow-control feature, preventing sending messages to full cports. In addition to the host device over SPI part, there's also a class driver for a vendor protocol that enables Bluetooth on supported devices. This is mostly there to open the discussion on how a new protocol should be added to Greybus. Damien Riégel (6): greybus: move host controller drivers comment in Makefile greybus: cpc: add core logic greybus: cpc: add SPI driver greybus: add API for async unidirectional transfer greybus: match device with bundle ID greybus: add class driver for Silabs Bluetooth MAINTAINERS | 12 + drivers/greybus/Kconfig | 2 + drivers/greybus/Makefile | 4 +- drivers/greybus/core.c | 4 + drivers/greybus/cpc/Kconfig | 12 + drivers/greybus/cpc/Makefile | 6 + drivers/greybus/cpc/cpc.h | 135 +++++++ drivers/greybus/cpc/endpoint.c | 158 ++++++++ drivers/greybus/cpc/header.c | 212 ++++++++++ drivers/greybus/cpc/header.h | 81 ++++ drivers/greybus/cpc/host.c | 113 ++++++ drivers/greybus/cpc/protocol.c | 274 +++++++++++++ drivers/greybus/cpc/spi.c | 585 +++++++++++++++++++++++++++ drivers/greybus/operation.c | 52 +++ drivers/staging/greybus/Kconfig | 9 + drivers/staging/greybus/Makefile | 6 + drivers/staging/greybus/silabs-ble.c | 203 ++++++++++ include/linux/greybus.h | 7 +- include/linux/greybus/greybus_id.h | 2 + include/linux/greybus/operation.h | 4 + 20 files changed, 1877 insertions(+), 4 deletions(-) create mode 100644 drivers/greybus/cpc/Kconfig create mode 100644 drivers/greybus/cpc/Makefile create mode 100644 drivers/greybus/cpc/cpc.h create mode 100644 drivers/greybus/cpc/endpoint.c create mode 100644 drivers/greybus/cpc/header.c create mode 100644 drivers/greybus/cpc/header.h create mode 100644 drivers/greybus/cpc/host.c create mode 100644 drivers/greybus/cpc/protocol.c create mode 100644 drivers/greybus/cpc/spi.c create mode 100644 drivers/staging/greybus/silabs-ble.c -- 2.49.0

1 month, 2 weeks

Re: [PATCH] staging: greybus: power_supply fix alignment

by Rui Miguel Silva

Hey Akhil, Thanks for your patch. All looks good with the exception of a small nit... On Mon Jul 14, 2025 at 2:56 PM WEST, Akhil Varkey wrote: > Fix checkpatch check "CHECK:Alignment should match open parenthesis" > > Signed-off-by: Akhil Varkey <akhilvarkey(a)disroot.org> > --- > > Hello, This is my first patch, I appreciate any feedbacks. Thanks!! Welcome, and continue... > --- > drivers/staging/greybus/power_supply.c | 14 +++++++------- > 1 file changed, 7 insertions(+), 7 deletions(-) > > diff --git a/drivers/staging/greybus/power_supply.c b/drivers/staging/greybus/power_supply.c > index 2ef46822f676..a484c0ca058d 100644 > --- a/drivers/staging/greybus/power_supply.c > +++ b/drivers/staging/greybus/power_supply.c > @@ -324,7 +324,7 @@ static struct gb_power_supply_prop *get_psy_prop(struct gb_power_supply *gbpsy, > } > > static int is_psy_prop_writeable(struct gb_power_supply *gbpsy, > - enum power_supply_property psp) > + enum power_supply_property psp) > { > struct gb_power_supply_prop *prop; > > @@ -493,7 +493,7 @@ static int gb_power_supply_description_get(struct gb_power_supply *gbpsy) > if (!gbpsy->model_name) > return -ENOMEM; > gbpsy->serial_number = kstrndup(resp.serial_number, PROP_MAX, > - GFP_KERNEL); > + GFP_KERNEL); > if (!gbpsy->serial_number) > return -ENOMEM; > > @@ -546,7 +546,7 @@ static int gb_power_supply_prop_descriptors_get(struct gb_power_supply *gbpsy) > } > > gbpsy->props = kcalloc(gbpsy->properties_count, sizeof(*gbpsy->props), > - GFP_KERNEL); > + GFP_KERNEL); > if (!gbpsy->props) { > ret = -ENOMEM; > goto out_put_operation; > @@ -634,8 +634,8 @@ static int __gb_power_supply_property_get(struct gb_power_supply *gbpsy, > } > > static int __gb_power_supply_property_strval_get(struct gb_power_supply *gbpsy, > - enum power_supply_property psp, > - union power_supply_propval *val) > + enum power_supply_property psp, > + union power_supply_propval *val) Here you fix the alignment, but the last line goes over column 81, even though 80 is not really one hard requirement anymore, all code (strings is ok to go over to be easier to grep for messages) is on that register. So, to be coherent, if you could please send a V2 without this specific change would be great, Or even better, if you could get rid of all the _ and __ prefixes in functions names that would be great, and will give more space for function paramethers. Your call. Also, gives you also the chance to practice to send a new version ;). Cheers, Rui > { > switch (psp) { > case POWER_SUPPLY_PROP_MODEL_NAME: > @@ -943,8 +943,8 @@ static int gb_power_supplies_setup(struct gb_power_supplies *supplies) > goto out; > > supplies->supply = kcalloc(supplies->supplies_count, > - sizeof(struct gb_power_supply), > - GFP_KERNEL); > + sizeof(struct gb_power_supply), > + GFP_KERNEL); > > if (!supplies->supply) { > ret = -ENOMEM; > -- > 2.47.2

1 month, 2 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

greybus-dev