Deprecate `emul_get_binding`

[alevkoy]

Is your enhancement proposal related to a problem? Please describe.
EMUL_DT_GET will provide a mechanism to statically get a reference to a struct emul based on the device tree. Generally, it should be possible and preferable to get emulator references statically. emul_get_binding currently provides a mechanism to get them dynamically.

Describe the solution you'd like
Deprecate emul_get_binding. Provide a function struct emul *emul_get_device(struct device *), which will dynamically get the emulator corresponding to a specified device.

Describe alternatives you've considered

• Continue to use emul_get_binding: This is potentially time-consuming and can fail at runtime.
• Something about not having emul_get_device, to be elaborated by @galak.

Additional context
See request from @galak in #44883 (comment).

@galak Did I miss anything? Is that what you were thinking for emul_get_device? What is the use case for emul_get_device?

[alevkoy]

@galak Can you flesh out how you wanted emul_get_device to work?

[galak]

@galak Can you flesh out how you wanted emul_get_device to work?

I think something like:

const struct emul *emul_get_dev(const struct device *dev)
{
	const struct emul *emul_it;

	for (emul_it = __emul_list_start; emul_it < __emul_list_end; emul_it++) {
		if (emul_it->dev == dev) {
			return emul_it;
		}
	}

	return NULL;
}

[galak]

I think we can mark emul_get_binding deprecated now. Its only if you guys need a runtime mechanism do we need to add emul_get_dev

[alevkoy]

@yperess I think you had thoughts on this previously, but I can't remember what they were.

[yperess]

@yperess I think you had thoughts on this previously, but I can't remember what they were.

I'm good with this, had a chat with Kumar offline and we have a good path forward if we end up needing a dynamic lookup later on

[zephyrbot]

Hi @yperess,

This issue, marked as an Enhancement, was opened a while ago and did not get any traction. It was just assigned to you based on the labels. If you don't consider yourself the right person to address this issue, please re-assing it to the right person.

Please take a moment to review if the issue is still relevant to the project. If it is, please provide feedback and direction on how to move forward. If it is not, has already been addressed, is a duplicate, or is no longer relevant, please close it with a short comment explaining the reason.

@alevkoy you are also encouraged to help moving this issue forward by providing additional information and confirming this request/issue is still relevant to you.

Thanks!