From: peter.griffin@linaro.org (Peter Griffin)
To: linux-arm-kernel@lists.infradead.org
Subject: [STLinux Kernel] [PATCH 4/7] ARM: stih416-b2020e: Enable PWM on the B2020 Rev-E
Date: Thu, 19 Jun 2014 14:29:59 +0100 [thread overview]
Message-ID: <20140619132959.GA22592@griffinp-ThinkPad-X1-Carbon-2nd> (raw)
In-Reply-To: <20140619112239.GC26560@lee--X1>
Hi Lee,
> > > Purely for testing purposes, as it's the only board I have. If
> > > anyone has the other revisions and would be happy to test the driver
> > > for me then great.
> >
> > Ok that's what I suspected.
> >
> > If you tell me how, I can test on a Rev C board. But as there are several other
> > revisions I think checking the board schematics would be the quickest way forward.
>
> Great. Do you have a oscilloscope/logic analyser?
I have an old scope, and I've been wanting to buy a decent logic analyser ;-)
Also can you email me the rev E schematic? I currently only have rev C.
> > > > If you make the stih415 DT PWM nodes part of this series as well, then
> > > > assuming there is no good reason to the contary, the PWM could
> > > > be enabled for both stih415/6 in the common stih41x-b2020 DTS file which
> > > > is also included by rev-E (assuming that PWM wiring is not some rev-E specific
> > > > thing).
> >
> > Can you add the stih415 bindings in V2 as well?
>
> Who's using Orly1?
I'll let ST answer that.
AFAIK drivers upstreamed so far for Orly based hardware have generally been enabled for both
SoCs, hence querying why the stih415 bindings are missing from this series.
Being pinout compatible, a b2020 board can be populated with a stih415, so it seems strange
for it to then be missing PWM support given that the SoC, board and pwm driver all support it.
regards,
Peter.
next prev parent reply other threads:[~2014-06-19 13:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 14:52 [PATCH 1/7] ARM: stih407: Add DT nodes for for PWM Lee Jones
2014-06-18 14:52 ` [PATCH 2/7] ARM: stih416: Add Pinctrl settings " Lee Jones
2014-06-18 14:52 ` [PATCH 3/7] ARM: stih416: Add DT nodes " Lee Jones
2014-06-18 15:08 ` Gabriel Fernandez
2014-06-18 15:17 ` Lee Jones
2014-06-18 15:28 ` [PATCH v2 " Lee Jones
2014-06-18 14:52 ` [PATCH 4/7] ARM: stih416-b2020e: Enable PWM on the B2020 Rev-E Lee Jones
2014-06-19 9:05 ` [STLinux Kernel] " Peter Griffin
2014-06-19 9:20 ` Lee Jones
2014-06-19 10:12 ` Peter Griffin
2014-06-19 10:59 ` Maxime Coquelin
2014-06-19 11:22 ` Lee Jones
2014-06-19 13:29 ` Peter Griffin [this message]
2014-06-18 14:52 ` [PATCH 5/7] ARM: multi_v7_defconfig: Enable ST's PWM driver Lee Jones
2014-06-18 14:52 ` [PATCH 6/7] pwm: st: Add new driver for ST's PWM IP Lee Jones
2014-06-18 23:11 ` Thierry Reding
2014-06-19 8:44 ` Lee Jones
2014-06-19 11:32 ` Russell King - ARM Linux
2014-06-19 14:27 ` Ajit Pal
2014-06-20 22:27 ` Thierry Reding
2014-06-20 22:16 ` Thierry Reding
2014-06-18 14:52 ` [PATCH 7/7] pwm: st: Supply Device Tree binding documentation " Lee Jones
2014-06-18 15:08 ` Gabriel Fernandez
2014-06-18 15:16 ` Lee Jones
2014-06-18 15:29 ` [PATCH v2 " Lee Jones
2014-06-18 15:07 ` [PATCH 1/7] ARM: stih407: Add DT nodes for for PWM Gabriel Fernandez
2014-06-18 15:16 ` Lee Jones
2014-06-18 15:26 ` [PATCH v2 " Lee Jones
2014-06-19 8:38 ` [STLinux Kernel] [PATCH " Peter Griffin
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=20140619132959.GA22592@griffinp-ThinkPad-X1-Carbon-2nd \
--to=peter.griffin@linaro.org \
--cc=linux-arm-kernel@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