Message ID | 1376673628-5867-3-git-send-email-swarren@wwwdotorg.org |
---|---|
State | New |
Headers | show |
Stephen Warren <swarren@wwwdotorg.org> writes: > This branch contains all *.dts (device tree) changes for Tegra. > New features enabled are: > > * PMICs on Dalmore > * CPU power-gating on Dalmore > * HDMI output on Beaver > * LP1 system suspend mode on almost all boards > * PCIe support on numerous Tegra20/30 boards > * USB support on Tegra30/114 boards > * Audio capture on Beaver and Dalmore > * Temperature sensor on Cardhu. > > ... along with a few DT cleanups. Hmm, shouldn't I have a DT maintainer signoff on this stuff... oh, wait... ;) > ---------------------------------------------------------------- > > The following changes since commit ad81f0545ef01ea651886dddac4bef6cec930092: > > Linux 3.11-rc1 > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git tegra-for-3.12-dt > > for you to fetch changes up to 8af3bbec752902c0480c84613d7f10e22f485977: > > ARM: tegra: add Mic Jack to Dalmore device tree Pulled into next/dt. Kevin
On 08/20/2013 05:45 PM, Kevin Hilman wrote: > Stephen Warren <swarren@wwwdotorg.org> writes: > >> This branch contains all *.dts (device tree) changes for Tegra. >> New features enabled are: >> >> * PMICs on Dalmore >> * CPU power-gating on Dalmore >> * HDMI output on Beaver >> * LP1 system suspend mode on almost all boards >> * PCIe support on numerous Tegra20/30 boards >> * USB support on Tegra30/114 boards >> * Audio capture on Beaver and Dalmore >> * Temperature sensor on Cardhu. >> >> ... along with a few DT cleanups. > > Hmm, shouldn't I have a DT maintainer signoff on this stuff... oh, > wait... ;) One thought here on my DT binding maintainer role (hence CCing the other DT maintainers): I assume that the DT maintainers are reviewing the DT bindings, and not the *.dts files. There's certainly so much email defining/modifying bindings that I can't even keep up with that. So, I deliberately don't even attempt to look at anything other than the binding changes. Is this not what the role entails? If the role is supposed to include reviewing *.dts changes, then perhaps I should wait until someone else has reviewed such patches before applying them to the Tegra tree? Of course, as Tegra maintainer I do actively look at the specific *.dts changes that go through my own tree.
Stephen Warren <swarren@wwwdotorg.org> writes: > On 08/20/2013 05:45 PM, Kevin Hilman wrote: >> Stephen Warren <swarren@wwwdotorg.org> writes: >> >>> This branch contains all *.dts (device tree) changes for Tegra. >>> New features enabled are: >>> >>> * PMICs on Dalmore >>> * CPU power-gating on Dalmore >>> * HDMI output on Beaver >>> * LP1 system suspend mode on almost all boards >>> * PCIe support on numerous Tegra20/30 boards >>> * USB support on Tegra30/114 boards >>> * Audio capture on Beaver and Dalmore >>> * Temperature sensor on Cardhu. >>> >>> ... along with a few DT cleanups. >> >> Hmm, shouldn't I have a DT maintainer signoff on this stuff... oh, >> wait... ;) > > One thought here on my DT binding maintainer role (hence CCing the other > DT maintainers): > > I assume that the DT maintainers are reviewing the DT bindings, and not > the *.dts files. There's certainly so much email defining/modifying > bindings that I can't even keep up with that. So, I deliberately don't > even attempt to look at anything other than the binding changes. Is this > not what the role entails? If the role is supposed to include reviewing > *.dts changes, then perhaps I should wait until someone else has > reviewed such patches before applying them to the Tegra tree? I was assuming that the DT maintainers would primarily focus on bindings. The platform maintainers should be primarily responsible for the .dts files. That being said, there will be no harm done if the DT reviewers have some bandwidth to look at .dts files too. :) > Of course, as Tegra maintainer I do actively look at the specific *.dts > changes that go through my own tree. Phew. Kevin