[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025090509-stoppable-contrite-13ae@gregkh>
Date: Fri, 5 Sep 2025 12:32:45 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Sakari Ailus <sakari.ailus@....fi>
Cc: linux-doc@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Madhavan Srinivasan <maddy@...ux.ibm.com>,
Haren Myneni <haren@...ux.ibm.com>,
Bagas Sanjaya <bagasdotme@...il.com>,
Andrew Donnellan <ajd@...ux.ibm.com>,
Michael Ellerman <mpe@...erman.id.au>,
Akshay Gupta <akshay.gupta@....com>, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, hans@...erkuil.nl,
laurent.pinchart@...asonboard.com,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Lee Jones <lee@...nel.org>
Subject: Re: [PATCH v2 0/3] Document Media Controller IOCTL number assignments
On Fri, Sep 05, 2025 at 01:25:33PM +0300, Sakari Ailus wrote:
> Hi Jonathan, Greg, Miguel, others,
>
> On Tue, May 27, 2025 at 08:56:45AM +0300, Sakari Ailus wrote:
> > Hello all,
> >
> > The Media Controller uses IOCTL numbers with '|' type up to 0x81 but the
> > range from 0x80 upwards is documented to belong to samples. The samples,
> > however, are currently using these values. Solve the problem by bumping
> > the top of the MC range and the samples allocation by 0x10 as the samples
> > don't require a stable IOCTL interface.
>
> Could you comment on this, please?
Why not just live with the overlap? What problem is this causing? It's
the MC subsystem's "bug" in that it took over an ioctl range that was
already documented as being used by something else :)
thanks,
greg k-h
Powered by blists - more mailing lists