public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: bingbu.cao@intel.com
Cc: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
	djrscally@gmail.com, bingbu.cao@linux.intel.com
Subject: Re: [PATCH] media: ipu3-cio2: support multiple sensors and VCMs with HID name
Date: Mon, 6 Mar 2023 13:26:44 +0200	[thread overview]
Message-ID: <ZAXN9EszoxHt+F7w@smile.fi.intel.com> (raw)
In-Reply-To: <20230303144432.2108677-1-bingbu.cao@intel.com>

On Fri, Mar 03, 2023 at 10:44:32PM +0800, bingbu.cao@intel.com wrote:
> From: Bingbu Cao <bingbu.cao@intel.com>
> 
> In current cio2-bridge, it is using the hid as node name to register
> software node and swnode will create kobject and sysfs entry with
> the node name, if there are multiple sensors and VCMs which are sharing
> same HID name, it will cause the software nodes registration failure:
> 
> [ 7.142311] sysfs: cannot create duplicate filename '/kernel/software_nodes/dw9714'
> ...
> [ 7.142328] Call Trace:
> [ 7.142330]  <TASK>
> [ 7.142336]  dump_stack_lvl+0x49/0x63
> [ 7.142341]  dump_stack+0x10/0x16
> [ 7.142343]  sysfs_warn_dup.cold+0x17/0x2b
> [ 7.142346]  sysfs_create_dir_ns+0xbc/0xd0
> [ 7.142351]  kobject_add_internal+0xb1/0x2b0
> [ 7.142356]  kobject_init_and_add+0x71/0xa0
> [ 7.142360]  swnode_register+0x136/0x210
> [ 7.142363]  software_node_register+0xd2/0x120
> [ 7.142364]  software_node_register_nodes+0x83/0xf0
> [ 7.142366]  ? acpi_get_physical_device_location+0x65/0xc0
> [ 7.142371]  cio2_bridge_init+0x82a/0xb5e
> ...
> [ 7.142448] kobject_add_internal failed for dw9714 with -EEXIST,
> don't try to register things with the same name in the same directory.

Please cut unneeded context of the backtrace as it's explained in the
Submitting Patches documentation.

> One solution is appending the sensor link(Mipi Port) in SSDB as suffix
> of the node name to fix this problem.

...

> +	if (sensor->ssdb.vcmtype) {
> +		scnprintf(vcm_name, sizeof(vcm_name), "%s-%u",
> +			  cio2_vcm_types[sensor->ssdb.vcmtype - 1],
> +			  sensor->ssdb.link);

Is using 'c' variant a cargo cult? Otherwise explain, why dropping the last
part of the number is not a problem.

> +		nodes[SWNODE_VCM] = NODE_VCM(vcm_name);
> +	}

...

> +		scnprintf(sensor->name, sizeof(sensor->name), "%s-%u",
> +			  cfg->hid, sensor->ssdb.link);


Ditto.

...

> -	char name[ACPI_ID_LEN];
> +	char name[ACPI_ID_LEN + 4];

Why 4 is chosen? This needs an explanation.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-03-06 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 14:44 [PATCH] media: ipu3-cio2: support multiple sensors and VCMs with HID name bingbu.cao
2023-03-06 11:26 ` Andy Shevchenko [this message]
2023-03-06 13:33   ` Cao, Bingbu
2023-03-06 16:35     ` Andy Shevchenko
2023-03-07  2:43       ` Bingbu Cao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZAXN9EszoxHt+F7w@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bingbu.cao@intel.com \
    --cc=bingbu.cao@linux.intel.com \
    --cc=djrscally@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox