public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Dan Scally <dan.scally@ideasonboard.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	jacopo.mondi@ideasonboard.com, nayden.kanchev@arm.com,
	robh+dt@kernel.org, mchehab@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	jerome.forissier@linaro.org, kieran.bingham@ideasonboard.com
Subject: Re: [PATCH v2 2/5] dt-bindings: media: Add bindings for ARM mali-c55
Date: Fri, 16 Feb 2024 19:07:58 +0000	[thread overview]
Message-ID: <20240216-caboose-poison-3052a4bb9eaf@spud> (raw)
In-Reply-To: <f5e63a8b-fb6c-449f-8ec3-26aed5b11b95@ideasonboard.com>


[-- Attachment #1.1: Type: text/plain, Size: 1328 bytes --]

On Fri, Feb 16, 2024 at 02:45:31PM +0000, Dan Scally wrote:

> > > > > > > +      - description: ISP AXI clock
> > > > > > > +      - description: ISP AHB-lite clock
> > > > > > These two other clocks look good to me.
> > > > > > 
> > > > > > > +
> > > > > > > +  clock-names:
> > > > > > > +    items:
> > > > > > > +      - const: vclk
> > > > > > > +      - const: aclk
> > > > > > > +      - const: hclk
> > > > > Why not "video" "axi" "ahb-lite"? There's 3 useful letters between the
> > > > > tree clock names you've provided - they're all clocks, so having "clk"
> > > > > in them is just noise :)
> > > > As far as I understand, the names proposed by Dan come directly from the
> > > > IP core documentation.
> > > This is the case, but I do take Conor's point that more descriptive names might be nicer - if I'm
> > > honest I just didn't think about it particularly given "Xclk" is such a common name for them
> > > already, but having been poked into thinking about it I do agree.
> > Isn't the usual practice in DT bindings is to name GPIOs, clocks and reset
> > signals based on the hardware documentation ?
> 
> 
> Ah - I don't know honestly. If that's so then yeah - these are the names the documentation prescribes.

If a direct doc match is what you're going for, then sure, keep it.

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

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

  reply	other threads:[~2024-02-16 19:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 14:19 [PATCH v2 0/5] Add Arm Mali-C55 Image Signal Processor Driver Daniel Scally
2024-02-14 14:19 ` [PATCH v2 1/5] media: uapi: Add MEDIA_BUS_FMT_RGB202020_1X60 format code Daniel Scally
2024-02-14 14:19 ` [PATCH v2 2/5] dt-bindings: media: Add bindings for ARM mali-c55 Daniel Scally
2024-02-14 14:28   ` Laurent Pinchart
2024-02-14 17:37     ` Conor Dooley
2024-02-15 11:02       ` Laurent Pinchart
2024-02-16 13:09         ` Dan Scally
2024-02-16 13:27           ` Laurent Pinchart
2024-02-16 14:45             ` Dan Scally
2024-02-16 19:07               ` Conor Dooley [this message]
2024-02-22 18:07                 ` Rob Herring
2024-02-26 11:54   ` Sakari Ailus
2024-02-26 12:04     ` Laurent Pinchart
2024-02-26 12:20       ` Sakari Ailus
2024-02-26 12:58         ` Laurent Pinchart
2024-02-26 13:37           ` Sakari Ailus
2024-02-26 13:42             ` Dan Scally
2024-02-14 14:19 ` [PATCH v2 4/5] media: Documentation: Add Mali-C55 ISP Documentation Daniel Scally
2024-02-25 21:22   ` Kieran Bingham
2024-02-26  7:48     ` Dan Scally
2024-02-26  9:12       ` Kieran Bingham
2024-02-14 14:19 ` [PATCH v2 5/5] MAINTAINERS: Add entry for mali-c55 driver Daniel Scally
     [not found] ` <20240214141906.245685-4-dan.scally@ideasonboard.com>
     [not found]   ` <ZdxwE3omXmUjfLMn@valkosipuli.retiisi.eu>
2024-02-28 12:50     ` [PATCH v2 3/5] media: mali-c55: Add Mali-C55 ISP driver Jacopo Mondi
2024-02-28 13:11       ` Sakari Ailus
2024-02-28 13:29         ` Kieran Bingham
2024-02-28 13:38           ` Laurent Pinchart
2024-03-01 16:21     ` Dan Scally

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=20240216-caboose-poison-3052a4bb9eaf@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=dan.scally@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=jerome.forissier@linaro.org \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nayden.kanchev@arm.com \
    --cc=robh+dt@kernel.org \
    /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