devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rudraksha Gupta <guptarud@gmail.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	agross@kernel.org, david@ixit.cz, devicetree@vger.kernel.org,
	krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v2 1/2] ARM: msm8960: Rename cxo_board to cxo-board and add alias
Date: Tue, 21 Feb 2023 01:40:40 -0500	[thread overview]
Message-ID: <4778cc0a-77ad-b28f-bbf5-6247d26f81b4@gmail.com> (raw)
In-Reply-To: <20220829215443.dvc5xnmeqnhmxb2d@builder.lan>

Hello,


So I'm trying to add a cxo-board node to my dts, however the current 
implementation seems like it wants cxo_board. It was recommended a while 
ago that I refactor gcc-msm8960.c to be more like 
https://github.com/torvalds/linux/blob/master/drivers/clk/qcom/gcc-msm8996.c#L36 
. However, I have a couple of questions:

- The xo struct that I listed above is listed in another struct 
https://github.com/torvalds/linux/blob/master/drivers/clk/qcom/gcc-msm8996.c#L3408 
which is listed in the SoC desc struct 
https://github.com/torvalds/linux/blob/master/drivers/clk/qcom/gcc-msm8996.c#L3818 
. My question is that even though gcc-msm8960.c has an msm8960/apq8064 
desc struct, it doesn't have anything like gcc_msm8996_hws. How would I 
know what goes in a hypothetical gcc_(msm8960/apq8064)_hws struct? I'm 
assuming that all I need in the hw struct is the pxo and cxo listed here 
https://github.com/torvalds/linux/blob/master/drivers/clk/qcom/gcc-msm8960.c#L3727 
however I'm not 100% sure how to verify this. Would anything else go 
into a hypothetical gcc_(msm8960/apq8064)_hws struct?

- Is there documentation on how the gcc-<soc> files work? I'm still 
quite new to contributing to the Linux kernel and would like to learn 
more about the modern way to format these files and to learn more about 
how they work in general


Thanks,

Rudraksha


  reply	other threads:[~2023-02-21  6:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 23:47 [PATCH 1/2] ARM: msm8960: Rename cxo_board to cxo-board and add alias Rudraksha Gupta
2022-08-08 23:47 ` [PATCH 2/2] ARM: msm8960: Add Samsung Galaxy Express support Rudraksha Gupta
2022-08-09  0:02   ` [PATCH v2 1/2] ARM: msm8960: Rename cxo_board to cxo-board and add alias Rudraksha Gupta
2022-08-09  0:03     ` [PATCH v2 2/2] ARM: msm8960: Add Samsung Galaxy Express support Rudraksha Gupta
2022-08-09  5:35       ` Krzysztof Kozlowski
2022-08-09 23:57         ` Rudraksha Gupta
2022-08-10  7:47           ` Krzysztof Kozlowski
2022-08-09  5:32     ` [PATCH v2 1/2] ARM: msm8960: Rename cxo_board to cxo-board and add alias Krzysztof Kozlowski
2022-08-10 19:53     ` Bjorn Andersson
2022-08-11  2:51       ` Rudraksha Gupta
2022-08-29 21:54         ` Bjorn Andersson
2023-02-21  6:40           ` Rudraksha Gupta [this message]
2022-08-09  5:30 ` [PATCH " Krzysztof Kozlowski

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=4778cc0a-77ad-b28f-bbf5-6247d26f81b4@gmail.com \
    --to=guptarud@gmail.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=david@ixit.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).