From: Andreas Schwab <schwab@suse.de>
To: Yash Shah <yash.shah@sifive.com>
Cc: Palmer Dabbelt <palmer@sifive.com>,
linux-pwm@vger.kernel.org, linux-riscv@lists.infradead.org,
Thierry Reding <thierry.reding@gmail.com>,
robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Sachin Ghadi <sachin.ghadi@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v8 0/2] PWM support for HiFive Unleashed
Date: Tue, 05 Mar 2019 09:32:06 +0100 [thread overview]
Message-ID: <mvmlg1tzpq1.fsf@suse.de> (raw)
In-Reply-To: <CAJ2_jOE=8_c6aN2FTQVt0wTpBAkL8BYyF3UFaMmqdvWYWAAmvg@mail.gmail.com> (Yash Shah's message of "Tue, 5 Mar 2019 13:55:41 +0530")
On Mär 05 2019, Yash Shah <yash.shah@sifive.com> wrote:
> On Mon, Mar 4, 2019 at 4:39 PM Andreas Schwab <schwab@suse.de> wrote:
>>
>> On Mär 01 2019, Yash Shah <yash.shah@sifive.com> wrote:
>>
>> > This patch series adds a PWM driver and DT documentation
>> > for HiFive Unleashed board. The patches are mostly based on
>> > Wesley's patch.
>>
>> That doesn't appear to work with the heartbeat trigger, the led doesn't
>> flash.
>
> Make sure you modify the DTS file
Which DTS file?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2019-03-05 8:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 10:53 [PATCH v8 0/2] PWM support for HiFive Unleashed Yash Shah
2019-03-01 10:53 ` [PATCH v8 1/2] pwm: sifive: Add DT documentation for SiFive PWM Controller Yash Shah
2019-03-01 10:53 ` [PATCH v8 2/2] pwm: sifive: Add a driver for SiFive SoC PWM Yash Shah
2019-03-07 15:27 ` Uwe Kleine-König
2019-03-08 11:29 ` Yash Shah
2019-03-08 11:57 ` Uwe Kleine-König
2019-03-11 11:40 ` Yash Shah
2019-03-11 13:29 ` Uwe Kleine-König
2019-03-12 6:52 ` Yash Shah
2019-03-04 11:09 ` [PATCH v8 0/2] PWM support for HiFive Unleashed Andreas Schwab
2019-03-05 8:25 ` Yash Shah
2019-03-05 8:32 ` Andreas Schwab [this message]
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=mvmlg1tzpq1.fsf@suse.de \
--to=schwab@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sachin.ghadi@sifive.com \
--cc=thierry.reding@gmail.com \
--cc=yash.shah@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).