From: "Hawkins, Nick" <nick.hawkins@hpe.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"Verdun, Jean-Marie" <verdun@hpe.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"wsa@kernel.org" <wsa@kernel.org>
Subject: Re: [PATCH v5 3/5] ARM: dts: hpe: Add I2C Topology
Date: Thu, 23 Feb 2023 21:02:36 +0000 [thread overview]
Message-ID: <66D4DB5E-46AA-4280-A073-E22262F7FD58@hpe.com> (raw)
In-Reply-To: <dc708865-6005-760f-cbb0-cb2d1d989b9d@linaro.org>
> clock-frequency is a property of the board. If it is fixed in the SoC,
> then make it fixed in the driver and there is no point for this property
> in DT.
Greetings Krzysztof,
It can be other values however if this property is missing the code will
default to this value.
I will remove it.
Thanks,
-Nick Hawkins
next prev parent reply other threads:[~2023-02-23 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 15:50 [PATCH v5 0/5] ARM: Add GXP I2C Support nick.hawkins
2023-02-17 15:50 ` [PATCH v5 1/5] i2c: hpe: Add GXP SoC I2C Controller nick.hawkins
2023-02-17 22:08 ` Wolfram Sang
2023-02-17 15:50 ` [PATCH v5 2/5] dt-bindings: i2c: Add hpe,gxp-i2c nick.hawkins
2023-02-17 22:08 ` Wolfram Sang
2023-02-17 15:50 ` [PATCH v5 3/5] ARM: dts: hpe: Add I2C Topology nick.hawkins
2023-02-18 10:10 ` Krzysztof Kozlowski
2023-02-23 21:02 ` Hawkins, Nick [this message]
2023-02-24 8:25 ` Krzysztof Kozlowski
2023-02-17 15:50 ` [PATCH v5 4/5] ARM: multi_v7_defconfig: add gxp i2c module nick.hawkins
2023-02-17 15:50 ` [PATCH v5 5/5] MAINTAINERS: Add HPE GXP I2C Support nick.hawkins
2023-02-17 22:09 ` Wolfram Sang
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=66D4DB5E-46AA-4280-A073-E22262F7FD58@hpe.com \
--to=nick.hawkins@hpe.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=verdun@hpe.com \
--cc=wsa@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
all inboxes | Powered by JetHome®