[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025051649-commode-brussels-1034@gregkh>
Date: Fri, 16 May 2025 08:03:27 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
Cc: Linux-Kernel <linux-kernel@...r.kernel.org>, devicetree@...r.kernel.org,
shimoda <yoshihiro.shimoda.uh@...esas.com>,
goda <yusuke.goda.sx@...esas.com>,
Kurokawa <harunobu.kurokawa.dn@...esas.com>,
Kihara <takeshi.kihara.df@...esas.com>,
kazuya.mizuguchi.ks@...esas.com, takamitsu.honda.pv@...esas.com
Subject: Re: Question about UIO vs DT
On Fri, May 16, 2025 at 02:18:07AM +0000, Kuninori Morimoto wrote:
>
> Hi Greg
>
> Thank you for the reply
>
> > > For example in case of
> > > the device which needs "2 regs 3 irqs". it will be
> > >
> > > (A) [1 reg, 1 IRQ] UIO
> > > (B) [1 reg, 1 IRQ] UIO
> > > (C) [0 reg, 1 IRQ] UIO
> > >
> > > and (C) will be DT error. Is this known issue ? Do we have better solution ?
> >
> > Yes, write a real driver for the device as obviously it is a complex one
> > and UIO shouldn't be used for it :)
> >
> > What type of device is this that requires this type of hardware control
> > and why do you feel that UIO is the proper solution?
>
> One of big reason is license.
> Because it needs to be proprietary licensed driver, we can't create
> real driver.
That is not a valid reason at all, sorry. So much so that I, and many
others, have argued that you can not have UIO drivers in userspace that
are NOT also released under the GPLv2.
Go work with your lawyers please, there's nothing I can now do to help
you out with this due to the expectation that you are attempting to
evade the license requirements here.
greg k-h
Powered by blists - more mailing lists