mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sriranjani P <sriranjani.p@samsung.com>,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	lee@kernel.org, devicetree@vger.kernel.org,
	alim.akhtar@samsung.com, pankaj.dubey@samsung.com,
	ravi.patel@samsung.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: fsd: add sysreg device node
Date: Thu, 24 Nov 2022 10:19:53 +0100	[thread overview]
Message-ID: <2751584a-782e-2bdd-b72d-4a726e6ede8d@linaro.org> (raw)
In-Reply-To: <001601d8ff41$231deaf0$6959c0d0$@samsung.com>

On 23/11/2022 14:40, Sriranjani P wrote:
>>
>>>
>>> So I can think of following two approaches:
>>> 1: For the time being I will put this sysreg node in between
>>> clock_peric node and clock_fysys0 node and clock_fsys1 node as per
>>> increasing unit address. I will clean up other exynos and FSD DTSI
>>> files and post a new patch
>>
>> Not sure what cleaning you have in mind.
>>
>>> 2: First I will clean up exynos and FSD DTSI files and then post this sysreg
>> patch keeping it at appropriate place.
>>
>> What cleaning?
> 
> By cleaning I meant fixing these dtsi files to have the device nodes in the order of ascending unit address.

Such cleanup is fine.

Best regards,
Krzysztof


  reply	other threads:[~2022-11-24  9:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221121090555epcas5p29c8c7de6dba38449aaf3357beb43432d@epcas5p2.samsung.com>
2022-11-21  9:11 ` [PATCH 0/2] arm64: dts: Add SYSREG nodes for FSD SoC Sriranjani P
     [not found]   ` <CGME20221121090622epcas5p4cbce7d07007fc76d3c69e0013d3c4cf4@epcas5p4.samsung.com>
2022-11-21  9:11     ` [PATCH 1/2] dt-bindings: mfd: syscon: Add tesla compatibles found on " Sriranjani P
2022-11-21 12:25       ` Lee Jones
2022-11-23 12:02         ` Sriranjani P
     [not found]   ` <CGME20221121090647epcas5p439dc84f0c4f435a703a1f8396a11202f@epcas5p4.samsung.com>
2022-11-21  9:11     ` [PATCH 2/2] arm64: dts: fsd: add sysreg device node Sriranjani P
2022-11-21 12:27       ` Krzysztof Kozlowski
2022-11-23 11:57         ` Sriranjani P
2022-11-23 13:12           ` Krzysztof Kozlowski
2022-11-23 13:40             ` Sriranjani P
2022-11-24  9:19               ` Krzysztof Kozlowski [this message]
2022-11-21 12:31   ` [PATCH 0/2] arm64: dts: Add SYSREG nodes for FSD SoC 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=2751584a-782e-2bdd-b72d-4a726e6ede8d@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=alim.akhtar@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pankaj.dubey@samsung.com \
    --cc=ravi.patel@samsung.com \
    --cc=robh+dt@kernel.org \
    --cc=sriranjani.p@samsung.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

all inboxes | Powered by JetHome®