From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Petr Tesarik <petrtesarik@huaweicloud.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"open list:SUPERH" <linux-sh@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Roberto Sassu <roberto.sassu@huaweicloud.com>,
petr@tesarici.cz, Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH v1] sh: boards: fix CEU buffer size passed to dma_declare_coherent_memory()
Date: Tue, 25 Jul 2023 14:09:42 +0300 [thread overview]
Message-ID: <20230725110942.GB31069@pendragon.ideasonboard.com> (raw)
In-Reply-To: <314b21abaade55ba55ccdd930f9fdf24028cadf0.camel@physik.fu-berlin.de>
On Tue, Jul 25, 2023 at 07:50:56AM +0200, John Paul Adrian Glaubitz wrote:
> On Mon, 2023-07-24 at 20:43 +0300, Laurent Pinchart wrote:
> > > arch/sh is being maintained again, so it's save to keep these boards. At some point, we're
> > > going to convert the architecture to using Device Trees which should reduce the maintenance
> > > burden anyways.
> >
> > Keeping the architecture is fine for newer systems, but is anyone really
> > maintaining the Renesas SH board ?
>
> I own Renesas evaluation boards, including SH7785LCR-based and
> SH7724-based boards.
Will you have time to port them to DT, or would you rather focus on
J-core systems ? Do those boards still boot a mainline kernel ?
Dropping Renesas SH board files doesn't preclude anyone from moving them
to DT, all the information will remain in the git history. Unless you
plan to move to DT in a reasonably near future, I think dropping support
for the CEU at least, if not the whole board files, could be a good
option.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-07-25 11:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 12:07 [PATCH v1] sh: boards: fix CEU buffer size passed to dma_declare_coherent_memory() Petr Tesarik
2023-07-24 13:01 ` Geert Uytterhoeven
2023-07-24 13:22 ` Jacopo Mondi
2023-07-24 15:34 ` Petr Tesařík
2023-07-24 17:12 ` Laurent Pinchart
2023-07-24 17:29 ` John Paul Adrian Glaubitz
2023-07-24 17:43 ` Laurent Pinchart
2023-07-25 5:45 ` Petr Tesařík
2023-07-25 5:50 ` John Paul Adrian Glaubitz
2023-07-25 11:09 ` Laurent Pinchart [this message]
2023-07-25 11:38 ` John Paul Adrian Glaubitz
2023-07-25 12:42 ` Laurent Pinchart
2023-07-25 12:21 ` D. Jeff Dionne
2023-09-08 9:36 ` 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=20230725110942.GB31069@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hans.verkuil@cisco.com \
--cc=jacopo+renesas@jmondi.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=petr@tesarici.cz \
--cc=petrtesarik@huaweicloud.com \
--cc=roberto.sassu@huaweicloud.com \
--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