Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 129
    • Issues 129
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 23
    • Merge requests 23
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Librem5
  • linux
  • Issues
  • #382
Closed
Open
Created Dec 15, 2021 by Martin Kepplinger@martin.kepplingerOwner

make the wwan driver listen to 4G_WAKE and wake the system

even in mainline we currently describe the 4G_WAKE pin as gpio-key for the devkit: https://elixir.bootlin.com/linux/latest/source/arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dts#L53 and we want to do the same for the phone.

but that looks like a short-term workaround: the KEY_PHONE describes a physical key that starts a phone application (afaik). This is not what's happening here and not what we have on the phone (or devkit).

so the wwan driver should look at this pin and wake the system on incoming calls and sms instead, right?

Edited Dec 15, 2021 by Martin Kepplinger
Assignee
Assign to
Time tracking