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]
Date:	Wed, 3 Aug 2016 21:57:26 +0200
From:	Marek Vasut <marex@...x.de>
To:	Ksenija Stanojević <ksenija.stanojevic@...il.com>
Cc:	Fabio Estevam <festevam@...il.com>,
	Stefan Wahren <stefan.wahren@...e.com>,
	Lee Jones <lee.jones@...aro.org>, linux-input@...r.kernel.org,
	Peter Meerwald-Stadler <pmeerw@...erw.net>,
	Jonathan Cameron <jic23@...nel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Hartmut Knaack <knaack.h@....de>,
	Lars-Peter Clausen <lars@...afoo.de>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Fabio Estevam <fabio.estevam@...escale.com>,
	linux-iio@...r.kernel.org, Harald Geyer <harald@...ib.org>
Subject: Re: [PATCH v3 1/4] mfd: mxs-lradc: Add support for mxs-lradc MFD

On 08/03/2016 09:45 PM, Ksenija Stanojević wrote:
> On Wed, Aug 3, 2016 at 9:39 PM, Marek Vasut <marex@...x.de> wrote:
>> On 08/03/2016 09:34 PM, Ksenija Stanojević wrote:
>>> On Wed, Aug 3, 2016 at 9:13 PM, Marek Vasut <marex@...x.de> wrote:
>>>> On 08/03/2016 06:45 PM, Ksenija Stanojević wrote:
>>>>> Hi Fabio,
>>>>
>>>> Hi,
>>>>
>>>>> On Wed, Aug 3, 2016 at 6:35 PM, Fabio Estevam <festevam@...il.com> wrote:
>>>>>> Hi Ksenija,
>>>>>>
>>>>>> On Wed, Aug 3, 2016 at 1:32 PM, Ksenija Stanojević
>>>>>> <ksenija.stanojevic@...il.com> wrote:
>>>>>>
>>>>>>> Can someone with imx23 board send me /proc/interrupts log, I
>>>>>>> need irq numbers...
>>>>>>
>>>>>> Can't you get them from the MX23 Reference Manual (Table 5-1. i.MX23
>>>>>> Interrupt Sources)?
>>>>>
>>>>> I thought it will be more reliable if I asked someone, since numbers from MX28
>>>>> manual don't match with /proc/interrupts log.
>>>>>
>>>> What do you mean they don't match ? Please elaborate.
>>>
>>> irqs don't have the same values in Table 5.1 in MX28 manual and in
>>> /proc/interrupts
>>> output.
>>>
>>> For example:
>>> touchscreen irq in MX28 manual have these values:
>>> 10 (source number) and 0x0028 (vector number)
>>>
>>> in /proc/interrupts:
>>> 210:          0         -  10 Edge      mxs-lradc-touchscreen
>>
>> I see lradc_touch_irq in the MX28RM is IRQ 10 and it is also 10 in your
>> /proc/interrupts output . What am I missing ?
> 
> I was referring to the number of the first column 210, that's the number that
> I need and cannot find in the Table of the manual.

The first number in /proc/interrupts is the number which Linux maps to
that particular IRQ line, but that number can be anything, it does not
(need to) match the hardware in any way. What do you need it for ?

-- 
Best regards,
Marek Vasut

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ