From: Arend van Spriel <arend@broadcom.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: <linux-wireless@vger.kernel.org>, <zajec5@gmail.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <arnd@arndb.de>
Subject: Re: [PATCH 1/2] bcma: register bcma as device tree driver
Date: Sat, 13 Sep 2014 17:13:18 +0200 [thread overview]
Message-ID: <54145F0E.8000506@broadcom.com> (raw)
In-Reply-To: <1410615446-7639-1-git-send-email-hauke@hauke-m.de>
On 09/13/14 15:37, Hauke Mehrtens wrote:
> This driver is used by the bcm53xx ARM SoC code. Now it is possible to
> give the address of the chipcommon core in device tree and bcma will
> search for all the other cores.
>
> Signed-off-by: Hauke Mehrtens<hauke@hauke-m.de>
> ---
> Documentation/devicetree/bindings/bus/bcma.txt | 41 +++++++++++++
> drivers/bcma/bcma_private.h | 16 +++++
> drivers/bcma/host_soc.c | 82 ++++++++++++++++++++++++++
> drivers/bcma/main.c | 10 ++++
> include/linux/bcma/bcma.h | 2 +
> 5 files changed, 151 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/bcma.txt
>
> This is based on wireless-testing and should go into that tree.
>
> changes since:
> RFC:
> - reworded the irq description
> - improved the example
> - hocked into bcma_modeinit() and bcma_modexit()
>
> diff --git a/Documentation/devicetree/bindings/bus/bcma.txt b/Documentation/devicetree/bindings/bus/bcma.txt
> new file mode 100644
> index 0000000..17e095f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/bcma.txt
> @@ -0,0 +1,41 @@
> +Broadcom AIX SoC bcma bus driver
Hi Hauke,
First of all a typo used all over the place: AIX should be AXI.
The backplane in Broadcom SoC is ARM AXI with additional plugin option
to make it discoverable. Indeed the IRQ info is not included, but I see
no reason for specifying the register space for the cores in device-tree
as that is discoverable by bcma.
Regards,
Arend
WARNING: multiple messages have this Message-ID (diff)
From: arend@broadcom.com (Arend van Spriel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] bcma: register bcma as device tree driver
Date: Sat, 13 Sep 2014 17:13:18 +0200 [thread overview]
Message-ID: <54145F0E.8000506@broadcom.com> (raw)
In-Reply-To: <1410615446-7639-1-git-send-email-hauke@hauke-m.de>
On 09/13/14 15:37, Hauke Mehrtens wrote:
> This driver is used by the bcm53xx ARM SoC code. Now it is possible to
> give the address of the chipcommon core in device tree and bcma will
> search for all the other cores.
>
> Signed-off-by: Hauke Mehrtens<hauke@hauke-m.de>
> ---
> Documentation/devicetree/bindings/bus/bcma.txt | 41 +++++++++++++
> drivers/bcma/bcma_private.h | 16 +++++
> drivers/bcma/host_soc.c | 82 ++++++++++++++++++++++++++
> drivers/bcma/main.c | 10 ++++
> include/linux/bcma/bcma.h | 2 +
> 5 files changed, 151 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/bcma.txt
>
> This is based on wireless-testing and should go into that tree.
>
> changes since:
> RFC:
> - reworded the irq description
> - improved the example
> - hocked into bcma_modeinit() and bcma_modexit()
>
> diff --git a/Documentation/devicetree/bindings/bus/bcma.txt b/Documentation/devicetree/bindings/bus/bcma.txt
> new file mode 100644
> index 0000000..17e095f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/bcma.txt
> @@ -0,0 +1,41 @@
> +Broadcom AIX SoC bcma bus driver
Hi Hauke,
First of all a typo used all over the place: AIX should be AXI.
The backplane in Broadcom SoC is ARM AXI with additional plugin option
to make it discoverable. Indeed the IRQ info is not included, but I see
no reason for specifying the register space for the cores in device-tree
as that is discoverable by bcma.
Regards,
Arend
WARNING: multiple messages have this Message-ID (diff)
From: Arend van Spriel <arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
To: Hauke Mehrtens <hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org
Subject: Re: [PATCH 1/2] bcma: register bcma as device tree driver
Date: Sat, 13 Sep 2014 17:13:18 +0200 [thread overview]
Message-ID: <54145F0E.8000506@broadcom.com> (raw)
In-Reply-To: <1410615446-7639-1-git-send-email-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
On 09/13/14 15:37, Hauke Mehrtens wrote:
> This driver is used by the bcm53xx ARM SoC code. Now it is possible to
> give the address of the chipcommon core in device tree and bcma will
> search for all the other cores.
>
> Signed-off-by: Hauke Mehrtens<hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
> ---
> Documentation/devicetree/bindings/bus/bcma.txt | 41 +++++++++++++
> drivers/bcma/bcma_private.h | 16 +++++
> drivers/bcma/host_soc.c | 82 ++++++++++++++++++++++++++
> drivers/bcma/main.c | 10 ++++
> include/linux/bcma/bcma.h | 2 +
> 5 files changed, 151 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/bcma.txt
>
> This is based on wireless-testing and should go into that tree.
>
> changes since:
> RFC:
> - reworded the irq description
> - improved the example
> - hocked into bcma_modeinit() and bcma_modexit()
>
> diff --git a/Documentation/devicetree/bindings/bus/bcma.txt b/Documentation/devicetree/bindings/bus/bcma.txt
> new file mode 100644
> index 0000000..17e095f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/bcma.txt
> @@ -0,0 +1,41 @@
> +Broadcom AIX SoC bcma bus driver
Hi Hauke,
First of all a typo used all over the place: AIX should be AXI.
The backplane in Broadcom SoC is ARM AXI with additional plugin option
to make it discoverable. Indeed the IRQ info is not included, but I see
no reason for specifying the register space for the cores in device-tree
as that is discoverable by bcma.
Regards,
Arend
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-13 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 13:37 [PATCH 1/2] bcma: register bcma as device tree driver Hauke Mehrtens
2014-09-13 13:37 ` Hauke Mehrtens
2014-09-13 13:37 ` Hauke Mehrtens
2014-09-13 13:37 ` [PATCH 2/2] bcma: get IRQ numbers from dt Hauke Mehrtens
2014-09-13 13:37 ` Hauke Mehrtens
2014-09-13 13:37 ` Hauke Mehrtens
2014-09-13 15:13 ` Arend van Spriel [this message]
2014-09-13 15:13 ` [PATCH 1/2] bcma: register bcma as device tree driver Arend van Spriel
2014-09-13 15:13 ` Arend van Spriel
2014-09-13 16:02 ` Hauke Mehrtens
2014-09-13 16:02 ` Hauke Mehrtens
2014-09-13 16:02 ` Hauke Mehrtens
2014-09-13 16:40 ` Arend van Spriel
2014-09-13 16:40 ` Arend van Spriel
2014-09-13 16:40 ` Arend van Spriel
2014-09-14 17:16 ` Hauke Mehrtens
2014-09-14 17:16 ` Hauke Mehrtens
2014-09-14 17:16 ` Hauke Mehrtens
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=54145F0E.8000506@broadcom.com \
--to=arend@broadcom.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.