From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: dri-devel@lists.freedesktop.org,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Subject: Question regarding clocks in the DW-HDMI DT bindings
Date: Thu, 24 Nov 2016 23:16:05 +0200 [thread overview]
Message-ID: <2778019.JJI4Lz6scm@avalon> (raw)
Hi Andy,
As the author of the DW-HDMI DT bindings this question is addressed to you,
but information from anyone is more than welcome.
The DT bindings specify two clocks named "iahb" and "isfr" but don't describe
them. While I assume that the "isfr" clock corresponds to the "isfrclk" input
signal of the DW HDMI, there is no "iahb" clock described in the IP core
datasheet.
The DW HDMI IP exposes control registers through an APB, not an AHB. There is
a bus clock named "iapbclk", is "iahb" just an incorrect name for that clock ?
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-11-24 21:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 21:16 Laurent Pinchart [this message]
2016-11-24 22:07 ` Question regarding clocks in the DW-HDMI DT bindings Fabio Estevam
2016-11-24 22:16 ` Vladimir Zapolskiy
2016-11-24 22:28 ` Fabio Estevam
2016-11-24 23:26 ` Laurent Pinchart
2016-11-25 2:56 ` Andy Yan
2016-11-25 15:22 ` Laurent Pinchart
2016-11-25 15:29 ` Fabio Estevam
2016-11-25 15:56 ` Laurent Pinchart
[not found] ` <CAOMZO5CJTu7jzCb-iVLe2wt8VjyzWq-oYaC2Jw34V8SgaqrGkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-03 17:16 ` Laurent Pinchart
2016-12-03 21:10 ` Vladimir Zapolskiy
2016-12-05 6:52 ` Laurent Pinchart
2016-11-28 21:56 ` Michael Turquette
[not found] ` <CAEG3pNDtMY+Pf1_w6vQEswaMVZ=jOC69R749jSFwB2NiU8r58Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-29 6:04 ` Laurent Pinchart
2016-11-29 6:27 ` Michael Turquette
[not found] ` <CAEG3pNCTH5YUjO8m-jd1rfRRKRus7c39W4rYK56c6NdfQsOcyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-29 9:18 ` Laurent Pinchart
2016-11-25 12:43 ` Fabio Estevam
2016-11-25 13:25 ` Laurent Pinchart
2016-11-25 12:29 ` Fabio Estevam
2016-11-25 13:00 ` Vladimir Zapolskiy
2016-11-25 13:06 ` Fabio Estevam
2016-11-25 13:36 ` Vladimir Zapolskiy
2016-11-25 9:56 ` Philipp Zabel
2016-11-25 15:45 ` Laurent Pinchart
2016-11-25 16:08 ` Philipp Zabel
2016-11-25 19:26 ` Laurent Pinchart
2016-11-28 11:34 ` Andy Yan
2016-11-28 11:45 ` Laurent Pinchart
2016-11-28 12:09 ` Jose Abreu
2016-11-28 14:24 ` Laurent Pinchart
2016-11-28 15:25 ` Jose Abreu
2016-11-28 19:19 ` Laurent Pinchart
2016-11-29 11:06 ` Jose Abreu
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=2778019.JJI4Lz6scm@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=andy.yan@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=vladimir_zapolskiy@mentor.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).