From: Teresa Remmet <t.remmet@phytec.de>
To: barebox@lists.infradead.org
Subject: [PATCH 0/7] Add ti-sysc bus driver
Date: Mon, 11 Feb 2019 16:16:33 +0100 [thread overview]
Message-ID: <1549898200-32688-1-git-send-email-t.remmet@phytec.de> (raw)
Hello,
with the device tree update to v5.0-rc2 most of the barebox devices
could not be enabled or probed any more. The am33xx*.dtsi files
have been updated to the interconnect target module hierarchy.
To make barebox working again we need a ti-sysc bus driver to
register the child devices of the ti-sysc bus.
Teresa
Teresa Remmet (7):
drivers: bus: Add ti-sysc bus driver
arm: configs: omap_defconfig: Enable ti-sysc bus driver
arm: configs: am33xx_mlo_defconfig: Enable ti-sysc bus driver
drivers: of: Add function to enable and register a device by alias
arm: mach-omap: am335x_generic: Enable nodes by alias where needed
net: ethernet: cpsw: cpsw-phy-sel: Use phandle for phy sel
arm: dts: am335x-phytec: Use phy-handle instead of phy_id
arch/arm/configs/am335x_mlo_defconfig | 2 +-
arch/arm/configs/omap_defconfig | 2 +-
arch/arm/dts/am335x-phytec-phycard-som.dtsi | 7 ++++-
arch/arm/dts/am335x-phytec-phycore-som.dtsi | 7 ++++-
arch/arm/dts/am335x-phytec-phyflex-som.dtsi | 12 ++++++--
arch/arm/mach-omap/am33xx_generic.c | 8 ++---
drivers/bus/Kconfig | 7 +++++
drivers/bus/Makefile | 1 +
drivers/bus/ti-sysc.c | 45 +++++++++++++++++++++++++++++
drivers/net/cpsw.c | 17 +++++++----
drivers/of/platform.c | 19 ++++++++++++
include/of.h | 8 +++++
12 files changed, 119 insertions(+), 16 deletions(-)
create mode 100644 drivers/bus/ti-sysc.c
--
2.7.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2019-02-11 15:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 15:16 Teresa Remmet [this message]
2019-02-11 15:16 ` [PATCH 1/7] drivers: bus: " Teresa Remmet
2019-02-11 15:41 ` Sam Ravnborg
2019-02-12 8:09 ` Sascha Hauer
2019-02-12 13:23 ` Teresa Remmet
2019-02-12 16:32 ` Sam Ravnborg
2019-02-12 2:57 ` Andrey Smirnov
2019-02-12 13:13 ` Teresa Remmet
2019-02-13 0:56 ` Andrey Smirnov
2019-02-13 8:19 ` Teresa Remmet
2019-02-12 8:10 ` Sascha Hauer
2019-02-12 13:25 ` Teresa Remmet
2019-02-11 15:16 ` [PATCH 2/7] arm: configs: omap_defconfig: Enable " Teresa Remmet
2019-02-11 15:16 ` [PATCH 3/7] arm: configs: am33xx_mlo_defconfig: " Teresa Remmet
2019-02-11 15:16 ` [PATCH 4/7] drivers: of: Add function to enable and register a device by alias Teresa Remmet
2019-02-11 15:16 ` [PATCH 5/7] arm: mach-omap: am335x_generic: Enable nodes by alias where needed Teresa Remmet
2019-02-11 15:16 ` [PATCH 6/7] net: ethernet: cpsw: cpsw-phy-sel: Use phandle for phy sel Teresa Remmet
2019-02-11 15:16 ` [PATCH 7/7] arm: dts: am335x-phytec: Use phy-handle instead of phy_id Teresa Remmet
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=1549898200-32688-1-git-send-email-t.remmet@phytec.de \
--to=t.remmet@phytec.de \
--cc=barebox@lists.infradead.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