Re: [PATCH RFC v2 05/19] drm/panel: embed a drm_bridge into every drm_panel

[Jani Nikula]

On Wed, 09 Sep 2026, Maxime Ripard <mripard@xxxxxxxxxx> wrote:
> On Wed, Sep 09, 2026 at 05:02:58PM +0300, Jani Nikula wrote:
>> On Wed, 09 Sep 2026, Maxime Ripard <mripard@xxxxxxxxxx> wrote:
>> > I really wish i915 was at least *trying* to fit within the larger model
>> > basically everybody else uses. I understand that it's a large
>> > undertaking and regression prone and everything, but I'm also concerned
>> > about having the "we can't because of i915" or "supported by everybody
>> > else but i915" on a regular basis now.
>> 
>> Okay, let's hear it, please name a few things where i915 is alone in
>> doing something bonkers that amd, radeon, nouveau also don't do, and
>> what would be the changes that would bring i915 closer to everybody
>> else?
>
> Where did I say "bonkers"?
>
> But since you're asking, because it doesn't implement .reset, we had that
> conversation this week for
>
> https://lore.kernel.org/r/20260908-drm-reset-state-flag-v3-0-905570f387a4@xxxxxxxxxx

You mean struct drm_crtc_funcs .reset?

-- 
Jani Nikula, Intel