Page MenuHomeFreeBSD

linuxkpi: Define `dev_is_platform()` and `to_platform_device()`
ClosedPublic

Authored by dumbbell on Jan 22 2023, 2:14 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Dec 21, 1:43 PM
Unknown Object (File)
Mon, Dec 16, 11:37 PM
Unknown Object (File)
Sat, Dec 7, 10:46 PM
Unknown Object (File)
Nov 26 2024, 9:33 PM
Unknown Object (File)
Nov 17 2024, 8:56 AM
Unknown Object (File)
Nov 14 2024, 1:42 AM
Unknown Object (File)
Oct 21 2024, 8:08 AM
Unknown Object (File)
Oct 16 2024, 12:01 AM

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

What do they do exactly in Linux ?

In D38163#866986, @manu wrote:

What do they do exactly in Linux ?

I'm not sure I understand the concept, so let me copy/paste the comment in Documentation/driver-api/driver-model/platform.rst:

Platform devices are devices that typically appear as autonomous
entities in the system. This includes legacy port-based devices and
host bridges to peripheral buses, and most controllers integrated
into system-on-chip platforms.  What they usually have in common
is direct addressing from a CPU bus.  Rarely, a platform_device will
be connected through a segment of some other kind of bus; but its
registers will still be directly addressable.

In the context of DRM, it is used in the support for VESA/EFI during early stages of the boot. The code is not called on FreeBSD.

Ok, good to me then, but please add in the commit message that those are no-op just to satisfy drm compiling.

This revision is now accepted and ready to land.Jan 28 2023, 8:31 AM