From: djw at t-chip.com.cn <djw@t-chip.com.cn>
To: u-boot@lists.denx.de
Subject: [U-Boot] rockchip: missing request op in common pinctrl driver resulting kernel boot failure
Date: Mon, 17 Jun 2019 15:44:55 +0800 [thread overview]
Message-ID: <87v9x4fyfc.fsf_-_@t-chip.com.cn> (raw)
In-Reply-To: <54386d8e47424022@bloch.sibelius.xs4all.nl> (Mark Kettenis's message of "Fri, 14 Jun 2019 16:52:34 +0200 (CEST)")
Since this request is a no-op, it is best to drop the
pinctrl_request_noflags(pinctrl, PERIPH_ID_PWM?) lines in
board/rockchip/evb_rk3399/evb-rk3399.c (there're no such code lines in other
rk3399 board files), which is tested to work with the Firefly-RK3399 board.
Therefore, are the PERIPH_ID_PWM? taken care of somewhere in other places?
--
Best Regards,
Levin Du
prev parent reply other threads:[~2019-06-17 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 9:09 [U-Boot] rockchip: missing request op in common pinctrl driver resulting kernel boot failure Levin Du
2019-06-14 14:52 ` Mark Kettenis
2019-06-17 7:44 ` djw at t-chip.com.cn [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=87v9x4fyfc.fsf_-_@t-chip.com.cn \
--to=djw@t-chip.com.cn \
--cc=u-boot@lists.denx.de \
/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