From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/3] Meson (32-bit) multi_v7_defconfig updates
Date: Mon, 12 Jun 2017 09:38:15 +0200 [thread overview]
Message-ID: <888ef3fd-d8aa-d09c-dace-8662a7fd9c5a@baylibre.com> (raw)
In-Reply-To: <20170611100343.25868-1-martin.blumenstingl@googlemail.com>
On 06/11/2017 12:03 PM, Martin Blumenstingl wrote:
> This enables the following drivers which are supported on Meson8 and
> Meson8b (as well as Meson8m2):
> - Meson USB2 PHY driver (USB controller support is provided by dwc2,
> which is already enabled)
> - Meson PWM driver (used to dim LEDs and generate the 32.768 kHz LPO
> clock for the SDIO wifi modules)
> - the generic PWM clock driver (for the 32.768 kHz LPO clock for the
> SDIO wifi modules)
>
>
> I am not sure if these patches will go through Kevin's Amlogic tree
> or through some other tree. However, these should be independent from
> anything else, so it's just a matter of preference through which tree
> they go.
>
>
> Martin Blumenstingl (3):
> ARM: multi_v7_defconfig: enable the Amlogic Meson USB2 PHY driver
> ARM: multi_v7_defconfig: enable the Meson PWM controller
> ARM: multi_v7_defconfig: enable the PWM clock driver
>
> arch/arm/configs/multi_v7_defconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
Hi Martin,
Isn't it better to have these as modules like for the ARM64 counterpart ?
Thanks,
Neil
next prev parent reply other threads:[~2017-06-12 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 10:03 Martin Blumenstingl
2017-06-11 10:03 ` [PATCH 1/3] ARM: multi_v7_defconfig: enable the Amlogic Meson USB2 PHY driver Martin Blumenstingl
2017-06-11 10:03 ` [PATCH 2/3] ARM: multi_v7_defconfig: enable the Meson PWM controller Martin Blumenstingl
2017-06-11 10:03 ` [PATCH 3/3] ARM: multi_v7_defconfig: enable the PWM clock driver Martin Blumenstingl
2017-06-12 7:38 ` Neil Armstrong [this message]
2017-06-14 21:36 ` [PATCH 0/3] Meson (32-bit) multi_v7_defconfig updates Martin Blumenstingl
2017-06-16 17:52 ` Kevin Hilman
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=888ef3fd-d8aa-d09c-dace-8662a7fd9c5a@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linus-amlogic@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
all inboxes | Powered by JetHome®