From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Sergey Shtylyov <s.shtylyov@omp.ru>,
Rich Felker <dalias@libc.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: [PATCH] sh: avoid using IRQ0 on SH3/4
Date: Fri, 11 Feb 2022 21:30:31 +0100 [thread overview]
Message-ID: <dde846f0-1324-7fde-ef92-eb72d4200b50@physik.fu-berlin.de> (raw)
In-Reply-To: <63f06bf0-fc7b-3c5c-8af9-5adfd7628354@omp.ru>
Hi Sergey!
On 2/11/22 21:28, Sergey Shtylyov wrote:
> On 2/11/22 11:15 PM, Sergey Shtylyov wrote:
>
>> Using IRQ0 by the platform devices is going to be disallowed soon (see [1])
>> and the code supporting SH3/4 SoCs maps the IRQ #s starting at 0 -- modify
>> that code to start the IRQ #s from 16 instead.
>>
>> [1] https://lore.kernel.org/all/5e001ec1-d3f1-bcb8-7f30-a6301fd9930c@omp.ru/
>>
>> Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
>>
>> ---
>> The patch is against Linus Torvalds' 'linux.git' repo.
>>
>> arch/sh/kernel/cpu/sh3/entry.S | 4 ++--
>> include/linux/sh_intc.h | 6 +++---
>> 2 files changed, 5 insertions(+), 5 deletions(-)
>>
>> Index: linux/arch/sh/kernel/cpu/sh3/entry.S
>> ===================================================================
>> --- linux.orig/arch/sh/kernel/cpu/sh3/entry.S
>> +++ linux/arch/sh/kernel/cpu/sh3/entry.S
>> @@ -470,9 +470,9 @@ ENTRY(handle_interrupt)
>> mov r4, r0 ! save vector->jmp table offset for later
>>
>> shlr2 r4 ! vector to IRQ# conversion
>> - add #-0x10, r4
>>
>> - cmp/pz r4 ! is it a valid IRQ?
>> + mov #0x10, r5
>> + cmp/ge r5, r4 ! is it a valid IRQ?
>
> Maybe I should've used cmp/hs... my 1st try at SH assembly! :-)
I can test your revised patch next week on my SH7785LCR.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2022-02-11 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 20:15 Sergey Shtylyov
2022-02-11 20:28 ` Sergey Shtylyov
2022-02-11 20:30 ` John Paul Adrian Glaubitz [this message]
2022-02-11 20:46 ` Sergey Shtylyov
2022-02-11 21:14 ` John Paul Adrian Glaubitz
2022-02-25 19:28 ` Sergey Shtylyov
2022-02-26 8:07 ` John Paul Adrian Glaubitz
2022-03-02 9:31 ` Sergey Shtylyov
2022-03-02 9:43 ` John Paul Adrian Glaubitz
2022-03-02 10:10 ` John Paul Adrian Glaubitz
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=dde846f0-1324-7fde-ef92-eb72d4200b50@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®