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
F100481430: D38163.diff
Wed, Oct 16, 12:01 AM
Unknown Object (File)
Fri, Oct 11, 7:29 AM
Unknown Object (File)
Fri, Oct 11, 7:28 AM
Unknown Object (File)
Thu, Oct 3, 4:26 PM
Unknown Object (File)
Thu, Oct 3, 1:29 PM
Unknown Object (File)
Tue, Oct 1, 2:12 AM
Unknown Object (File)
Wed, Sep 25, 2:32 PM
Unknown Object (File)
Sun, Sep 22, 5:15 PM

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