From: Amit Sunil Dhamne <amitsd@google.com>
To: gregkh@linuxfoundation.org, robh@kernel.org,
dmitry.baryshkov@linaro.org, heikki.krogerus@linux.intel.com
Cc: badhri@google.com, kyletso@google.com, rdbabiera@google.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org,
Amit Sunil Dhamne <amitsd@google.com>
Subject: [RFC v2 0/2] Add support for time DT property in TCPM
Date: Thu, 19 Sep 2024 00:51:12 -0700 [thread overview]
Message-ID: <20240919075120.328469-1-amitsd@google.com> (raw)
USB PD specification defines a bunch of timers that can have a range of
acceptable values instead of specific values. These values have to be
tuned based on the platform. However, TCPM currently sets them to a
default value without providing a mechanism to set platform specific
values.
This patchset adds new DT properties per timer to allow users to define
platform specific values.
Changes compared to v1:
- Defined new properties per timer that we are interested in rather
than defining a single pd-timers u32 array property.
- Better description of the timer properties.
- Since subject has changed, adding link for previous patchset for
posterity:
https://lore.kernel.org/all/20240911000715.554184-1-amitsd@google.com/
Amit Sunil Dhamne (2):
dt-bindings: connector: Add properties to define time values
usb: typec: tcpm: Add support for parsing time dt properties
.../bindings/connector/usb-connector.yaml | 32 +++++++-
drivers/usb/typec/tcpm/tcpm.c | 81 +++++++++++++++----
2 files changed, 96 insertions(+), 17 deletions(-)
base-commit: 68d4209158f43a558c5553ea95ab0c8975eab18c
--
2.46.0.792.g87dc391469-goog
next reply other threads:[~2024-09-19 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 7:51 Amit Sunil Dhamne [this message]
2024-09-19 7:51 ` [RFC v2 1/2] dt-bindings: connector: Add properties to define time values Amit Sunil Dhamne
2024-09-21 0:56 ` Rob Herring
2024-09-19 7:51 ` [RFC v2 2/2] usb: typec: tcpm: Add support for parsing time dt properties Amit Sunil Dhamne
2024-09-19 8:56 ` Dmitry Baryshkov
2024-09-19 22:08 ` Amit Sunil Dhamne
2024-09-19 13:32 ` Heikki Krogerus
2024-09-19 22:15 ` Amit Sunil Dhamne
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=20240919075120.328469-1-amitsd@google.com \
--to=amitsd@google.com \
--cc=badhri@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kyletso@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdbabiera@google.com \
--cc=robh@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).