From: Florian Fainelli <f.fainelli@gmail.com>
To: arm@kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>,
Shawn Guo <shawn.guo@linaro.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Alexander Shiyan <shc_work@mail.ru>,
Huang Shijie <b32955@freescale.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v2 0/3] bus: add Broadcom GISB bus arbiter timeout/error handler
Date: Mon, 19 May 2014 13:05:58 -0700 [thread overview]
Message-ID: <1400529962-9612-1-git-send-email-f.fainelli@gmail.com> (raw)
Hi all,
This patch adds support for the Broadcom GISB bus arbiter timeout/error handler.
GISB is a custom and proprietary bus used in the Broadcom Set Top Box devices
exclusively. The bus arbiter offers the possibly to decode faulting masters as
well as masters that are timing out on the bus.
V2 addresses some comments made by Arnd, and widens the audience by posting
on linux-arm-kernel as well.
These patches should be merged via the 'arm-soc' tree. I am resending those
such that every mailing-list has them in copy.
Thank you!
Florian Fainelli (3):
bus: add Broadcom GISB arbiter bus timeout/error handler
Documentation: devicetree: add Broadcom GISB arbiter bindings
Documentation: sysfs: add Broadcom GISB arbiter sysfs properties
.../ABI/testing/sysfs-platform-brcmstb-gisb-arb | 8 +
.../devicetree/bindings/bus/brcm,gisb-arb.txt | 30 +++
drivers/bus/Kconfig | 11 +-
drivers/bus/Makefile | 1 +
drivers/bus/brcmstb_gisb.c | 289 +++++++++++++++++++++
5 files changed, 338 insertions(+), 1 deletion(-)
create mode 100644 Documentation/ABI/testing/sysfs-platform-brcmstb-gisb-arb
create mode 100644 Documentation/devicetree/bindings/bus/brcm,gisb-arb.txt
create mode 100644 drivers/bus/brcmstb_gisb.c
--
1.9.1
next reply other threads:[~2014-05-19 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 20:05 Florian Fainelli [this message]
2014-05-19 20:05 ` [PATCH RESEND v2 1/3] bus: add Broadcom GISB bus arbiter timeout/error handler Florian Fainelli
2014-05-19 20:06 ` [PATCH RESEND v2 2/3] Documentation: devicetree: add Broadcom GISB arbiter bindings Florian Fainelli
2014-05-19 20:06 ` [PATCH RESEND v2 3/3] Documentation: sysfs: add Broadcom GISB arbiter sysfs properties Florian Fainelli
2014-05-23 23:00 ` [PATCH RESEND v2 0/3] bus: add Broadcom GISB bus arbiter timeout/error handler Arnd Bergmann
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=1400529962-9612-1-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arm@kernel.org \
--cc=b32955@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=nicolas.pitre@linaro.org \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=shc_work@mail.ru \
/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).