linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] sh: avoid using IRQ0 on SH3/4
Date: Fri, 02 Jun 2023 11:01:06 +0200	[thread overview]
Message-ID: <1df63fac0075558850331210c28cb8fa534dc116.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <71105dbf-cdb0-72e1-f9eb-eeda8e321696@omp.ru>

Hi Sergey!

On Thu, 2023-06-01 at 23:22 +0300, Sergey Shtylyov wrote:
> IRQ0 is no longer returned by platform_get_irq() and its ilk -- they now
> return -EINVAL instead.  However, the kernel code supporting SH3/4 based
> SoCs still maps the IRQ #s starting at 0 -- modify that code to start the
> IRQ #s from 16 instead.
> 
> The patch should mostly affect the AP-SH4A-3A/AP-SH4AD-0A boards as they
> indeed are using IRQ0 for the SMSC911x compatible Ethernet chip...

I don't have time today, but I will look at all current SH patches over the
weekend. Thanks a lot for being so persistent.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2023-06-02  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 20:22 [PATCH v6] sh: avoid using IRQ0 on SH3/4 Sergey Shtylyov
2023-06-02  9:01 ` John Paul Adrian Glaubitz [this message]
2023-06-10  4:32 ` John Paul Adrian Glaubitz
2023-06-10 10:24   ` Sergei Shtylyov
2023-06-11  5:28     ` John Paul Adrian Glaubitz
2023-06-12 10:56       ` Sergey Shtylyov
2023-06-12 11:01         ` John Paul Adrian Glaubitz
2023-06-13 19:54           ` Sergey Shtylyov
2023-06-10  4:56 ` 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=1df63fac0075558850331210c28cb8fa534dc116.camel@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;
as well as URLs for NNTP newsgroup(s).