From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Raghavendra, Vignesh" <vigneshr@ti.com>,
Judith Mendez <jm@ti.com>, Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Nishanth Menon <nm@ti.com>, Andrew Davis <afd@ti.com>,
Udit Kumar <u-kumar1@ti.com>, Roger Quadros <rogerq@kernel.org>,
devicetree@vger.kernel.org, Randolph Sapp <rs@ti.com>
Subject: Re: [RFC PATCH 00/13] Add tuning algorithm for delay chain
Date: Thu, 1 Feb 2024 08:28:08 +0100 [thread overview]
Message-ID: <b94df34e-938b-4f89-97e2-ebfe694c8e7a@linaro.org> (raw)
In-Reply-To: <52b14b42-6e42-4435-b391-c3f48470e56c@ti.com>
On 31/01/2024 14:53, Raghavendra, Vignesh wrote:
>
>
> On 1/31/2024 7:11 PM, Krzysztof Kozlowski wrote:
>> On 31/01/2024 14:35, Raghavendra, Vignesh wrote:
>>>> Judith Mendez (11):
>>>> drivers: mmc: host: sdhci_am654: Add tuning algorithm for delay chain
>>>> drivers: mmc: host: sdhci_am654: Write ITAPDLY for DDR52 timing
>>>> drivers: mmc: host: sdhci_am654: Add missing OTAP/ITAP enable
>>>> drivers: mmc: host: sdhci_am654: Add ITAPDLYSEL in
>>>> sdhci_j721e_4bit_set_clock
>>>> drivers: mmc: host: sdhci_am654: Fix ITAPDLY for HS400 timing
>>>
>>> These patches needs to have Fixes: tag as they are bug fixes IMO.
>>>
>>>> arm64: dts: ti: k3-am62a-main: Add sdhci2 instance
>>>> arm64: dts: ti: k3-am64-main: Update ITAP/OTAP values for MMC
>>>> arm64: dts: ti: k3-am62-main: Update ITAP/OTAP values for MMC
>>>> arm64: dts: ti: k3-am62p: Add missing properties for MMC
>>>> arm64: dts: ti: k3-am6*: Remove DLL properties for soft phys
>>>> arm64: dts: ti: k3-am6*: Reorganize MMC properties
>>>>
>>>> Nitin Yadav (2):
>>>> arm64: dts: ti: k3-am62a-main: Add sdhci0 instance
>>>> arm64: dts: ti: k3-am62a7-sk: Enable eMMC support
>>>>
>>>
>>> Can the driver changes be merged independent of DT changes? Or are they
>>> meant to go together? Latter would be problematic as it creates cross
>>> tree dependencies.
>>
>> DTS cannot depend on driver changes, because that would mean hardware
>> description is not really hardware but OS. So the answer to your
>> question must be "yes, can be merged independently".
>>
>
> Normally yes, but here I see update to tuning algorithm and timing
> paramaters to the algorithm. DT updates seem to be nature of bug fixes
> where in parameters have been refined due to more HW char
> data/understanding being available.
Then the patchset should be probably split into fixes and new features,
so it would be clear that new DTS features do not depend on driver code.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-02-01 7:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 0:37 [RFC PATCH 00/13] Add tuning algorithm for delay chain Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 01/13] drivers: mmc: host: sdhci_am654: " Judith Mendez
2024-01-31 11:04 ` Vignesh Raghavendra
2024-01-31 20:27 ` Judith Mendez
2024-02-02 10:00 ` Roger Quadros
2024-01-31 0:37 ` [RFC PATCH 02/13] drivers: mmc: host: sdhci_am654: Write ITAPDLY for DDR52 timing Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 03/13] drivers: mmc: host: sdhci_am654: Add missing OTAP/ITAP enable Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 04/13] drivers: mmc: host: sdhci_am654: Add ITAPDLYSEL in sdhci_j721e_4bit_set_clock Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 05/13] drivers: mmc: host: sdhci_am654: Fix ITAPDLY for HS400 timing Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 06/13] arm64: dts: ti: k3-am62a-main: Add sdhci0 instance Judith Mendez
2024-01-31 19:17 ` Nishanth Menon
2024-01-31 20:28 ` Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 07/13] arm64: dts: ti: k3-am62a7-sk: Enable eMMC support Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 08/13] arm64: dts: ti: k3-am62a-main: Add sdhci2 instance Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 09/13] arm64: dts: ti: k3-am64-main: Update ITAP/OTAP values for MMC Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 10/13] arm64: dts: ti: k3-am62-main: " Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 11/13] arm64: dts: ti: k3-am62p: Add missing properties " Judith Mendez
2024-02-02 9:50 ` Roger Quadros
2024-02-12 23:38 ` Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 12/13] arm64: dts: ti: k3-am6*: Remove DLL properties for soft phys Judith Mendez
2024-01-31 0:37 ` [RFC PATCH 13/13] arm64: dts: ti: k3-am6*: Reorganize MMC properties Judith Mendez
2024-02-02 9:54 ` Roger Quadros
2024-02-12 23:41 ` Judith Mendez
2024-01-31 13:35 ` [RFC PATCH 00/13] Add tuning algorithm for delay chain Raghavendra, Vignesh
2024-01-31 13:41 ` Krzysztof Kozlowski
2024-01-31 13:53 ` Raghavendra, Vignesh
2024-02-01 7:28 ` Krzysztof Kozlowski [this message]
2024-01-31 20:41 ` Judith Mendez
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=b94df34e-938b-4f89-97e2-ebfe694c8e7a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jm@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=rs@ti.com \
--cc=u-kumar1@ti.com \
--cc=ulf.hansson@linaro.org \
--cc=vigneshr@ti.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).