lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <871pspti1t.wl-kuninori.morimoto.gx@renesas.com>
Date: Fri, 16 May 2025 02:18:07 +0000
From: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To: Greg KH <gregkh@...uxfoundation.org>
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


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.

Our team is thinking it will be no more DT error if UIO can allow
below, somehow.

	reg = <reg1 reg2>;
	interrupts = <irq1 irq2 irq3>;

Thank you for your help !!

Best regards
---
Kuninori Morimoto

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ