public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Mon, 24 Jul 2023 20:43:31 +0300	[thread overview]
Message-ID: <20230724174331.GD11977@pendragon.ideasonboard.com> (raw)
In-Reply-To: <31ad16fe8f1435805185ba8e889512ec181a867e.camel@physik.fu-berlin.de>

On Mon, Jul 24, 2023 at 07:29:27PM +0200, John Paul Adrian Glaubitz wrote:
> On Mon, 2023-07-24 at 20:12 +0300, Laurent Pinchart wrote:
> > On Mon, Jul 24, 2023 at 02:07:42PM +0200, Petr Tesarik wrote:
> > > From: Petr Tesarik <petr.tesarik.ext@huawei.com>
> > > 
> > > In all these cases, the last argument to dma_declare_coherent_memory() is
> > > the buffer end address, but the expected value should be the size of the
> > > reserved region.
> > > 
> > > Fixes: 39fb993038e1 ("media: arch: sh: ap325rxa: Use new renesas-ceu camera driver")
> > > Fixes: c2f9b05fd5c1 ("media: arch: sh: ecovec: Use new renesas-ceu camera driver")
> > > Fixes: f3590dc32974 ("media: arch: sh: kfr2r09: Use new renesas-ceu camera driver")
> > > Fixes: 186c446f4b84 ("media: arch: sh: migor: Use new renesas-ceu camera driver")
> > > Fixes: 1a3c230b4151 ("media: arch: sh: ms7724se: Use new renesas-ceu camera driver")
> > > Signed-off-by: Petr Tesarik <petr.tesarik.ext@huawei.com>
> > 
> > Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> > 
> > But given that nobody noticed for 5 years, maybe we should drop
> > renesas-ceu support from those boards ? Or drop the boards completely ?
> 
> 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 ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2023-07-24 17:43 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 [this message]
2023-07-25  5:45       ` Petr Tesařík
2023-07-25  5:50       ` John Paul Adrian Glaubitz
2023-07-25 11:09         ` Laurent Pinchart
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=20230724174331.GD11977@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