mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	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 v5] sh: avoid using IRQ0 on SH3/4
Date: Thu, 1 Jun 2023 21:32:08 +0300	[thread overview]
Message-ID: <d78797df-530e-229b-418a-5cb6c269d683@omp.ru> (raw)
In-Reply-To: <e9a5f27effa12a058fa944034ee581817f2e7928.camel@physik.fu-berlin.de>

On 6/1/23 9:38 AM, John Paul Adrian Glaubitz wrote:
[...]
>> Now that IRQ0 is no longer returned by platform_get_irq() and its ilk (they
>> now return -EINVAL instead).  However, the code supporting SH3/4 SoCs still
>> maps the IRQ #s starting at 0 -- modify that code to start the IRQ #s from
>> 16 instead.

  Now that I'm re-reading this passage, it seems unfinished... :-/

>> The patch should mostly affect the AP-SH4A-3A/AP-SH4AD-0A boards as they
>> indeed use IRQ0 for the SMSC911x compatible Ethernet chip...
> 
> I'm not sure I understand. Does that mean that the Ethernet controller on
> the AP-SH4A-3A/AP-SH4AD-0A boards will no longer work after this patch
> has been applied?

   Contrariwise, they should start working again! :-)
   Here's the story as I understand it:

1. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=965b2aa78fbcb831acf4f669f494da201f4bcace broke IRQ0 use in the SMSC 9111x
driver.

2. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5ef9b803a4af0f5e42012176889b40bb2a978b18 fixed IRQ0 use in that driver.

3. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ce753ad1549cbe9ccaea4c06a1f5fa47432c8289 totally stopped returning IRQ0
from platform_get_irq(), thus breaking that driver again.

4. This patch remaps IRQ0 to IRQ16 and thus fixes the SMSC 911x driver again.

[...]

MBR, Sergey

      reply	other threads:[~2023-06-01 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <197b4ccb-2dc8-add6-02a5-2e241b15a5f9@omp.ru>
2023-06-01  6:38 ` John Paul Adrian Glaubitz
2023-06-01 18:32   ` Sergey Shtylyov [this message]

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=d78797df-530e-229b-418a-5cb6c269d683@omp.ru \
    --to=s.shtylyov@omp.ru \
    --cc=dalias@libc.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --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®