public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
	devicetree@vger.kernel.org,
	shimoda <yoshihiro.shimoda.uh@renesas.com>,
	goda <yusuke.goda.sx@renesas.com>,
	Kurokawa <harunobu.kurokawa.dn@renesas.com>,
	Kihara <takeshi.kihara.df@renesas.com>,
	kazuya.mizuguchi.ks@renesas.com, takamitsu.honda.pv@renesas.com
Subject: Re: Question about UIO vs DT
Date: Fri, 16 May 2025 08:03:27 +0200	[thread overview]
Message-ID: <2025051649-commode-brussels-1034@gregkh> (raw)
In-Reply-To: <871pspti1t.wl-kuninori.morimoto.gx@renesas.com>

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

  reply	other threads:[~2025-05-16  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15  4:45 Question about UIO vs DT Kuninori Morimoto
2025-05-15  7:52 ` Greg KH
2025-05-16  2:18   ` Kuninori Morimoto
2025-05-16  6:03     ` Greg KH [this message]
2025-05-16  7:05       ` Kuninori Morimoto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2025051649-commode-brussels-1034@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=devicetree@vger.kernel.org \
    --cc=harunobu.kurokawa.dn@renesas.com \
    --cc=kazuya.mizuguchi.ks@renesas.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=takamitsu.honda.pv@renesas.com \
    --cc=takeshi.kihara.df@renesas.com \
    --cc=yoshihiro.shimoda.uh@renesas.com \
    --cc=yusuke.goda.sx@renesas.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox