Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update screen mirroring in Infotainment.vspec #699

Closed
wants to merge 1 commit into from
Closed

Update screen mirroring in Infotainment.vspec #699

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions spec/Cabin/Infotainment.vspec
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,4 +267,27 @@ SmartphoneProjection.SupportedMode:
allowed: [ 'ANDROID_AUTO', 'APPLE_CARPLAY', 'MIRROR_LINK', 'OTHER' ]
description: Supportable list for projection.

SmartphoneScreenMirroring:
type: branch
description: All smartphone mirroring actions.

SmartphoneScreenMirroring.Active:
datatype: string
type: actuator
allowed: [ 'NONE', 'ACTIVE', 'INACTIVE' ]
description: Mirroring activation info.
comment: NONE indicates that mirroring is not supported.

SmartphoneScreenMirroring.Source:
datatype: string
type: actuator
allowed: ['USB', 'BLUETOOTH', 'WIFI']
description: Connectivity source selected for mirroring.

SmartphoneScreenMirroring.Resolution:
datatype: string
type: attribute
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this the physical resolution offered by the HMI, i.e. static, or is it the current resolution as agreed by receiver (Infotainment) and sending device?

One can in general discuss if the ScreenMirroring/SmartphoneProjection signals shall be sensor or actuators. I assume the actual setup/connection/pairing not will be managed by VSS so that VSS only is used for showing current status, and then all could be "sensors", but I have no problems calling them "actuators" either, in the end it all depends on implementation. But if this signal represents current resolution rather than static/constant display resolution the it should be "sensor" rather than "attribute".

allowed: ['RES_720P', 'RES_1080P', 'RES_4K']
description: Display resolution for the mirrored content.

#include include/PowerOptimize.vspec