linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-sh@vger.kernel.org, glaubitz@physik.fu-berlin.de
Subject: Re: [RESEND RFC PATCH 01/12] sh: Add OF target boards.
Date: Wed, 06 Sep 2023 17:05:29 +0900	[thread overview]
Message-ID: <87bkefvi9i.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <CAMuHMdV0rmmi8=DyQL-WmMdFyo4g6obNXjWutNGEz=3QcO_d+g@mail.gmail.com>

On Fri, 01 Sep 2023 23:26:10 +0900,
Geert Uytterhoeven wrote:
> 
> Hi Sato-san,
> 
> On Thu, Aug 31, 2023 at 5:19 AM Yoshinori Sato
> <ysato@users.sourceforge.jp> wrote:
> > --- a/arch/sh/Kconfig
> > +++ b/arch/sh/Kconfig
> 
> > @@ -702,7 +707,7 @@ config BUILTIN_DTB_SOURCE
> >  config ZERO_PAGE_OFFSET
> >         hex
> >         default "0x00010000" if PAGE_SIZE_64KB || SH_RTS7751R2D || \
> > -                               SH_7751_SOLUTION_ENGINE
> > +                               SH_7751_SOLUTION_ENGINE || SH_RTS7751R2D_OF
> 
> This is the only user of SH_RTS7751R2D_OF. Can we get rid of it?
> 
> >         default "0x00004000" if PAGE_SIZE_16KB || SH_SH03
> >         default "0x00002000" if PAGE_SIZE_8KB
> >         default "0x00001000"
> 
> > --- a/arch/sh/boards/Kconfig
> > +++ b/arch/sh/boards/Kconfig
> > @@ -161,6 +166,17 @@ config SH_RTS7751R2D
> >           Select RTS7751R2D if configuring for a Renesas Technology
> >           Sales SH-Graphics board.
> >
> > +config SH_RTS7751R2D_OF
> > +       bool "RTS7751R2D (DeviceTree)"
> > +       depends on CPU_SUBTYPE_SH7751R
> > +       select HAVE_PCI
> > +       select IO_TRAPPED if MMU
> > +       select SH_DEVICE_TREE
> > +       select COMMON_CLK
> > +       help
> > +         Select RTS7751R2D if configuring for a Renesas Technology
> > +         Sales SH-Graphics board. (Use DeviceTree)
> > +
> >  config SH_RSK
> >         bool "Renesas Starter Kit"
> >         depends on CPU_SUBTYPE_SH7201 || CPU_SUBTYPE_SH7203 || \
> > @@ -300,8 +316,20 @@ config SH_LANDISK
> >         bool "LANDISK"
> >         depends on CPU_SUBTYPE_SH7751R
> >         select HAVE_PCI
> > +       select SYS_SUPPORTS_PCI
> > +       help
> > +         I-O DATA DEVICE, INC. "LANDISK Series" support.
> > +
> > +config SH_LANDISK_OF
> > +       bool "LANDISK (DeviceTree)"
> > +       depends on CPU_SUBTYPE_SH7751R
> > +       select HAVE_PCI
> > +       select SYS_SUPPORTS_PCI
> > +       select SH_DEVICE_TREE
> > +       select COMMON_CLK
> >         help
> >           I-O DATA DEVICE, INC. "LANDISK Series" support.
> > +         Use Device Tree.
> >
> >  config SH_TITAN
> >         bool "TITAN"
> 
> Apart from the above, there are no users of the "<machine>_OF" symbols.
> Do we need them?

-- 
Yosinori Sato

  reply	other threads:[~2023-09-06  8:05 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  1:11 [RESEND RFC PATCH 00/12] DeviceTree support for SH7751 based boards Yoshinori Sato
2023-08-31  1:11 ` [RESEND RFC PATCH 01/12] sh: Add OF target boards Yoshinori Sato
2023-09-01 12:22   ` Geert Uytterhoeven
2023-09-01 14:26   ` Geert Uytterhoeven
2023-09-06  8:05     ` Yoshinori Sato [this message]
2023-09-06  8:12       ` John Paul Adrian Glaubitz
2023-09-07  3:28         ` Yoshinori Sato
2023-09-07  3:35     ` Yoshinori Sato
2023-08-31  1:11 ` [RESEND RFC PATCH 02/12] sh: Update OF handling Yoshinori Sato
2023-09-01 12:25   ` Geert Uytterhoeven
2023-08-31  1:11 ` [RESEND RFC PATCH 03/12] sh: SH4 OF support Yoshinori Sato
2023-09-01 12:26   ` Geert Uytterhoeven
2023-09-13 12:23   ` Geert Uytterhoeven
2023-09-15  9:21     ` Yoshinori Sato
2023-08-31  1:11 ` [RESEND RFC PATCH 04/12] clk: SH7750 / 7751 clk driver Yoshinori Sato
2023-09-01 12:26   ` Geert Uytterhoeven
2023-09-07  3:44     ` Yoshinori Sato
2023-08-31  1:11 ` [RESEND RFC PATCH 05/12] drivers/irqchip: Add SH7751 and boards specific irqchip Yoshinori Sato
2023-09-01 12:49   ` Geert Uytterhoeven
2023-08-31  1:11 ` [RESEND RFC PATCH 06/12] drivers/pci: Add SH7751 PCI Host bridge driver Yoshinori Sato
2023-09-01 12:54   ` Geert Uytterhoeven
2023-08-31  1:11 ` [RESEND RFC PATCH 07/12] clocksource: Update sh_tmu of handling Yoshinori Sato
2023-08-31  6:48   ` Krzysztof Kozlowski
2023-09-01 13:01   ` Geert Uytterhoeven
2023-09-01 13:40     ` Yoshinori Sato
2023-08-31  1:11 ` [RESEND RFC PATCH 08/12] mfd/sm501: Add OF properties Yoshinori Sato
2023-08-31  6:51   ` Krzysztof Kozlowski
2023-09-01 13:09   ` Geert Uytterhoeven
2023-08-31  1:11 ` [RESEND RFC PATCH 09/12] of: FDT vaddr support for SH Yoshinori Sato
2023-08-31  6:48   ` Krzysztof Kozlowski
2023-09-01 13:11   ` Geert Uytterhoeven
2023-09-01 13:33     ` Yoshinori Sato
2023-08-31  1:11 ` [RESEND RFC PATCH 10/12] serial/sh-sci: Fix earlyprintk / earlycon Yoshinori Sato
2023-09-01 13:26   ` Geert Uytterhoeven
2023-09-06  7:27     ` Yoshinori Sato
2023-08-31  1:11 ` [RESEND RFC PATCH 11/12] sh: target dts Yoshinori Sato
2023-09-01 14:23   ` Geert Uytterhoeven
2023-08-31  1:11 ` [RESEND RFC PATCH 12/12] sh: OF defconfig Yoshinori Sato

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=87bkefvi9i.wl-ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-sh@vger.kernel.org \
    /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).