From: Rob Herring <robh@kernel.org>
To: Ming Qian <ming.qian@nxp.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"Mirela Rabulea (OSS)" <mirela.rabulea@oss.nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"X.H. Bao" <xiahong.bao@nxp.com>, Eagle Zhou <eagle.zhou@nxp.com>,
Tao Jiang <tao.jiang_2@nxp.com>, dl-linux-imx <linux-imx@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [EXT] Re: [PATCH v4 2/2] dt-bindings: media: imx-jpeg: Assign slot for imx jpeg encoder/decoder
Date: Thu, 28 Sep 2023 11:47:20 -0500 [thread overview]
Message-ID: <20230928164720.GA816352-robh@kernel.org> (raw)
In-Reply-To: <AM6PR04MB63415CF2EDCF0AF33F778774E7C2A@AM6PR04MB6341.eurprd04.prod.outlook.com>
On Wed, Sep 27, 2023 at 09:10:52AM +0000, Ming Qian wrote:
> >From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >
> >On 26/09/2023 12:10, Ming Qian wrote:
> >> There are total 4 slots available in the IP, and we only need to use
> >> one slot in one os, assign a single slot, configure interrupt and
> >> power domain only for 1 slot, not for the all 4 slots.
> >>
> >> Signed-off-by: Ming Qian <ming.qian@nxp.com>
> >> ---
> >> v4
> >> - improve commit message
> >> - don't make an ABI break
> >> v3
> >> - add vender prefix, change property slot to nxp,slot
> >> - add type for property slot
> >>
> >> .../bindings/media/nxp,imx8-jpeg.yaml | 45 +++++++++----------
> >> 1 file changed, 21 insertions(+), 24 deletions(-)
> >>
> >> diff --git
> >> a/Documentation/devicetree/bindings/media/nxp,imx8-jpeg.yaml
> >> b/Documentation/devicetree/bindings/media/nxp,imx8-jpeg.yaml
> >> index 3d9d1db37040..4bcfc815c894 100644
> >> --- a/Documentation/devicetree/bindings/media/nxp,imx8-jpeg.yaml
> >> +++ b/Documentation/devicetree/bindings/media/nxp,imx8-jpeg.yaml
> >> @@ -32,19 +32,26 @@ properties:
> >> maxItems: 1
> >>
> >> interrupts:
> >> - description: |
> >> - There are 4 slots available in the IP, which the driver may use
> >> - If a certain slot is used, it should have an associated interrupt
> >> - The interrupt with index i is assumed to be for slot i
> >> - minItems: 1 # At least one slot is needed by the driver
> >> - maxItems: 4 # The IP has 4 slots available for use
> >> + description:
> >> + Interrupt number for slot
> >> + maxItems: 1
> >>
> >> power-domains:
> >> description:
> >> List of phandle and PM domain specifier as documented in
> >> Documentation/devicetree/bindings/power/power_domain.txt
> >> - minItems: 2 # Wrapper and 1 slot
> >> - maxItems: 5 # Wrapper and 4 slots
> >> + minItems: 1 # VPUMIX
> >> + maxItems: 2 # Wrapper and 1 slot
> >> +
> >> + nxp,slot:
> >> + $ref: /schemas/types.yaml#/definitions/uint32
> >> + description:
> >> + Integer number of slot index used. There are 4 slots available in the IP,
> >> + and driver can use a certain slot, it should have an associated interrupt
> >> + and power-domain. In theory, it supports 4 os or vm. If not specified, 0
> >> + is used by default.
> >> + minimum: 0
> >> + maximum: 3
> >
> >NAK, you still did not answer concerns why this is needed and justified.
> >I keep asking and you keep ignoring...
> >
> >Best regards,
> >Krzysztof
>
> Hi Krzysztof,
>
> > Nothing explains what is a slot and nothing explains why do you need this property.
>
> I thought I had answered that question, but seems you don't agree with that explanation.
> Would the following description be any better?
>
> The slot is the IP used to share the jpeg engine across multiple VMS
> and os, there are 4 slots available in the IP. We can use one slot in
> linux. The slot index indicates which slot we choose. If not
> specified, 0 is used by default.
If you have to modify the DT to update 'nxp,slot', then you can modify
the DT to just expose the parts of the h/w for the assigned slot. For
example, only put slot 1's power-domains entry in the DT when slot 1 is
assigned.
As far as formatting your emails, talk to your NXP colleagues. They've
figured it out. If you've configured git-send-email successfully, then
using mutt should be possible. You can use 'b4' to get the thread mbox,
and read it in mutt.
Rob
next prev parent reply other threads:[~2023-09-28 16:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 10:09 [PATCH v4 1/2] arm64: dts: imx8-ss-img: Assign slot for imx jpeg encoder/decoder Ming Qian
2023-09-26 10:10 ` [PATCH v4 2/2] dt-bindings: media: imx-jpeg: " Ming Qian
2023-09-26 13:25 ` Conor Dooley
2023-09-27 2:10 ` [EXT] " Ming Qian
2023-09-27 8:10 ` Krzysztof Kozlowski
2023-09-27 9:11 ` Conor Dooley
2023-09-27 9:25 ` Ming Qian
2023-09-28 5:24 ` Krzysztof Kozlowski
2023-09-28 10:03 ` Ming Qian
2023-09-27 8:06 ` Krzysztof Kozlowski
2023-09-27 9:10 ` [EXT] " Ming Qian
2023-09-28 5:06 ` Krzysztof Kozlowski
2023-09-28 9:42 ` Ming Qian
2023-09-30 14:40 ` Krzysztof Kozlowski
2023-10-02 1:23 ` Ming Qian
2023-09-28 5:06 ` Krzysztof Kozlowski
2023-09-28 16:47 ` Rob Herring [this message]
2023-09-29 2:03 ` Ming Qian
2023-09-27 8:10 ` [PATCH v4 1/2] arm64: dts: imx8-ss-img: " Krzysztof Kozlowski
2023-09-27 9:19 ` [EXT] " Ming Qian
2023-09-28 5:02 ` Krzysztof Kozlowski
2023-09-28 9:51 ` Ming Qian
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=20230928164720.GA816352-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eagle.zhou@nxp.com \
--cc=festevam@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ming.qian@nxp.com \
--cc=mirela.rabulea@oss.nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tao.jiang_2@nxp.com \
--cc=xiahong.bao@nxp.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;
as well as URLs for NNTP newsgroup(s).