From: Stephen Boyd <sboyd@codeaurora.org>
To: Alexey Firago <alexey_firago@mentor.com>
Cc: mturquette@baylibre.com, robh+dt@kernel.org,
marek.vasut@gmail.com, geert@linux-m68k.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/3] clk: vc5: Add structure to describe particular chip features
Date: Wed, 19 Apr 2017 09:09:38 -0700 [thread overview]
Message-ID: <20170419160938.GV7065@codeaurora.org> (raw)
In-Reply-To: <1491556344-9465-2-git-send-email-alexey_firago@mentor.com>
On 04/07, Alexey Firago wrote:
> Introduce vc5_chip_info structure to describe features of a particular
> VC5 chip (id, number of FODs, number of outputs, flags).
> For now flags are only used to indicate if chip has internal XTAL.
> vc5_chip_info is set on probe from the matched of_device_id->data.
>
> Also add defines to specify maximum number of FODs and clock outputs
> supported by the driver.
>
> With these changes it should be easier to extend driver to support
> more VC5 models.
>
> Signed-off-by: Alexey Firago <alexey_firago@mentor.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Alexey Firago <alexey_firago-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
Cc: mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
marek.vasut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v4 1/3] clk: vc5: Add structure to describe particular chip features
Date: Wed, 19 Apr 2017 09:09:38 -0700 [thread overview]
Message-ID: <20170419160938.GV7065@codeaurora.org> (raw)
In-Reply-To: <1491556344-9465-2-git-send-email-alexey_firago-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
On 04/07, Alexey Firago wrote:
> Introduce vc5_chip_info structure to describe features of a particular
> VC5 chip (id, number of FODs, number of outputs, flags).
> For now flags are only used to indicate if chip has internal XTAL.
> vc5_chip_info is set on probe from the matched of_device_id->data.
>
> Also add defines to specify maximum number of FODs and clock outputs
> supported by the driver.
>
> With these changes it should be easier to extend driver to support
> more VC5 models.
>
> Signed-off-by: Alexey Firago <alexey_firago-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe devicetree" 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:[~2017-04-19 16:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 9:12 [PATCH v4 0/3] clk: Add support for IDT 5P49V5935 Alexey Firago
2017-04-07 9:12 ` Alexey Firago
2017-04-07 9:12 ` [PATCH v4 1/3] clk: vc5: Add structure to describe particular chip features Alexey Firago
2017-04-07 9:12 ` Alexey Firago
2017-04-07 19:55 ` Marek Vasut
2017-04-19 16:09 ` Stephen Boyd [this message]
2017-04-19 16:09 ` Stephen Boyd
2017-04-07 9:12 ` [PATCH v4 2/3] clk: vc5: Add bindings for IDT VersaClock 5P49V5935 Alexey Firago
2017-04-07 9:12 ` Alexey Firago
2017-04-07 19:56 ` Marek Vasut
2017-04-07 19:56 ` Marek Vasut
2017-04-10 20:10 ` Rob Herring
2017-04-10 20:10 ` Rob Herring
2017-04-19 16:09 ` Stephen Boyd
2017-04-19 16:09 ` Stephen Boyd
2017-04-07 9:12 ` [PATCH v4 3/3] clk: vc5: Add support " Alexey Firago
2017-04-07 9:12 ` Alexey Firago
2017-04-07 19:56 ` Marek Vasut
2017-04-07 19:56 ` Marek Vasut
2017-04-19 16:09 ` Stephen Boyd
2017-04-07 19:40 ` [PATCH v4 0/3] clk: Add support for IDT 5P49V5935 Stephen Boyd
2017-04-07 19:40 ` Stephen Boyd
2017-04-07 19:55 ` Marek Vasut
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=20170419160938.GV7065@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=alexey_firago@mentor.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-clk@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@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.