All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Eugen Hristev <eugen.hristev@collabora.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-mediatek@lists.infradead.org, bin.liu@mediatek.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	angelogioacchino.delregno@collabora.com, kernel@collabora.com,
	matthias.bgg@gmail.com
Subject: Re: [PATCH v2 1/2] dt-bindings: media: mediatek-jpeg-encoder: change max iommus count
Date: Tue, 9 Jan 2024 13:06:17 -0600	[thread overview]
Message-ID: <20240109190617.GA2958445-robh@kernel.org> (raw)
In-Reply-To: <20240102103801.268647-1-eugen.hristev@collabora.com>

On Tue, Jan 02, 2024 at 12:38:00PM +0200, Eugen Hristev wrote:
> MT8186 has 4 iommus in the list, to cope with this situation, adjust
> the maxItems to 4 (instead of previous 2).
> Add also minItems as 1 since iommus are mandatory, to avoid warning
> on the example.

maxItems alone means minItems is the same size. If IOMMU is required,
then 'required' is where that is defined. Is there a case where 1 IOMMU
is valid? If so, what h/w has this case.

Rob


WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Eugen Hristev <eugen.hristev@collabora.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-mediatek@lists.infradead.org, bin.liu@mediatek.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	angelogioacchino.delregno@collabora.com, kernel@collabora.com,
	matthias.bgg@gmail.com
Subject: Re: [PATCH v2 1/2] dt-bindings: media: mediatek-jpeg-encoder: change max iommus count
Date: Tue, 9 Jan 2024 13:06:17 -0600	[thread overview]
Message-ID: <20240109190617.GA2958445-robh@kernel.org> (raw)
In-Reply-To: <20240102103801.268647-1-eugen.hristev@collabora.com>

On Tue, Jan 02, 2024 at 12:38:00PM +0200, Eugen Hristev wrote:
> MT8186 has 4 iommus in the list, to cope with this situation, adjust
> the maxItems to 4 (instead of previous 2).
> Add also minItems as 1 since iommus are mandatory, to avoid warning
> on the example.

maxItems alone means minItems is the same size. If IOMMU is required,
then 'required' is where that is defined. Is there a case where 1 IOMMU
is valid? If so, what h/w has this case.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-01-09 19:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 10:38 [PATCH v2 1/2] dt-bindings: media: mediatek-jpeg-encoder: change max iommus count Eugen Hristev
2024-01-02 10:38 ` Eugen Hristev
2024-01-02 10:38 ` [PATCH v2 2/2] arm64: dts: mediatek: mt8186: Add jpgenc node Eugen Hristev
2024-01-02 10:38   ` Eugen Hristev
2024-01-02 14:13   ` AngeloGioacchino Del Regno
2024-01-02 14:13     ` AngeloGioacchino Del Regno
2024-01-09 19:06 ` Rob Herring [this message]
2024-01-09 19:06   ` [PATCH v2 1/2] dt-bindings: media: mediatek-jpeg-encoder: change max iommus count Rob Herring

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=20240109190617.GA2958445-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=bin.liu@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eugen.hristev@collabora.com \
    --cc=kernel@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@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.