From: Kevin Hilman <khilman@linaro.org>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL 2/2] omap changes for am43xx hwmod for v3.13 merge window
Date: Fri, 18 Oct 2013 07:53:22 -0700 [thread overview]
Message-ID: <87d2n2wrz1.fsf@linaro.org> (raw)
In-Reply-To: <526041df.4740e50a.3954.5084SMTPIN_ADDED_MISSING@mx.google.com> (Tony Lindgren's message of "Thu, 17 Oct 2013 13:00:21 -0700")
Tony Lindgren <tony@atomide.com> 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@pwsan.com>:
>
> 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
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] omap changes for am43xx hwmod for v3.13 merge window
Date: Fri, 18 Oct 2013 07:53:22 -0700 [thread overview]
Message-ID: <87d2n2wrz1.fsf@linaro.org> (raw)
In-Reply-To: <526041df.4740e50a.3954.5084SMTPIN_ADDED_MISSING@mx.google.com> (Tony Lindgren's message of "Thu, 17 Oct 2013 13:00:21 -0700")
Tony Lindgren <tony@atomide.com> 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@pwsan.com>:
>
> 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
next parent reply other threads:[~2013-10-18 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <526041df.4740e50a.3954.5084SMTPIN_ADDED_MISSING@mx.google.com>
2013-10-18 14:53 ` Kevin Hilman [this message]
2013-10-18 14:53 ` [GIT PULL 2/2] omap changes for am43xx hwmod for v3.13 merge window Kevin Hilman
2013-10-17 20:00 [GIT PULL 1/2] omap board removal for some omap3 boards " Tony Lindgren
2013-10-17 20:00 ` [GIT PULL 2/2] omap changes for am43xx hwmod " Tony Lindgren
2013-10-17 20:00 ` Tony Lindgren
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=87d2n2wrz1.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.