greybus-dev

greybus-dev@lists.linaro.org

4 participants
595 discussions

Re: [greybus-dev] [PATCH] staging: greybus: fix gb_loopback_stats_attrs definition

by Greg KH

On Fri, May 14, 2021 at 07:53:57PM +0530, Shreyansh Chouhan wrote: > On Fri, May 14, 2021 at 04:05:32PM +0200, Greg KH wrote: > > On Fri, May 14, 2021 at 07:18:38PM +0530, Shreyansh Chouhan wrote: > > > On Fri, May 14, 2021 at 03:36:25PM +0200, Greg KH wrote: > > > > On Fri, May 14, 2021 at 07:00:39PM +0530, Shreyansh Chouhan wrote: > > > > > The gb_loopback_stats_attrs macro, (defined in loopback.c,) is a > > > > > multiline macro whose statements were not enclosed in a do while > > > > > loop. > > > > > > > > > > This patch adds a do while loop around the statements of the said > > > > > macro. > > > > > > > > > > Signed-off-by: Shreyansh Chouhan <chouhan.shreyansh630(a)gmail.com> > > > > > --- > > > > > drivers/staging/greybus/loopback.c | 10 ++++++---- > > > > > 1 file changed, 6 insertions(+), 4 deletions(-) > > > > > > > > > > diff --git a/drivers/staging/greybus/loopback.c b/drivers/staging/greybus/loopback.c > > > > > index 2471448ba42a..c88ef3e894fa 100644 > > > > > --- a/drivers/staging/greybus/loopback.c > > > > > +++ b/drivers/staging/greybus/loopback.c > > > > > @@ -162,10 +162,12 @@ static ssize_t name##_avg_show(struct device *dev, \ > > > > > } \ > > > > > static DEVICE_ATTR_RO(name##_avg) > > > > > > > > > > -#define gb_loopback_stats_attrs(field) \ > > > > > - gb_loopback_ro_stats_attr(field, min, u); \ > > > > > - gb_loopback_ro_stats_attr(field, max, u); \ > > > > > - gb_loopback_ro_avg_attr(field) > > > > > +#define gb_loopback_stats_attrs(field) \ > > > > > + do { \ > > > > > + gb_loopback_ro_stats_attr(field, min, u); \ > > > > > + gb_loopback_ro_stats_attr(field, max, u); \ > > > > > + gb_loopback_ro_avg_attr(field); \ > > > > > + } while (0) > > > > > > > > > > #define gb_loopback_attr(field, type) \ > > > > > static ssize_t field##_show(struct device *dev, \ > > > > > -- > > > > > 2.31.1 > > > > > > > > > > > > > > > > > > Did you test build this change? > > > > > > I built the module using make -C . M=drivers/staging/greybus to test > > > build it. I didn't get any errors. > > > > Really? Can you provide the full build output for this file with your > > change? I don't think you really built this file for the obvious > > reasons... > > I ran make -C . M=drivers/staging/greybus > > I got a three line output saying: > make: Entering directory '/work/linux' > MODPOST drivers/staging/greybus//Module.symvers > make: Leaving directory '/work/linux' > > I just tried rebuilding the kernel with CONFIG_GREYBUS=m, and now I can > see what you are talking about. Why weren't these errors reported when I > ran the previous make command? Does that too check for the config > variables even when I specifically asked it to build a module? You were just asking it to build a subdirectory, not a specific individual file, and when you do that it looks at the configuration settings. It's always good to ensure that you actually build the files you modify before sending patches out. thanks, greg k-h

4 years, 5 months

Re: [greybus-dev] [PATCH] staging: greybus: fix gb_loopback_stats_attrs definition

by Greg KH

On Fri, May 14, 2021 at 07:18:38PM +0530, Shreyansh Chouhan wrote: > On Fri, May 14, 2021 at 03:36:25PM +0200, Greg KH wrote: > > On Fri, May 14, 2021 at 07:00:39PM +0530, Shreyansh Chouhan wrote: > > > The gb_loopback_stats_attrs macro, (defined in loopback.c,) is a > > > multiline macro whose statements were not enclosed in a do while > > > loop. > > > > > > This patch adds a do while loop around the statements of the said > > > macro. > > > > > > Signed-off-by: Shreyansh Chouhan <chouhan.shreyansh630(a)gmail.com> > > > --- > > > drivers/staging/greybus/loopback.c | 10 ++++++---- > > > 1 file changed, 6 insertions(+), 4 deletions(-) > > > > > > diff --git a/drivers/staging/greybus/loopback.c b/drivers/staging/greybus/loopback.c > > > index 2471448ba42a..c88ef3e894fa 100644 > > > --- a/drivers/staging/greybus/loopback.c > > > +++ b/drivers/staging/greybus/loopback.c > > > @@ -162,10 +162,12 @@ static ssize_t name##_avg_show(struct device *dev, \ > > > } \ > > > static DEVICE_ATTR_RO(name##_avg) > > > > > > -#define gb_loopback_stats_attrs(field) \ > > > - gb_loopback_ro_stats_attr(field, min, u); \ > > > - gb_loopback_ro_stats_attr(field, max, u); \ > > > - gb_loopback_ro_avg_attr(field) > > > +#define gb_loopback_stats_attrs(field) \ > > > + do { \ > > > + gb_loopback_ro_stats_attr(field, min, u); \ > > > + gb_loopback_ro_stats_attr(field, max, u); \ > > > + gb_loopback_ro_avg_attr(field); \ > > > + } while (0) > > > > > > #define gb_loopback_attr(field, type) \ > > > static ssize_t field##_show(struct device *dev, \ > > > -- > > > 2.31.1 > > > > > > > > > > Did you test build this change? > > I built the module using make -C . M=drivers/staging/greybus to test > build it. I didn't get any errors. Really? Can you provide the full build output for this file with your change? I don't think you really built this file for the obvious reasons... thanks, greg k-h

4 years, 5 months

Re: [greybus-dev] [PATCH] staging: greybus: fix gb_loopback_stats_attrs definition

by Greg KH

On Fri, May 14, 2021 at 07:00:39PM +0530, Shreyansh Chouhan wrote: > The gb_loopback_stats_attrs macro, (defined in loopback.c,) is a > multiline macro whose statements were not enclosed in a do while > loop. > > This patch adds a do while loop around the statements of the said > macro. > > Signed-off-by: Shreyansh Chouhan <chouhan.shreyansh630(a)gmail.com> > --- > drivers/staging/greybus/loopback.c | 10 ++++++---- > 1 file changed, 6 insertions(+), 4 deletions(-) > > diff --git a/drivers/staging/greybus/loopback.c b/drivers/staging/greybus/loopback.c > index 2471448ba42a..c88ef3e894fa 100644 > --- a/drivers/staging/greybus/loopback.c > +++ b/drivers/staging/greybus/loopback.c > @@ -162,10 +162,12 @@ static ssize_t name##_avg_show(struct device *dev, \ > } \ > static DEVICE_ATTR_RO(name##_avg) > > -#define gb_loopback_stats_attrs(field) \ > - gb_loopback_ro_stats_attr(field, min, u); \ > - gb_loopback_ro_stats_attr(field, max, u); \ > - gb_loopback_ro_avg_attr(field) > +#define gb_loopback_stats_attrs(field) \ > + do { \ > + gb_loopback_ro_stats_attr(field, min, u); \ > + gb_loopback_ro_stats_attr(field, max, u); \ > + gb_loopback_ro_avg_attr(field); \ > + } while (0) > > #define gb_loopback_attr(field, type) \ > static ssize_t field##_show(struct device *dev, \ > -- > 2.31.1 > > Did you test build this change?

4 years, 5 months

[PATCH -next] staging: greybus: audio: Add missing MODULE_DEVICE_TABLE

by Zou Wei

This patch adds missing MODULE_DEVICE_TABLE definition which generates correct modalias for automatic loading of this driver when it is built as an external module. Reported-by: Hulk Robot <hulkci(a)huawei.com> Signed-off-by: Zou Wei <zou_wei(a)huawei.com> --- drivers/staging/greybus/audio_codec.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/greybus/audio_codec.c b/drivers/staging/greybus/audio_codec.c index b589cf6..6fa9781 100644 --- a/drivers/staging/greybus/audio_codec.c +++ b/drivers/staging/greybus/audio_codec.c @@ -1086,6 +1086,7 @@ static const struct of_device_id greybus_asoc_machine_of_match[] = { { .compatible = "toshiba,apb-dummy-codec", }, {}, }; +MODULE_DEVICE_TABLE(of, greybus_asoc_machine_of_match); static struct platform_driver gbaudio_codec_driver = { .driver = { -- 2.6.2

4 years, 5 months

[PATCH] Staging: greybus: tools: loopback_test: fixed coding style issues

by Thais Camacho

Fixed warnings found by checkpatch.pl script Signed-off-by: Thais Camacho <thaiscamachoo(a)gmail.com> --- drivers/staging/greybus/tools/loopback_test.c | 18 +++--------------- 1 file changed, 3 insertions(+), 15 deletions(-) diff --git a/drivers/staging/greybus/tools/loopback_test.c b/drivers/staging/greybus/tools/loopback_test.c index 867bf289df2e..553883b2bfa3 100644 --- a/drivers/staging/greybus/tools/loopback_test.c +++ b/drivers/staging/greybus/tools/loopback_test.c @@ -239,7 +239,6 @@ static void show_loopback_devices(struct loopback_test *t) for (i = 0; i < t->device_count; i++) printf("device[%d] = %s\n", i, t->devices[i].name); - } int open_sysfs(const char *sys_pfx, const char *node, int flags) @@ -274,7 +273,6 @@ float read_sysfs_float_fd(int fd, const char *sys_pfx, const char *node) char buf[SYSFS_MAX_INT]; if (read(fd, buf, sizeof(buf)) < 0) { - fprintf(stderr, "unable to read from %s%s %s\n", sys_pfx, node, strerror(errno)); close(fd); @@ -367,7 +365,6 @@ static int get_results(struct loopback_test *t) r->apbridge_unipro_latency_max - r->apbridge_unipro_latency_min; r->gbphy_firmware_latency_jitter = r->gbphy_firmware_latency_max - r->gbphy_firmware_latency_min; - } /*calculate the aggregate results of all enabled devices */ @@ -407,7 +404,6 @@ static int get_results(struct loopback_test *t) r->apbridge_unipro_latency_max - r->apbridge_unipro_latency_min; r->gbphy_firmware_latency_jitter = r->gbphy_firmware_latency_max - r->gbphy_firmware_latency_min; - } return 0; @@ -536,7 +532,6 @@ static int log_results(struct loopback_test *t) fprintf(stderr, "unable to open %s for appendation\n", file_name); abort(); } - } for (i = 0; i < t->device_count; i++) { if (!device_enabled(t, i)) @@ -550,10 +545,8 @@ static int log_results(struct loopback_test *t) if (ret == -1) fprintf(stderr, "unable to write %d bytes to csv.\n", len); } - } - if (t->aggregate_output) { len = format_output(t, &t->aggregate_results, "aggregate", data, sizeof(data), &tm); @@ -675,11 +668,13 @@ static int open_poll_files(struct loopback_test *t) static int close_poll_files(struct loopback_test *t) { int i; + for (i = 0; i < t->poll_count; i++) close(t->fds[i].fd); return 0; } + static int is_complete(struct loopback_test *t) { int iteration_count; @@ -740,7 +735,6 @@ static int wait_for_complete(struct loopback_test *t) ts = &t->poll_timeout; while (1) { - ret = ppoll(t->fds, t->poll_count, ts, &mask_old); if (ret <= 0) { stop_tests(t); @@ -780,7 +774,6 @@ static void prepare_devices(struct loopback_test *t) if (t->stop_all || device_enabled(t, i)) write_sysfs_val(t->devices[i].sysfs_entry, "type", 0); - for (i = 0; i < t->device_count; i++) { if (!device_enabled(t, i)) continue; @@ -823,13 +816,12 @@ static int start(struct loopback_test *t) return 0; } - void loopback_run(struct loopback_test *t) { int i; int ret; - for (i = 0; dict[i].name != NULL; i++) { + for (i = 0; dict[i].name; i++) { if (strstr(dict[i].name, t->test_name)) t->test_id = dict[i].type; } @@ -852,7 +844,6 @@ void loopback_run(struct loopback_test *t) if (ret) goto err; - get_results(t); log_results(t); @@ -861,7 +852,6 @@ void loopback_run(struct loopback_test *t) err: printf("Error running test\n"); - return; } static int sanity_check(struct loopback_test *t) @@ -881,10 +871,8 @@ static int sanity_check(struct loopback_test *t) fprintf(stderr, "Bad device mask %x\n", (1 << i)); return -1; } - } - return 0; } -- 2.20.1

4 years, 5 months

DMA support via gb-netlink and gbridge

by Kyle Harding

Hey all, new member here! As the subject line suggests, our development hardware does not support UniPro so we were looking at a guest kernel solution with TCP/IP transport over gbridge. However, one of the SDIO bus devices is a wifi module that requires DMA. Is this possible over the current gb-netlink/gbridge to your knowledge? Cheers, -- *—* *Kyle Harding* Embedded Linux Engineer, balena.io

4 years, 6 months

[PATCH] greybus: es2: fix kernel-doc warnings

by Randy Dunlap

Fix these kernel-doc complaints: ../drivers/greybus/es2.c:79: warning: bad line: ../drivers/greybus/es2.c:100: warning: cannot understand function prototype: 'struct es2_ap_dev ' es2.c:126: warning: Function parameter or member 'cdsi1_in_use' not described in 'es2_ap_dev' Signed-off-by: Randy Dunlap <rdunlap(a)infradead.org> Cc: Johan Hovold <johan(a)kernel.org> Cc: Alex Elder <elder(a)kernel.org> Cc: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> Cc: greybus-dev(a)lists.linaro.org (moderated for non-subscribers) --- drivers/greybus/es2.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) --- linux-next-20210414.orig/drivers/greybus/es2.c +++ linux-next-20210414/drivers/greybus/es2.c @@ -72,11 +72,11 @@ struct es2_cport_in { }; /** - * es2_ap_dev - ES2 USB Bridge to AP structure + * struct es2_ap_dev - ES2 USB Bridge to AP structure * @usb_dev: pointer to the USB device we are. * @usb_intf: pointer to the USB interface we are bound to. * @hd: pointer to our gb_host_device structure - + * * @cport_in: endpoint, urbs and buffer for cport in messages * @cport_out_endpoint: endpoint for for cport out messages * @cport_out_urb: array of urbs for the CPort out messages @@ -85,7 +85,7 @@ struct es2_cport_in { * @cport_out_urb_cancelled: array of flags indicating whether the * corresponding @cport_out_urb is being cancelled * @cport_out_urb_lock: locks the @cport_out_urb_busy "list" - * + * @cdsi1_in_use: true if cport CDSI1 is in use * @apb_log_task: task pointer for logging thread * @apb_log_dentry: file system entry for the log file interface * @apb_log_enable_dentry: file system entry for enabling logging

4 years, 6 months

[PATCH] staging: greybus: Match parentheses alignment

by Zhansaya Bagdauletkyzy

Match next line with open parentheses by adding tabs/spaces to conform with Linux kernel coding style. Reported by checkpatch. Signed-off-by: Zhansaya Bagdauletkyzy <zhansayabagdaulet(a)gmail.com> --- drivers/staging/greybus/camera.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/staging/greybus/camera.c b/drivers/staging/greybus/camera.c index cdbb42cd413b..5dca585694c0 100644 --- a/drivers/staging/greybus/camera.c +++ b/drivers/staging/greybus/camera.c @@ -220,7 +220,7 @@ static int gb_camera_operation_sync_flags(struct gb_connection *connection, } static int gb_camera_get_max_pkt_size(struct gb_camera *gcam, - struct gb_camera_configure_streams_response *resp) + struct gb_camera_configure_streams_response *resp) { unsigned int max_pkt_size = 0; unsigned int i; @@ -378,8 +378,8 @@ struct ap_csi_config_request { #define GB_CAMERA_CSI_CLK_FREQ_MARGIN 150000000U static int gb_camera_setup_data_connection(struct gb_camera *gcam, - struct gb_camera_configure_streams_response *resp, - struct gb_camera_csi_params *csi_params) + struct gb_camera_configure_streams_response *resp, + struct gb_camera_csi_params *csi_params) { struct ap_csi_config_request csi_cfg; struct gb_connection *conn; @@ -783,8 +783,8 @@ static ssize_t gb_camera_op_capabilities(void *priv, char *data, size_t len) } static int gb_camera_op_configure_streams(void *priv, unsigned int *nstreams, - unsigned int *flags, struct gb_camera_stream *streams, - struct gb_camera_csi_params *csi_params) + unsigned int *flags, struct gb_camera_stream *streams, + struct gb_camera_csi_params *csi_params) { struct gb_camera *gcam = priv; struct gb_camera_stream_config *gb_streams; -- 2.25.1

4 years, 6 months

[PATCH] staging: greybus: move to use request_irq by IRQF_NO_AUTOEN flag

by Tian Tao

disable_irq() after request_irq() still has a time gap in which interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will disable IRQ auto-enable because of requesting. this patch is made base on "add IRQF_NO_AUTOEN for request_irq" which is being merged: https://lore.kernel.org/patchwork/patch/1388765/ Signed-off-by: Tian Tao <tiantao6(a)hisilicon.com> --- drivers/staging/greybus/arche-platform.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/greybus/arche-platform.c b/drivers/staging/greybus/arche-platform.c index e374dfc..be27ace 100644 --- a/drivers/staging/greybus/arche-platform.c +++ b/drivers/staging/greybus/arche-platform.c @@ -500,13 +500,13 @@ static int arche_platform_probe(struct platform_device *pdev) arche_platform_wd_irq, arche_platform_wd_irq_thread, IRQF_TRIGGER_FALLING | - IRQF_TRIGGER_RISING | IRQF_ONESHOT, + IRQF_TRIGGER_RISING | IRQF_ONESHOT | + IRQF_NO_AUTOEN, dev_name(dev), arche_pdata); if (ret) { dev_err(dev, "failed to request wake detect IRQ %d\n", ret); return ret; } - disable_irq(arche_pdata->wake_detect_irq); ret = device_create_file(dev, &dev_attr_state); if (ret) { -- 2.7.4

4 years, 6 months

[PATCH 00/16] tty: TIOCSSERIAL fixes and clean ups

by Johan Hovold

TIOCSSERIAL is a horrid, underspecified, legacy interface which for most serial devices is only useful for setting the close_delay and closing_wait parameters. This series fixes up the various ways in which driver authors have gotten the implementation wrong over the years, like, for example, jiffies conversions, permissions checks and error handling. The de-facto standard for error handling is to ignore any unsupported features and immutable parameters (cf. UPF_FIXED_PORT and deprecated ASYNC flags). Permission checking should prevent an unprivileged user from changing anything but the ASYNC_USR flags (and custom divisor) by returning -EPERM. These patches are against tty-next, but the staging ones could otherwise go through either tree. I'll be sending the corresponding USB fixes separately. Johan Johan Hovold (16): staging: fwserial: fix TIOCSSERIAL jiffies conversions staging: fwserial: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL implementation staging: fwserial: fix TIOCGSERIAL implementation staging: greybus: uart: fix TIOCSSERIAL jiffies conversions staging: greybus: uart: fix unprivileged TIOCCSERIAL staging: greybus: uart: clean up TIOCGSERIAL tty: amiserial: fix TIOCSSERIAL permission check tty: amiserial: add missing TIOCSSERIAL jiffies conversions tty: moxa: fix TIOCSSERIAL jiffies conversions tty: moxa: fix TIOCSSERIAL permission check tty: moxa: fix TIOCSSERIAL implementation tty: mxser: fix TIOCSSERIAL jiffies conversions tty: mxser: fix TIOCSSERIAL permission check pcmcia: synclink_cs: drop redundant tty-port initialisation tty: synclink_gt: drop redundant tty-port initialisation drivers/char/pcmcia/synclink_cs.c | 2 -- drivers/staging/fwserial/fwserial.c | 19 +++++++++--------- drivers/staging/greybus/uart.c | 16 +++++++-------- drivers/tty/amiserial.c | 25 +++++++++++++++++------ drivers/tty/moxa.c | 21 +++++++++---------- drivers/tty/mxser.c | 31 ++++++++++++++++++++--------- drivers/tty/synclink_gt.c | 2 -- 7 files changed, 68 insertions(+), 48 deletions(-) -- 2.26.3

4 years, 6 months

← Newer
1
...
28
29
30
31
32
33
34
...
60
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

greybus-dev