Skip to content

qteesupplicant.service: make it conditional to /dev/tee0#52

Open
Ricardo Salveti (ricardosalveti) wants to merge 1 commit into
qualcomm:mainfrom
ricardosalveti:qtee
Open

qteesupplicant.service: make it conditional to /dev/tee0#52
Ricardo Salveti (ricardosalveti) wants to merge 1 commit into
qualcomm:mainfrom
ricardosalveti:qtee

Conversation

@ricardosalveti

Copy link
Copy Markdown

Remove bindsto and after dev-tee0.device and replace with a conditional in order for systemd to not force a wait timeout on devices without the tee device node.

Remove bindsto and after dev-tee0.device and replace with a conditional
in order for systemd to not force a wait timeout on devices without the
tee device node.

Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
@ricardosalveti Ricardo Salveti (ricardosalveti) changed the title qteesupplicant: make it conditional to /dev/tee0 qteesupplicant.service: make it conditional to /dev/tee0 Apr 14, 2026
Description=QTEE Supplicant Service
BindsTo=dev-tee0.device
After=dev-tee0.device sfsconfig.service
ConditionPathExists=/dev/tee0

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Does this mean that the After= dependency is not needed at all? Since QCOMTEE is an in-built module, a successful probe of it will always happen before this systemd unit starts? So qteesupplicant is guaranteed to run in scenarios where QCOMTEE probe is success and silently skipped when fails?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

We might be able to keep the After line, I will check, the main issue is really with BindsTo as that will force a dependency and will cause this service to be stuck (will fail after it timeouts) on devices without /dev/tee0.

@harshaldev27 Harshal Dev (harshaldev27) Apr 16, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yes understood. Then let's keep the After= if it's not causing any issues when /dev/tee0 is not available. When tee0 is available it's good to enforce that qteesupplicant start only happens after tee0 appears, otherwise qtee-supplicant start should be skipped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants