All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Kun-Fa Lin <milkfafa@gmail.com>
Cc: "CS20 KWLiu" <kwliu@nuvoton.com>,
	tali.perry1@gmail.com, tmaimon77@gmail.com,
	avifishman70@gmail.com, openbmc@lists.ozlabs.org,
	linux-kernel@vger.kernel.org,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	mchehab@kernel.org, "Marvin Lin" <kflin@nuvoton.com>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v2 5/5] drivers: media: platform: Add NPCM Video Capture/Encode Engine driver
Date: Thu, 19 May 2022 12:12:28 +0200	[thread overview]
Message-ID: <YoYYDPHPjSUefbAg@latitude> (raw)
In-Reply-To: <CADnNmFoa6=BWs74oQxEtP4TO-mL_vc0py4+4V1wjdtetW4Vy5w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 815 bytes --]

Hello Marvin,

On Thu, May 19, 2022 at 01:39:01PM +0800, Kun-Fa Lin wrote:
[...]
> In this architecture, for the case of WPCM450 (though it's in EOL for
> several years), I'd prefer to try to let ECE be an optional node
> instead of separating ECE code from this V4L2 video driver. However,
> this patch series could be the base version and keep reviewing, and
> afterwards we could make another patch for optional ECE, is it OK for
> you?

That's OK for me.

I will wait until the driver is ready and merged, and then start working
on WPCM450 integration and making ECE optional.

Regarding WPCM450 being EOL, I'm aware, and I don't want to hold up your
team's work on newer SoCs. But I personally find this old SoC interesting
and I want to share driver code with newer SoCs where possible.


Thank you,
Jonathan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Kun-Fa Lin <milkfafa@gmail.com>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	mchehab@kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, "CS20 KWLiu" <kwliu@nuvoton.com>,
	tmaimon77@gmail.com, avifishman70@gmail.com,
	openbmc@lists.ozlabs.org, tali.perry1@gmail.com,
	"Marvin Lin" <kflin@nuvoton.com>
Subject: Re: [PATCH v2 5/5] drivers: media: platform: Add NPCM Video Capture/Encode Engine driver
Date: Thu, 19 May 2022 12:12:28 +0200	[thread overview]
Message-ID: <YoYYDPHPjSUefbAg@latitude> (raw)
In-Reply-To: <CADnNmFoa6=BWs74oQxEtP4TO-mL_vc0py4+4V1wjdtetW4Vy5w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 815 bytes --]

Hello Marvin,

On Thu, May 19, 2022 at 01:39:01PM +0800, Kun-Fa Lin wrote:
[...]
> In this architecture, for the case of WPCM450 (though it's in EOL for
> several years), I'd prefer to try to let ECE be an optional node
> instead of separating ECE code from this V4L2 video driver. However,
> this patch series could be the base version and keep reviewing, and
> afterwards we could make another patch for optional ECE, is it OK for
> you?

That's OK for me.

I will wait until the driver is ready and merged, and then start working
on WPCM450 integration and making ECE optional.

Regarding WPCM450 being EOL, I'm aware, and I don't want to hold up your
team's work on newer SoCs. But I personally find this old SoC interesting
and I want to share driver code with newer SoCs where possible.


Thank you,
Jonathan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-05-19 10:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13  3:34 [PATCH v2 0/5] Support Nuvoton NPCM Video Capture/Encode Engine Marvin Lin
2022-05-13  3:34 ` Marvin Lin
2022-05-13  3:34 ` [PATCH v2 1/5] arm: dts: Add node for " Marvin Lin
2022-05-13  3:34   ` Marvin Lin
2022-05-13  5:22   ` Paul Menzel
2022-05-13  5:22     ` Paul Menzel
2022-05-17  1:55     ` Kun-Fa Lin
2022-05-17  1:55       ` Kun-Fa Lin
2022-05-13  3:34 ` [PATCH v2 2/5] dt-bindings: media: Add dt-bindings " Marvin Lin
2022-05-13  3:34   ` Marvin Lin
2022-05-13  3:34 ` [PATCH v2 3/5] dt-bindings: arm/npcm: Add dt-bindings for Graphics Core Information Marvin Lin
2022-05-13  3:34   ` Marvin Lin
2022-05-13  3:34 ` [PATCH v2 4/5] media: Add HEXTILE compressed format Marvin Lin
2022-05-13  3:34   ` Marvin Lin
2022-05-13  3:34 ` [PATCH v2 5/5] drivers: media: platform: Add NPCM Video Capture/Encode Engine driver Marvin Lin
2022-05-13  3:34   ` Marvin Lin
2022-05-13  5:46   ` Paul Menzel
2022-05-13  5:46     ` Paul Menzel
2022-05-17  2:59     ` Kun-Fa Lin
2022-05-17  2:59       ` Kun-Fa Lin
2022-06-06  2:42       ` Kun-Fa Lin
2022-06-06  2:42         ` Kun-Fa Lin
2022-05-13  9:09   ` kernel test robot
2022-05-13  9:09     ` kernel test robot
2022-05-13 10:30   ` kernel test robot
2022-05-13 10:30     ` kernel test robot
2022-05-14 10:41   ` kernel test robot
2022-05-14 10:41     ` kernel test robot
2022-05-17 13:30   ` Jonathan Neuschäfer
2022-05-17 13:30     ` Jonathan Neuschäfer
2022-05-19  5:39     ` Kun-Fa Lin
2022-05-19  5:39       ` Kun-Fa Lin
2022-05-19 10:12       ` Jonathan Neuschäfer [this message]
2022-05-19 10:12         ` Jonathan Neuschäfer

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=YoYYDPHPjSUefbAg@latitude \
    --to=j.neuschaefer@gmx.net \
    --cc=avifishman70@gmail.com \
    --cc=kflin@nuvoton.com \
    --cc=kwliu@nuvoton.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=milkfafa@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=tali.perry1@gmail.com \
    --cc=tmaimon77@gmail.com \
    /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.