Tony Lindgren <tony@xxxxxxxxxxx> writes: > The following changes since commit 254f57a92987b6cde6004f58d6b847813dfb9e0e: > > ARM: OMAP5: hwmod: add missing ocp2scp hwmod data (2013-10-11 15:37:05 -0700) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.13/am43xx-hwmod-signed > > for you to fetch changes up to 811e7c87340b75dce5c488d9496075b00853942b: > > Merge tag 'for-v3.13/am43xx-support' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v3.13/hwmod (2013-10-17 10:37:27 -0700) > > ---------------------------------------------------------------- > > Changes needed for am43xx for the hwmod data. > > This will be the last new set of hwmod data for any SoC > as future SoCs will use a driver and device tree based > approach. But before that can be dealt with, we need to > first sort out the pending driver/clk issues. > > Queued by Paul Walmsley <paul@xxxxxxxxx>: > > Add hwmod and PRCM data for the TI AM43xx family of SoCs. > > Under normal circumstances, these patches would not be merged. > The hwmod and PRCM data should be moved out either to DT data or > to drivers/. Also, the current implementation trades off lines > of diff by dynamically rewriting static data at runtime, which is > a bad practice - it causes future maintenance headaches. > However, after speaking with my upstream, it sounds like it's > better to merge these patches in their current state, due to long > term considerations. > > Basic test logs are here: > > http://www.pwsan.com/omap/testlogs/am43xx_support_v3.13/20131015213706/ > > Due to the lack of an AM43xx board and any available public > documentation, it's impossible for me to review or test that > platform in any meaningful way. But at least the tests above > verify that the patches don't affect existing platforms - > particularly AM33xx. > > ---------------------------------------------------------------- Pulled into next/soc. Thanks, Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
