From: Dilip Kota <eswara.kota@linux.intel.com>
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: kishon@ti.com, robh@kernel.org, andriy.shevchenko@intel.com,
cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com,
qi-ming.wu@intel.com, yixin.zhu@intel.com,
Dilip Kota <eswara.kota@linux.intel.com>
Subject: [PATCH v4 0/3] Add Intel ComboPhy driver
Date: Mon, 2 Mar 2020 16:43:22 +0800 [thread overview]
Message-ID: <cover.1583127977.git.eswara.kota@linux.intel.com> (raw)
This patch series adds Intel Combophy driver, respective yaml schemas
and a kernel API fwnode_to_regmap().
ComboPhy driver calls it to get regmap handle through firmware node.
Dilip Kota (3):
mfd: syscon: Add fwnode_to_regmap
dt-bindings: phy: Add YAML schemas for Intel Combophy
phy: intel: Add driver support for Combophy
.../devicetree/bindings/phy/intel,combo-phy.yaml | 123 ++++
drivers/mfd/syscon.c | 8 +
drivers/phy/intel/Kconfig | 14 +
drivers/phy/intel/Makefile | 1 +
drivers/phy/intel/phy-intel-combo.c | 661 +++++++++++++++++++++
include/dt-bindings/phy/phy-intel-combophy.h | 10 +
include/linux/mfd/syscon.h | 6 +
7 files changed, 823 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/intel,combo-phy.yaml
create mode 100644 drivers/phy/intel/phy-intel-combo.c
create mode 100644 include/dt-bindings/phy/phy-intel-combophy.h
--
2.11.0
next reply other threads:[~2020-03-02 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 8:43 Dilip Kota [this message]
2020-03-02 8:43 ` [PATCH v4 1/3] mfd: syscon: Add fwnode_to_regmap Dilip Kota
2020-03-02 8:43 ` [PATCH v4 2/3] dt-bindings: phy: Add YAML schemas for Intel Combophy Dilip Kota
2020-03-03 1:50 ` Rob Herring
2020-03-03 9:24 ` Dilip Kota
2020-03-03 16:26 ` Rob Herring
2020-03-04 9:16 ` Dilip Kota
2020-03-13 8:36 ` Dilip Kota
2020-03-02 8:43 ` [PATCH v4 3/3] phy: intel: Add driver support for ComboPhy Dilip Kota
2020-03-02 11:19 ` Andy Shevchenko
2020-03-03 8:41 ` Dilip Kota
2020-03-03 10:07 ` Andy Shevchenko
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=cover.1583127977.git.eswara.kota@linux.intel.com \
--to=eswara.kota@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi-ming.wu@intel.com \
--cc=robh@kernel.org \
--cc=yixin.zhu@intel.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).