On Wed, Jan 17, 2024 at 12:58:15PM +0000, Andri Yngvason wrote: > mið., 17. jan. 2024 kl. 09:21 skrifaði Pekka Paalanen <ppaalanen@xxxxxxxxx>: > > > > On Tue, 16 Jan 2024 14:11:43 +0000 > > Andri Yngvason <andri@xxxxxxxxxxx> wrote: > > > > > þri., 16. jan. 2024 kl. 13:29 skrifaði Sebastian Wick > > > <sebastian.wick@xxxxxxxxxx>: > > > > > > > > On Tue, Jan 16, 2024 at 01:13:13PM +0000, Andri Yngvason wrote: > > > [...] > > > > > şri., 16. jan. 2024 kl. 11:42 skrifaği Sebastian Wick > > > > > <sebastian.wick@xxxxxxxxxx>: > > > > > > > > > > > > On Mon, Jan 15, 2024 at 04:05:52PM +0000, Andri Yngvason wrote: > > > > > > > From: Werner Sembach <wse@xxxxxxxxxxxxxxxxxxx> > > > > > > > > > > > > > > Add a new general drm property "force color format" which can be used > > > > > > > by userspace to tell the graphics driver which color format to use. > > > > > > > > > > > > I don't like the "force" in the name. This just selects the color > > > > > > format, let's just call it "color format" then. > > > > > > > > > > > > > > > > In previous revisions, this was "preferred color format" and "actual > > > > > color format", of which the latter has been dropped. I recommend > > > > > reading the discussion for previous revisions. > > > > > > > > Please don't imply that I didn't read the thread I'm answering to. > > > > FYI, I have not read this thread. > > > > pq, You did not read this summary? > https://lore.kernel.org/dri-devel/CAFNQBQwjeJaX6B4oewpgASMUd5_nxZYMxUfdOG294CTVGBTd1w@xxxxxxxxxxxxxx/ > > You partook in the discussion on IRC. Please read it and tell me if I > misunderstood anything. > > Sebastian, I apologise. You clearly read it as you even replied to it! Thank you :) > > > > > > > > > There are arguments for adding "actual color format" later and if it > > > > > is added later, we'd end up with "color format" and "actual color > > > > > format", which might be confusing, and it is why I chose to call it > > > > > "force color format" because it clearly communicates intent and > > > > > disambiguates it from "actual color format". > > > > > > > > There is no such thing as "actual color format" in upstream though. > > > > Basing your naming on discarded ideas is not useful. The thing that sets > > > > the color space for example is called "Colorspace", not "force > > > > colorspace". > > > > > > > > > > Sure, I'm happy with calling it whatever people want. Maybe we can > > > have a vote on it? > > > > It would sound strange to say "force color format" = "auto". Just drop > > the "force" of it. > > > > If and when we need the feedback counterpart, it could be an immutable > > prop called "active color format" where "auto" is not a valid value, or > > something in the new "output properties" design Sima has been thinking > > of. > > There seems to be consensus for calling it "color format" > > > > > > > > [...] > > > > > > > @@ -1396,6 +1404,15 @@ static const u32 dp_colorspaces = > > > > > > > * drm_connector_attach_max_bpc_property() to create and attach the > > > > > > > * property to the connector during initialization. > > > > > > > * > > > > > > > + * force color format: > > > > > > > + * This property is used by userspace to change the used color format. When > > > > > > > + * used the driver will use the selected format if valid for the hardware, > > > > > > > > > > > > All properties are always "used", they just can have different values. > > > > > > You probably want to talk about the auto mode here. > > > > > > > > > > Maybe we can say something like: If userspace does not set the > > > > > property or if it is explicitly set to zero, the driver will select > > > > > the appropriate color format based on other constraints. > > > > > > > > The property can be in any state without involvement from user space. > > > > Don't talk about setting it, talk about the state it is in: > > > > > > > > When the color format is auto, the driver will select a format. > > > > > > > > > > Ok. > > > > > > > > > > > > > > > > + * sink, and current resolution and refresh rate combination. Drivers to > > > > > > > > > > > > If valid? So when a value is not actually supported user space can still > > > > > > set it? What happens then? How should user space figure out if the > > > > > > driver and the sink support the format? > > > > > > > > > > The kernel does not expose this property unless it's implemented in the driver. > > > > > > > > If the driver simply doesn't support *one format*, the enum value for > > > > that format should not be exposed, period. This isn't about the property > > > > on its own. > > > > > > Right, understood. You mean that enum should only contain values that > > > are supported by the driver. > > > > Yes. When a driver installs a property, it can choose which of the enum > > entries are exposed. That cannot be changed later though, so the list > > cannot live by the currently connected sink, only by what the driver > > and display controlled could ever do. > > Yes, and I think that basing it also on the connected sink's > capabilities would just add complexity for very little gain. In fact, > I think that limiting it based on the driver's capabilities is also > over-engineering, but I don't mind adding it if that's what people > really want. Having a bunch of values that will always fail a mode set just makes life for user space much worse. Might be overengineering from the kernel pov but it's not for user space. > > > > > > > This was originally "preferred color format". Perhaps the > > > > > documentation should better reflect that it is now a mandatory > > > > > constraint which fails the modeset if not satisfied. > > > > > > > > That would definitely help. > > > > > > > > > > > > > > > > For the Colorspace prop, the kernel just exposes all formats it supports > > > > > > (independent of the sink) and then makes it the job of user space to > > > > > > figure out if the sink supports it. > > > > > > > > > > > > The same could be done here. Property value is exposed if the driver > > > > > > supports it in general, commits can fail if the driver can't support it > > > > > > for a specific commit because e.g. the resolution or refresh rate. User > > > > > > space must look at the EDID/DisplayID/mode to figure out the supported > > > > > > format for the sink. > > > > > > > > > > Yes, we can make it possible for userspace to discover which modes are > > > > > supported by the monitor, but there are other constraints that need to > > > > > be satisfied. This was discussed in the previous revision. > > > > > > > > I mean, yes, that's what I said. User space would then only be > > > > responsible for checking the sink capabilities and the atomic check > > > > would take into account other (non-sink) constraints. > > > > > > Since we need to probe using TEST_ONLY anyway, we'll end up with two > > > mechanisms to do the same thing where one of them depends on the other > > > for completeness. > > > > What do you mean by "same thing"? > > I thought that it would be clear that I did not mean that they were > literally equal. This was discussed on IRC and summarised in the email > message that I linked to above. Excerpt: > "I asked if it made sense to add color format capabilities to the mode info > struct, but the conclusion was that it wouldn't really be useful because we > need TEST_ONLY anyway to see if the color format setting is compatible with > other settings." I feel like we're talking past each other. There are two questions: 1. Should the property expose enum values which will always result in a failed commit (because e.g. the hardware doesn't support it) 2. Should the commit fail if the sink doesn't claim to support the format The first issue I believe that we should try to minimize options that can't work to cut down on the combinatorial explosion problem. On the second issue, there are good reasons to just not fail commits in the kernel because: * user space already has to parse and understand EDIDs * this information is often wrong * support for new EDID/DisplayID can get to user space faster We have to decide on this and make them part of the API. We've seen how this gets a mess if that's not being done. > > > > Neither HDMI nor DisplayPort have a feedback message saying your > > infoframe contents are unacceptable, that I know of. Even if there was, > > it would come too late for failing the atomic commit ioctl in > > non-blocking mode. > > > > In general, display signalling is that you send whatever to the sink, > > and hope for the best. > > > > EDID is used to describe what the sink can accept, so in theory the > > kernel could parse EDID for all of these details and reject atomic > > commits that attempt unsupported configurations. However, EDID are also > > notoriously buggy. They are good for a best guess, but I believe it is > > useful to be able to try "unsupported" things. IIRC, PS VR2 > > intentionally lies for instance. > > > > Even if the kernel did reject everything based on EDID, the only way > > today for userspace to know what should work is to parse the EDID > > itself. TEST_ONLY trials lead to a combinatorial explosion too easily. > > So userspace is already expected to parse EDID, with the major > > exception being video mode lists that are explicitly provided by the > > kernel in UAPI. > > I thought that everyone agreed that display settings GUIs don't suffer > from combinatorial explosion because settings are selected in a > predefined order so they don't need to test all permutations. Not all permutations doesn't mean no permutations. This is still really expensive to do right. > > > > EDID and DisplayID standards also evolve. The kernel could be behind > > userspace in chasing them, which was the reason why the kernel does not > > validate HDR_OUTPUT_METADATA against EDID. > > > > The design of today with HDR_OUTPUT_METADATA and whatnot is > > that userspace is responsible for checking sink capabilities, and > > atomic check is responsible for driver and display controller > > capabilities. > > I'm not really sure where you're going with this. Are you for or > against userspace parsing EDID instead of getting the information from > the kernel? The opposite I hope. Sink capabilities shouldn't influence commits, let user space do what it can do. We have a bunch of "auto" states but I do consider them a mistake. > > > > > > > In any case, these things can be added later and need not be a part of > > > > > this change set. > > > > > > > > No, this is the contract between the kernel and user space and has to be > > > > figured out before we can merge new uAPI. > > > > Indeed. > > I don't see how adding something later to cut down on the > combinatorial explosion can possibly break any kind of contract in the > way things are currently implemented. Can anyone provide examples of > how things can go wrong in this particular instance? > > Thanks, > Andri >
