public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Majewski <mattwmajewski@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	"Dr. David Alan Gilbert" <linux@treblig.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	"Uwe Kleine-Konig" <u.kleine-koenig@baylibre.com>,
	Andrzej Pietrasiewicz <andrzejtp2010@gmail.com>
Cc: devicetree@vger.kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Matthew Majewski <mattwmajewski@gmail.com>
Subject: [PATCH v2 0/2] media: m2m-deinterlace: add device-tree support
Date: Fri, 14 Feb 2025 18:17:57 -0500	[thread overview]
Message-ID: <20250214231759.119481-1-mattwmajewski@gmail.com> (raw)

Hello all, this patch series adds device-tree support for the generic
m2m-deinterlace driver.

A specific dma controller channel can now be provided to the driver
via the dt, but the driver still supports the original dma query if an
of_node is not present. This should preserve backwards compatibility
with platform drivers that directly instantiate the device.

Probing the m2m-deinterlace device via device-tree was tested on the
BeagleBone Black with an m2m-appropriate edma channel.

Changes From v1 [1]:
 - [PATCH 1/2] media: dt-bindings: Add dt bindings for m2m-deinterlace
   - clarify device description and commit message for dt bindings
   - correct format error reported by yamllint for dt bindings
 - [PATCH 2/2] media: m2m-deinterlace: add device-tree support
   - no changes

[1] https://lore.kernel.org/linux-media/20250212170901.3881838-1-mattwmajewski@gmail.com/

Best,

Matthew Majewski

Matthew Majewski (2):
  media: dt-bindings: Add dt bindings for m2m-deinterlace device
  media: m2m-deinterlace: add device-tree support

 .../bindings/media/m2m-deinterlace.yaml       | 44 +++++++++++++++++++
 drivers/media/platform/m2m-deinterlace.c      | 25 ++++++++---
 2 files changed, 63 insertions(+), 6 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/media/m2m-deinterlace.yaml

-- 
2.25.1


             reply	other threads:[~2025-02-14 23:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 23:17 Matthew Majewski [this message]
2025-02-14 23:17 ` [PATCH v2 1/2] media: dt-bindings: Add dt bindings for m2m-deinterlace device Matthew Majewski
2025-02-18  8:30   ` Krzysztof Kozlowski
2025-02-26 22:41     ` Matthew Majewski
2025-03-03  7:31       ` Krzysztof Kozlowski
2025-03-03  7:34         ` Krzysztof Kozlowski
2025-03-03 15:21         ` Matthew Majewski
2025-03-04  7:26           ` Krzysztof Kozlowski
2025-02-14 23:17 ` [PATCH v2 2/2] media: m2m-deinterlace: add device-tree support Matthew Majewski

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=20250214231759.119481-1-mattwmajewski@gmail.com \
    --to=mattwmajewski@gmail.com \
    --cc=andrzejtp2010@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=mchehab@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=u.kleine-koenig@baylibre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox