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: Thu, 15 May 2025 09:52:29 +0200 [thread overview]
Message-ID: <2025051549-flannels-lively-a46d@gregkh> (raw)
In-Reply-To: <87o6vutrbw.wl-kuninori.morimoto.gx@renesas.com>
On Thu, May 15, 2025 at 04:45:23AM +0000, Kuninori Morimoto wrote:
>
> Hi Greg / UIO / DT
>
> I would like to ask about UIO vs DT.
>
> If my understanding was correct, current UIO can use 1 IRQ / 1 reg per 1 UIO,
> but some device needs multi-IRQ/reg. In such case, we need to use
> multi-UIO. But it is not good much to DT rule. 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?
thanks,
greg k-h
next prev parent reply other threads:[~2025-05-15 7:54 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 [this message]
2025-05-16 2:18 ` Kuninori Morimoto
2025-05-16 6:03 ` Greg KH
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=2025051549-flannels-lively-a46d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.