All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rich Felker <dalias@libc.org>
Cc: Simon Horman <horms@verge.net.au>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"D. Jeff Dionne" <jeff@uclinux.org>,
	Rob Landley <rob@landley.net>
Subject: Re: [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh sections
Date: Fri, 08 Jan 2016 20:35:11 +0000	[thread overview]
Message-ID: <CAMuHMdWkwXkFu6Uf-yYr7GiNc7OCvHXYPKGpOE7QhHY56F2rug@mail.gmail.com> (raw)
In-Reply-To: <20160108182145.GA22240@brightrain.aerifal.cx>

Hi Rich,

On Fri, Jan 8, 2016 at 7:21 PM, Rich Felker <dalias@libc.org> wrote:
> On Fri, Jan 08, 2016 at 10:01:25AM +0100, Geert Uytterhoeven wrote:
>> Many old ARM/SH-Mobile SoCs look like SH SoCs with an ARM CPU core bolted on.
>> Recent Renesas ARM SoCs still share many IP cores with older SH SoCs; most of
>> them even have a secondary SH4 CPU core. Using the SH4 CPU core could be useful
>> for doing SH4 work, until J4 becomes mainstream (cfr. old prototype in
>> http://www.spinics.net/lists/linux-sh/msg07188.html).
>> Probably the Jx series won't share IP cores with SH/ARM, but as arch/sh/
>> maintainers you have to care about older Renesas SH platforms, too.
>>
>> For patchwork, that would mean some more delegation needs to be put in place.
>>
>> So far my 0.05€...
>
> Is that actually the case? I can't find any current support in the
> kernel for running on these SH4 cores, and I was under the impression
> that they were being phased out, if not already gone. And the bulk of

There's no in-kernel support for these SH4 cores yet, just the prototype.

> the driver-related discussion I've seen on linux-sh over the past year
> does not seem to be related to hardware that's present/usable on
> boards where you can run Linux/SH. If this is incorrect, I'd like to
> hear some views on how/why such hardware is relevant to arch/sh.

At least the following drivers are shared between ARM and SH:

hspi
rspi
sh-cmt
sh_fsi
sh-mtu2
sh-sci (covering sci, scif, scifa, scifb, hscif)
sh-tmu
tpu

and of course the sh-pfc pinctrl subsystem.

Probably I'm forgetting a few that haven't been converted to DT on ARM yet,
and where the ARM side thus could benefit from a DT conversion on SH.

Note that you can find "shmobile" SoCs under both arch/sh/
(sh7723/sh7724/sh7343/sh7722/sh7366) and arch/arm/mach-shmobile/.
Some of these used to share even more code (e.g. drivers/sh/clk/), until the
ARM ones were converted to the Common Clock Framework.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rich Felker <dalias@libc.org>
Cc: Simon Horman <horms@verge.net.au>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"D. Jeff Dionne" <jeff@uclinux.org>,
	Rob Landley <rob@landley.net>
Subject: Re: [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh sections
Date: Fri, 8 Jan 2016 21:35:11 +0100	[thread overview]
Message-ID: <CAMuHMdWkwXkFu6Uf-yYr7GiNc7OCvHXYPKGpOE7QhHY56F2rug@mail.gmail.com> (raw)
In-Reply-To: <20160108182145.GA22240@brightrain.aerifal.cx>

Hi Rich,

On Fri, Jan 8, 2016 at 7:21 PM, Rich Felker <dalias@libc.org> wrote:
> On Fri, Jan 08, 2016 at 10:01:25AM +0100, Geert Uytterhoeven wrote:
>> Many old ARM/SH-Mobile SoCs look like SH SoCs with an ARM CPU core bolted on.
>> Recent Renesas ARM SoCs still share many IP cores with older SH SoCs; most of
>> them even have a secondary SH4 CPU core. Using the SH4 CPU core could be useful
>> for doing SH4 work, until J4 becomes mainstream (cfr. old prototype in
>> http://www.spinics.net/lists/linux-sh/msg07188.html).
>> Probably the Jx series won't share IP cores with SH/ARM, but as arch/sh/
>> maintainers you have to care about older Renesas SH platforms, too.
>>
>> For patchwork, that would mean some more delegation needs to be put in place.
>>
>> So far my 0.05€...
>
> Is that actually the case? I can't find any current support in the
> kernel for running on these SH4 cores, and I was under the impression
> that they were being phased out, if not already gone. And the bulk of

There's no in-kernel support for these SH4 cores yet, just the prototype.

> the driver-related discussion I've seen on linux-sh over the past year
> does not seem to be related to hardware that's present/usable on
> boards where you can run Linux/SH. If this is incorrect, I'd like to
> hear some views on how/why such hardware is relevant to arch/sh.

At least the following drivers are shared between ARM and SH:

hspi
rspi
sh-cmt
sh_fsi
sh-mtu2
sh-sci (covering sci, scif, scifa, scifb, hscif)
sh-tmu
tpu

and of course the sh-pfc pinctrl subsystem.

Probably I'm forgetting a few that haven't been converted to DT on ARM yet,
and where the ARM side thus could benefit from a DT conversion on SH.

Note that you can find "shmobile" SoCs under both arch/sh/
(sh7723/sh7724/sh7343/sh7722/sh7366) and arch/arm/mach-shmobile/.
Some of these used to share even more code (e.g. drivers/sh/clk/), until the
ARM ones were converted to the Common Clock Framework.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2016-01-08 20:35 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08  4:39 [PATCH 0/2] Resume maintenance & development of arch/sh Rich Felker
2016-01-08  4:39 ` Rich Felker
2016-01-08  4:39 ` [PATCH 1/2] MAINTAINERS: return arch/sh to maintained state, with new maintainers Rich Felker
2016-01-08  4:39   ` Rich Felker
2016-01-11 17:53   ` Peter Zijlstra
2016-01-11 17:53     ` Peter Zijlstra
2016-01-13  1:40     ` Simon Horman
2016-01-13  1:40       ` Simon Horman
2016-01-15  0:52       ` Rich Felker
2016-01-15  0:52         ` Rich Felker
2016-01-15  9:31         ` Geert Uytterhoeven
2016-01-15  9:31           ` Geert Uytterhoeven
2016-01-17  2:32           ` Rich Felker
2016-01-17  2:32             ` Rich Felker
2016-01-17  8:48             ` Geert Uytterhoeven
2016-01-17  8:48               ` Geert Uytterhoeven
2016-01-08  4:40 ` [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh sections Rich Felker
2016-01-08  4:40   ` Rich Felker
2016-01-08  6:56   ` Simon Horman
2016-01-08  6:56     ` Simon Horman
2016-01-08  9:01     ` Geert Uytterhoeven
2016-01-08  9:01       ` Geert Uytterhoeven
2016-01-08 18:21       ` Rich Felker
2016-01-08 18:21         ` Rich Felker
2016-01-08 20:35         ` Geert Uytterhoeven [this message]
2016-01-08 20:35           ` Geert Uytterhoeven
2016-01-08 20:52           ` Rich Felker
2016-01-08 20:52             ` Rich Felker
2016-01-10 19:41             ` Geert Uytterhoeven
2016-01-10 19:41               ` Geert Uytterhoeven
2016-01-08 17:35     ` Rob Landley
2016-01-08 17:35       ` Rob Landley
2016-01-08 18:28       ` Laurent Pinchart
2016-01-08 18:28         ` Laurent Pinchart
2016-01-08 19:40         ` Rich Felker
2016-01-08 19:40           ` Rich Felker
2016-01-08 23:15           ` Laurent Pinchart
2016-01-08 23:15             ` Laurent Pinchart
2016-01-08 22:50         ` Rob Landley
2016-01-08 22:50           ` Rob Landley
2016-01-10 20:05           ` Geert Uytterhoeven
2016-01-10 20:05             ` Geert Uytterhoeven
2016-01-11  2:02             ` Rob Landley
2016-01-11  2:02               ` Rob Landley
2016-01-11  2:22               ` uClinux.org
2016-01-11  2:22                 ` uClinux.org
2016-01-08 18:51       ` Rich Felker
2016-01-08 18:51         ` Rich Felker
2016-01-08 18:03   ` Sergei Shtylyov
2016-01-08 18:03     ` Sergei Shtylyov

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=CAMuHMdWkwXkFu6Uf-yYr7GiNc7OCvHXYPKGpOE7QhHY56F2rug@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=dalias@libc.org \
    --cc=horms@verge.net.au \
    --cc=jeff@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rob@landley.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.