pdr_add_lookup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so welcome to pdr_add_lookup(9), bestie β€” that's the page title, and this whole thing lives in the Kernel API Manual ✨. This function is literally here to register a tracking request for a PD. slay.

🌸 SYNOPSIS 🌸

struct pdr_service * pdr_add_lookup (struct pdr_handle *pdr , const char *service_name , const char *service_path );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • pdr β€” the PDR client handle, iconic.
  • service_name β€” the service name of the tracking request.
  • service_path β€” the service path of the tracking request.

πŸŽ€ DESCRIPTION πŸŽ€

Registering a pdr lookup is the move that lets you track the life cycle of the PD. that's it, that's the whole point, and it's lowkey important. πŸ‘‘

πŸ’… RETURN πŸ’…

  • success β†’ a pdr_service object πŸŽ‰
  • failure β†’ ERR_PTR 😭
  • already in progress? β†’ -EALREADY is returned if a lookup is already in progress for the given service path. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/soc/qcom/pdr_interface.c says hi, bestie β€” go peek at:


that's the whole page, bestie β€” source/version: ./drivers/soc/qcom; date: October 2026. xoxo, go track those PDs responsibly πŸ’–

πŸ“¦ where this page comes from