public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ashish Mhetre <amhetre@nvidia.com>, Rob Herring <robh@kernel.org>
Cc: dmitry.osipenko@collabora.com, digetx@gmail.com,
	thierry.reding@gmail.com, jonathanh@nvidia.com,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
	vdumpa@nvidia.com, Snikam@nvidia.com
Subject: Re: [Patch v7 3/4] dt-bindings: memory: Update reg/reg-names validation
Date: Sun, 24 Apr 2022 16:34:46 +0200	[thread overview]
Message-ID: <47ccfe2d-5b96-2a76-90b7-6c3679dcec27@linaro.org> (raw)
In-Reply-To: <011311d4-7139-c10c-edd7-119f5466469e@nvidia.com>

On 24/04/2022 07:20, Ashish Mhetre wrote:
>>>
>>> New, added properties cannot be required. That's an ABI break.
>>>
>> This is handled in driver code to make sure driver works with old dts
>> as well. So is this bindings change fine or shall I change it such that
>> dt bindings check shall pass with older dts as well?
>> Or as mentioned by Dmitry, I can update the commit message to reflect
>> that ABI change is intended and driver is compatible with older DTBs as
>> well.
>>
> Hi Rob,
> Can you please confirm how shall I go in next version?
> Is it fine for dt bindings check to fail if driver is compatible with
> old as well as new dts? Or dt bindings check shall pass with old as
> well as new dts?
The driver works fine without reg-names and accepts old DTB, right? In
such case, just mention this in commit msg, that the bindings require
reg-names but backwards compatibility will be preserved in the driver. I
think it's fine to alter bindings such way.

Best regards,
Krzysztof

  reply	other threads:[~2022-04-24 14:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  9:40 [Patch v7 0/4] memory: tegra: Add MC channels and error logging Ashish Mhetre
2022-04-13  9:40 ` [Patch v7 1/4] memory: tegra: Add memory controller channels support Ashish Mhetre
2022-04-13 21:17   ` Dmitry Osipenko
2022-04-14  5:35     ` Ashish Mhetre
2022-04-14 21:11   ` Dmitry Osipenko
2022-04-13  9:40 ` [Patch v7 2/4] memory: tegra: Add MC error logging on tegra186 onward Ashish Mhetre
2022-04-13 21:13   ` Dmitry Osipenko
2022-04-14  5:31     ` Ashish Mhetre
2022-04-14 21:14       ` Dmitry Osipenko
2022-04-13 21:17   ` Dmitry Osipenko
2022-04-14 20:36   ` Dmitry Osipenko
2022-04-13  9:40 ` [Patch v7 3/4] dt-bindings: memory: Update reg/reg-names validation Ashish Mhetre
2022-04-13 12:26   ` Rob Herring
2022-04-13 13:37   ` Rob Herring
2022-04-13 14:04     ` Dmitry Osipenko
2022-04-13 16:17       ` Ashish Mhetre
2022-04-13 21:09         ` Dmitry Osipenko
2022-04-14  4:07           ` Ashish Mhetre
2022-04-14 20:35             ` Dmitry Osipenko
2022-04-17  9:27     ` Ashish Mhetre
2022-04-24  5:20       ` Ashish Mhetre
2022-04-24 14:34         ` Krzysztof Kozlowski [this message]
2022-04-25  4:48           ` Ashish Mhetre
2022-04-13  9:40 ` [Patch v7 4/4] arm64: tegra: Add memory controller channels Ashish Mhetre

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=47ccfe2d-5b96-2a76-90b7-6c3679dcec27@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=Snikam@nvidia.com \
    --cc=amhetre@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=dmitry.osipenko@collabora.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=vdumpa@nvidia.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