Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1442794 > unrolled thread
| Started by | Stephen Warren <swarren@wwwdotorg.org> |
|---|---|
| First post | 2016-07-13 21:50 +0200 |
| Last post | 2016-07-18 08:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH V2 03/10] Documentation: dt-bindings: firmware: tegra: add bindings of the BPMP Stephen Warren <swarren@wwwdotorg.org> - 2016-07-13 21:50 +0200
Re: [PATCH V2 03/10] Documentation: dt-bindings: firmware: tegra: add bindings of the BPMP Joseph Lo <josephl@nvidia.com> - 2016-07-18 08:50 +0200
| From | Stephen Warren <swarren@wwwdotorg.org> |
|---|---|
| Date | 2016-07-13 21:50 +0200 |
| Subject | Re: [PATCH V2 03/10] Documentation: dt-bindings: firmware: tegra: add bindings of the BPMP |
| Message-ID | <rUykp-7ut-11@gated-at.bofh.it> |
On 07/05/2016 03:04 AM, Joseph Lo wrote: > The BPMP is a specific processor in Tegra chip, which is designed for > booting process handling and offloading the power management, clock > management, and reset control tasks from the CPU. The binding document > defines the resources that would be used by the BPMP firmware driver, > which can create the interprocessor communication (IPC) between the CPU > and BPMP. > diff --git a/Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt b/Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt > +- Documentation/devicetree/bindings/mailbox/mailbox.txt > +- Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.txt > +- Documentation/devicetree/bindings/clock/clock-bindings.txt > +- include/dt-bindings/clock/tegra186-clock.h > +- Documentation/devicetree/bindings/reset/reset.txt > +- include/dt-bindings/reset/tegra186-reset.h If you end up needing to repost this, it would be nice to make all those file references more generic. In particular, some SW projects store binding docs somewhere other than Documentation/devicetree/bindings/ (e.g. U-Boot uses doc/device-tree-bindings/), and it's possible that the header files aren't stored in include/ but somewhere else. To make these file references valid everywhere, I'd suggest using relative paths for the binding docs, and #include style paths for the headers, e.g.: ../clock/clock-bindings.txt <dt-bindings/clock/tegra186-clock.h>
[toc] | [next] | [standalone]
| From | Joseph Lo <josephl@nvidia.com> |
|---|---|
| Date | 2016-07-18 08:50 +0200 |
| Message-ID | <rWaxk-2J5-15@gated-at.bofh.it> |
| In reply to | #1442794 |
On 07/14/2016 03:41 AM, Stephen Warren wrote: > On 07/05/2016 03:04 AM, Joseph Lo wrote: >> The BPMP is a specific processor in Tegra chip, which is designed for >> booting process handling and offloading the power management, clock >> management, and reset control tasks from the CPU. The binding document >> defines the resources that would be used by the BPMP firmware driver, >> which can create the interprocessor communication (IPC) between the CPU >> and BPMP. > >> diff --git >> a/Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt >> b/Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt > >> +- Documentation/devicetree/bindings/mailbox/mailbox.txt >> +- Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.txt > >> +- Documentation/devicetree/bindings/clock/clock-bindings.txt >> +- include/dt-bindings/clock/tegra186-clock.h >> +- Documentation/devicetree/bindings/reset/reset.txt >> +- include/dt-bindings/reset/tegra186-reset.h > > If you end up needing to repost this, it would be nice to make all those > file references more generic. In particular, some SW projects store > binding docs somewhere other than Documentation/devicetree/bindings/ > (e.g. U-Boot uses doc/device-tree-bindings/), and it's possible that the > header files aren't stored in include/ but somewhere else. To make these > file references valid everywhere, I'd suggest using relative paths for > the binding docs, and #include style paths for the headers, e.g.: > > ../clock/clock-bindings.txt > > <dt-bindings/clock/tegra186-clock.h> > OK. Will fix this. Thanks, -Joseph
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web