From: Florian Fainelli <f.fainelli@gmail.com>
To: Al Cooper <alcooperx@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH V2 1/2] soc: brcmstb: Add Product ID and Family ID helper functions
Date: Mon, 11 Jul 2016 17:12:58 -0700 [thread overview]
Message-ID: <5784360A.60206@gmail.com> (raw)
In-Reply-To: <1464379050-30091-2-git-send-email-alcooperx@gmail.com>
On 05/27/2016 12:57 PM, Al Cooper wrote:
> Signed-off-by: Al Cooper <alcooperx@gmail.com>
> ---
> drivers/soc/brcmstb/common.c | 12 ++++++++++++
> include/linux/soc/brcmstb/brcmstb.h | 10 ++++++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/drivers/soc/brcmstb/common.c b/drivers/soc/brcmstb/common.c
> index 94e7335..454f4c2 100644
> --- a/drivers/soc/brcmstb/common.c
> +++ b/drivers/soc/brcmstb/common.c
> @@ -40,6 +40,18 @@ bool soc_is_brcmstb(void)
> return of_match_node(brcmstb_machine_match, root) != NULL;
> }
>
> +u32 brcmstb_get_family_id(void)
> +{
> + return family_id;
> +}
> +EXPORT_SYMBOL(brcmstb_get_family_id);
> +
> +u32 brcmstb_get_product_id(void)
> +{
> + return product_id;
> +}
> +EXPORT_SYMBOL(brcmstb_get_product_id);
Looping in Arnd, since he has been working on a generic solution to
allow drivers to match specific SoC id/revisions. Arnd, I could not
quite locate your patches, do you mind pasting a link?
--
Florian
next prev parent reply other threads:[~2016-07-12 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 19:57 [PATCH V2 0/2] Add Broadcom USB PHY driver for Broadcom STB SoCs Al Cooper
2016-05-27 19:57 ` [PATCH V2 1/2] soc: brcmstb: Add Product ID and Family ID helper functions Al Cooper
2016-07-12 0:12 ` Florian Fainelli [this message]
2016-05-27 19:57 ` [PATCH V2 2/2] usb: phy: phy-brcm-usb: Add Broadcom STB USB Phy driver Al Cooper
2016-07-12 0:16 ` Florian Fainelli
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=5784360A.60206@gmail.com \
--to=f.fainelli@gmail.com \
--cc=alcooperx@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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 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.