Skip to content

Conversation

@quic-lxu5
Copy link
Contributor

In case of default domain ID, the device open request falls back to DEFAUL_DEVICE which will be defined in the libs to which the application is linked. Remove this legacy fallback logic to avoid any confusion and unexpected observations.

@ekanshibu
Copy link
Contributor

Can you also clean-up the following:

  1. This function:
    static const char *get_default_device_name(int domain_id) {
  2. DEFAULT_DEVICE from here:
    name = DEFAULT_DEVICE;

    #define DEFAULT_DEVICE "/dev/fastrpc-adsp"

    name = DEFAULT_DEVICE;

return name;
}

static const char *get_default_device_name(int domain_id) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, I checked and this function cannot be removed. The reason is that some old platform use non-secure devices for daemons(if non-secure-domain property is added in DT).

You can just rename the function as get_non_secure_device_name and modify the default: case here.

static int fastrpc_wait_for_device(int domain)
{
int inotify_fd = -1, watch_fd = -1, err = 0;
const char *sec_dev_name = NULL, *def_dev_name = NULL;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

check for non-secure device also to maintain backward compatibility

In case of default domain ID, the device open request falls back to
DEFAUL_DEVICE which will be defined in the libs to which the application
is linked. Remove this legacy fallback logic to avoid any confusion
and unexpected observations.

Signed-off-by: Ling Xu <[email protected]>
@github-actions
Copy link

This pull request has been marked as stale due to 60 days of inactivity.

@github-actions github-actions bot added the Stale label Nov 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants