* [PATCH] pinctrl: mediatek: use builtin_platform_driver
From: Hongzhou Yang @ 2016-11-18 23:53 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <70fcc58b7e9219a9fbe3695df927041b8234dd08.1479457060.git.geliangtang@gmail.com>
On Fri, 2016-11-18 at 22:12 +0800, Geliang Tang wrote:
> Use builtin_platform_driver() helper to simplify the code.
>
> Signed-off-by: Geliang Tang <geliangtang@gmail.com>
> ---
> drivers/pinctrl/mediatek/pinctrl-mt6397.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/drivers/pinctrl/mediatek/pinctrl-mt6397.c b/drivers/pinctrl/mediatek/pinctrl-mt6397.c
> index 6eccb85..afcede7 100644
> --- a/drivers/pinctrl/mediatek/pinctrl-mt6397.c
> +++ b/drivers/pinctrl/mediatek/pinctrl-mt6397.c
> @@ -64,8 +64,4 @@ static struct platform_driver mtk_pinctrl_driver = {
> },
> };
>
> -static int __init mtk_pinctrl_init(void)
> -{
> - return platform_driver_register(&mtk_pinctrl_driver);
> -}
> -device_initcall(mtk_pinctrl_init);
> +builtin_platform_driver(mtk_pinctrl_driver);
Acked-by: Hongzhou Yang <hongzhou.yang@mediatek.com>
Thanks,
Hongzhou
^ permalink raw reply
* [GIT PULL] Reset controller changes for v4.10
From: Olof Johansson @ 2016-11-19 0:18 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1479237815.2456.59.camel@pengutronix.de>
On Tue, Nov 15, 2016 at 08:23:35PM +0100, Philipp Zabel wrote:
> Dear arm-soc maintainers,
>
> Please consider merging this tag which adds OX820 support, removes
> unused modular code and obsolete STiH41[56] support, and adds support
> for multiple devices sharing a pulsed reset, as long as their
> requirement is just being reset once, some time before use.
>
> regards
> Philipp
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.pengutronix.de/git/pza/linux.git tags/reset-for-4.10
>
> for you to fetch changes up to 7da33a37b48f11ffcb4a718f29a3d4552423fea1:
>
> reset: allow using reset_control_reset with shared reset (2016-11-14 09:58:28 +0100)
>
> ----------------------------------------------------------------
> Reset controller changes for v4.10
>
> - remove obsolete STiH41[56] platform support
> - add Oxford Semiconductor OX820 support
> - add reset index include files for OX810SE and OX820
> - make drivers with boolean Kconfig options explicitly
> non-modular
> - allow shared pulsed resets via reset_control_reset, which
> in this case means that the reset must have been triggered
> once, but possibly earlier, after the function returns, and
> is never triggered again for the lifetime of the reset
> control
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] Allwinner DT changes for 4.10
From: Olof Johansson @ 2016-11-19 0:23 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20161115204122.x3vnb3bkny5esdya@lukather>
Hi,
On Tue, Nov 15, 2016 at 09:41:22PM +0100, Maxime Ripard wrote:
> Hi Arnd, Olof,
>
> Here is our pull request for the next merge window.
>
> Thanks!
> Maxime
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git tags/sunxi-dt-for-4.10
>
> for you to fetch changes up to e39a30cf736144814b0bddb3fff28fbbc2a8be0f:
>
> ARM: sunxi: Add the missing clocks to the pinctrl nodes (2016-11-15 18:49:47 +0100)
>
> ----------------------------------------------------------------
> Allwinner DT additions for 4.10
>
> The usual bunch of DT additions, but most notably:
> - A31 DRM driver
> - A31 audio codec
> - WiFi for the A80-Based boards and the CHIP
> - Support for the NextThing Co CHIP Pro (the first board with NAND
> enabled)
> - New boards: NanoPi M1,
>
[...]
> Maxime Ripard (16):
> ARM: sun5i: a13-olinuxino: Enable VGA bridge
> ARM: gr8: Add the UART3
> ARM: gr8: Fix typo in the i2s mclk pin group
> ARM: gr8: Add missing pwm channel 1 pin
> ARM: gr8: Add UART2 pins
> ARM: gr8: Add UART3 pins
> ARM: gr8: Add CHIP Pro support
> ARM: sun5i: chip: Enable Wi-Fi SDIO chip
> ARM: sun5i: Rename A10s pins
> ARM: sun5i: Add SPI2 pins
> ARM: sun5i: Add RGB 565 LCD pins
> ARM: sun5i: chip: Add optional buses
> ARM: gr8: evb: Enable SPDIF
> ARM: gr8: evb: Add i2s codec
> ARM: sun8i: sina33: Enable USB gadget
> ARM: sunxi: Add the missing clocks to the pinctrl nodes
>
[...]
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/ntc-gr8-chip-pro.dts | 266 +++++++++++++++++++++
> arch/arm/boot/dts/ntc-gr8-evb.dts | 33 +++
> arch/arm/boot/dts/ntc-gr8.dtsi | 47 +++-
> arch/arm/boot/dts/sun4i-a10.dtsi | 3 +-
NTC isn't the SoC manufacturer, and we try to keep the prefixes down to
manufacturer to keep the namespace a little more manageable, even if
we never got subdirectories setup as on arm64.
I think this should probably be sun4i-a10-gr8 or sun4i-r8-gr8 as prefix?
-Olof
^ permalink raw reply
* [GIT PULL] Allwinner late DT changes for 4.10
From: Olof Johansson @ 2016-11-19 0:27 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20161115210034.mwqnsggmmbzoav77@lukather>
On Tue, Nov 15, 2016 at 10:00:34PM +0100, Maxime Ripard wrote:
> Hi Arnd, Olof,
>
> Here is a pull request that should be merged after the pinctrl PR,
> hence probably in your late PR.
>
> This is just a mechanic conversion to the generic pinconf bindings and
> removal of the useless pinmux properties we had.
>
> This is based on the previous DT PR I just sent.
>
> Thanks!
> Maxime
>
> The following changes since commit e39a30cf736144814b0bddb3fff28fbbc2a8be0f:
>
> ARM: sunxi: Add the missing clocks to the pinctrl nodes (2016-11-15 18:49:47 +0100)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git tags/sunxi-dt-late-for-4.10
>
> for you to fetch changes up to 1d20ba07ea57ae227a925302b42221df5b830f2b:
>
> ARM: sunxi: Convert pinctrl nodes to generic bindings (2016-11-15 21:56:30 +0100)
Nice cleanup!
Unfortuantely, see comment on previous pull request, so this would need
to be rebased.
Also, this won't work since this branch does not contain the required
pinctrl changes. If we merge this without basing it on those changes we lose
bisectability.
It'd be easiest if you just held off on these until right after 4.10-rc1, and
we could get them in before -rc2.
Thanks,
-Olof
^ permalink raw reply
* [GIT PULL] Allwinner defconfig changes for 4.10
From: Olof Johansson @ 2016-11-19 0:34 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20161115210342.vz6k5ihsfl4gx4nu@lukather>
On Tue, Nov 15, 2016 at 10:03:42PM +0100, Maxime Ripard wrote:
> Hi Arnd, Olof,
>
> Please pull the following changes for the next merge window.
>
> Thanks!
> Maxime
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git tags/sunxi-defconfig-for-4.10
>
> for you to fetch changes up to a0eb3ee3c8dbe918c397eaf52ea0c887defd35a7:
>
> ARM: multi_v7: enable VGA bridge (2016-10-16 14:31:52 +0200)
>
> ----------------------------------------------------------------
> Allwinner defconfig changes for 4.10
>
> Two patches to enable the dumb VGA bridges in the multi_v7 and sunxi
> defconfig.
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] Allwinner arm64 DT changes for 4.9
From: Olof Johansson @ 2016-11-19 0:39 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20161115211333.oqvxfjxxudfkdq7j@lukather>
On Tue, Nov 15, 2016 at 10:13:33PM +0100, Maxime Ripard wrote:
> Hi Arnd, Olof,
>
> Here are our changes for arm64 DT for the next merge window.
>
> Thanks!
> Maxime
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git tags/sunxi-dt64-for-4.10
>
> for you to fetch changes up to 4e3886081848b7ea16452a92c4324acaab644d49:
>
> arm64: dts: add Pine64 support (2016-11-03 09:08:24 +0100)
>
> ----------------------------------------------------------------
> Allwinner arm64 DT changes for 4.10
>
> Support for the Allwinner A64, their first armv8 SoC.
>
> ----------------------------------------------------------------
> Andre Przywara (3):
> arm64: dts: add Allwinner A64 SoC .dtsi
> Documentation: devicetree: add vendor prefix for Pine64
> arm64: dts: add Pine64 support
Hi,
Merged the branch, but please use "arm64: dts: allwinner: <..>" as patch
prefix in the future. Thanks!
-Olof
^ permalink raw reply
* [GIT PULL 1/5] non-urgent omap fixes for v4.10
From: Olof Johansson @ 2016-11-19 0:41 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <582b7c99.5790620a.e95a2.d641SMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Nov 15, 2016 at 01:22:19PM -0800, Tony Lindgren wrote:
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.10/fixes-not-urgent-signed
>
> for you to fetch changes up to 5c02b01d234f8410010c952069d3fb9ec5d9124a:
>
> ARM: OMAP2+: pm-debug: Use seq_putc() in two functions (2016-11-09 15:33:33 -0700)
>
> ----------------------------------------------------------------
> Non-urgent fixes for omaps for v4.10 merge window:
>
> - Fix mismatched interrupt numbers for tps65217, these are not yet
> used
>
> - Remove unused omapdss_early_init_of()
>
> - Use seq_putc() for pm-debug.c
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL 2/5] omap soc changes for v4.10
From: Olof Johansson @ 2016-11-19 0:43 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <582b7c9a.d549620a.d6a1a.22c0SMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Nov 15, 2016 at 01:22:20PM -0800, Tony Lindgren wrote:
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.10/soc-signed
>
> for you to fetch changes up to 2bb6375f5c03cc5bf510402b646c1a23046b3f12:
>
> Merge branch 'omap-for-v4.10/cpuidle-v2' into omap-for-v4.10/soc (2016-11-14 15:58:18 -0800)
>
> ----------------------------------------------------------------
> SoC changes for omaps for v4.10 merge window:
>
> - Add hwmod interconnect target wrapper module data for crypto
> accelerators for am3xxx, am43xx and dra7
>
> - Add support for dra71x family of SoCs
>
> - PM fixes for omap4/5 needed for omap5 cpuidle
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL 3/5] omap device tree changes for v4.10
From: Olof Johansson @ 2016-11-19 0:48 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <582b7c9b.0111620a.395b.cabdSMTPIN_ADDED_BROKEN@mx.google.com>
Hi,
On Tue, Nov 15, 2016 at 01:22:21PM -0800, Tony Lindgren wrote:
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.10/dt-signed
>
> for you to fetch changes up to 7e2f8c0ae670327cbe0348ad2f3df7d9a55a8e5d:
>
> ARM: dts: Add minimal support for motorola droid 4 xt894 (2016-11-15 10:28:49 -0800)
>
> ----------------------------------------------------------------
> Device tree changes for omaps for v4.10 merge window:
>
> - A series of patches to configure tps65217 PMIC interrupts for
> power button, charger and usb and use them on am335x
>
> - Configure EEPROM, LEDs and USR1 button for omap5 boards
>
> - Add tscadc DMA properites for am33xx and am4372
>
> - Configure baltos-ir5221 both musb channels to host mode
>
> - Configure internal and external RTC clocks for am335x boards
>
> - Don't reset gpio3 block on baltos
>
> - Remove pinmux for dra72-evm for erratum i869, fix the regulators
> and seprate out tps65917 support
>
> - Add dra718-evm support
>
> - Add minimal droid 4 xt894 support
Another phone, cool to see even though it's no longer being sold.
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL 4/5] drop unused omap platform_data for v4.10
From: Olof Johansson @ 2016-11-19 0:50 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <582b7c9c.5790620a.e95a2.d669SMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Nov 15, 2016 at 01:22:22PM -0800, Tony Lindgren wrote:
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.10/legacy-signed
>
> for you to fetch changes up to 19944b3a4a30163656b26e9d2ca659657113ac3e:
>
> ARM: OMAP2+: Drop legacy sdram timings (2016-11-10 16:07:32 -0700)
>
> ----------------------------------------------------------------
> Legacy platform_data removal for omaps for v4.10 merge window.
> We've dropped the last legacy boot board-*.c files for mach-omap2
> for v4.9 so now we can start removing the unused platform_data.
>
> All of the below has been unused since v4.9 merge window:
>
> - Drop legacy pmic init code
>
> - Apply seq_puts() fixes for legacy mux code, then drop it
>
> - Drop legacy serial init
>
> - Drop legacy i2c init
>
> - Drop legacy PM init
>
> - Drop legacy twl4030 platform init
>
> - Drop legacy USB host init
>
> - Drop legacy muxing for tusb6010, n8x0 is still using it's
> platform init via pdata-quirks.c
>
> - Drop legacy musb init
>
> - Drop hwmod related legacy mux code
>
> - Drop legacy hwmod data for omap3
>
> - Drop legacy smsc911x and smc91x init
>
> - Drop legacy board flash init
>
> - Drop legacy ads7846 init
>
> - Drop legacy sdram timings
[...]
> 45 files changed, 160 insertions(+), 8306 deletions(-)
Nice!!
Merged into next/soc, since we don't really track a cleanup branch any more.
-Olof
^ permalink raw reply
* [GIT PULL 5/5] omap defconfig changes for v4.10
From: Olof Johansson @ 2016-11-19 0:50 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <582b7c9d.473f630a.d4410.a225SMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Nov 15, 2016 at 01:22:23PM -0800, Tony Lindgren wrote:
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.10/defconfig-signed
>
> for you to fetch changes up to 9c106e4efab2ec96daebb7bdd0bb61602fd52e7a:
>
> ARM: omap2plus_defconfig: Run make savedefconfig to save some space (2016-11-15 11:01:24 -0800)
>
> ----------------------------------------------------------------
> Defconfig changes for omaps for v4.10 merge window:
>
> - Enable tsc2004 touchscreen as a loadable module
>
> - Enable REGULATOR_GPIO, dra71-evm needs this for MMC voltage
>
> - Enable LP873x PMICs for dra71x-evm
>
> - Run make savedefconfig to save some space and make it
> easier to generate minimal patches against it
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] Amlogic 64-bit DT changes for v4.10
From: Olof Johansson @ 2016-11-19 0:52 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <7hpolw2uih.fsf@baylibre.com>
On Tue, Nov 15, 2016 at 03:28:06PM -0800, Kevin Hilman wrote:
> Arnd, Olof,
>
> Here are the arm64 DT changes for Amlogic family SoCs.
>
> Please pull,
>
> Thanks,
>
> Kevin
>
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git tags/amlogic-dt64
>
> for you to fetch changes up to ab5b24fdd2d551ea729e8e19e47811a646260331:
>
> ARM64: dts: meson-gxbb-vega-s95: Add SD/SDIO/MMC and PWM nodes (2016-11-15 12:05:54 -0800)
>
> ----------------------------------------------------------------
> Amlogic DT changes for 64-bit platforms for v4.10
>
> Support for new drivers:
> - USB
> - i2c
> - SPI
> - mailbox/MHU
> - PWM
> - ethernet MAC, PHY
> - secure monitor
> - IR
> - watchdog
Merged, thanks. This platform is coming along nicely.
-Olof
^ permalink raw reply
* [GIT PULL] Amlogic defconfig changes for v4.10
From: Olof Johansson @ 2016-11-19 1:03 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <7hk2c42ugq.fsf@baylibre.com>
On Tue, Nov 15, 2016 at 03:29:09PM -0800, Kevin Hilman wrote:
> Arnd, Olof,
>
> Here are some defconfig change for Amlogic family SoCs for 4.10. Please
> pull.
>
> Thanks,
>
> Kevin
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git tags/amlogic-defconfig
>
> for you to fetch changes up to 88c9cb7c109e8867fd6ac3a11e5cead37a6a6f1d:
>
> ARM64: configs: Activate Internal PHY for Meson GXL (2016-11-14 08:40:47 -0800)
>
> ----------------------------------------------------------------
> Amlogic defconfig updates for v4.10
> - enable I2C driver
> - enable SPI, watchdog and HW random as modules
Merged, thanks.
-Olof
^ permalink raw reply
* [PATCH] ARM: qcom_defconfig: Enable RPM/RPM-SMD clocks
From: Olof Johansson @ 2016-11-19 1:17 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20161117152026.10491-1-georgi.djakov@linaro.org>
On Thu, Nov 17, 2016 at 05:20:26PM +0200, Georgi Djakov wrote:
> Enable support for clocks, controlled by the RPM processor on
> Qualcomm platforms.
>
> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
Hi,
Please send patches like these to the platform maintainer (i.e. Andy
Gross), and leave arm at kernel.org off of Cc.
We prefer that only maintainers email us at this address to avoid getting
cc:d on everything (and dealing with the volume of email that entails).
Thanks!
-Olof
^ permalink raw reply
* specifying order of /dev/mmcblk devices via device-tree?
From: Stefan Agner @ 2016-11-19 1:18 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20161115235503.GC1041@n2100.armlinux.org.uk>
On 2016-11-15 15:55, Russell King - ARM Linux wrote:
> On Tue, Nov 15, 2016 at 10:10:02PM +0000, Russell King - ARM Linux wrote:
>> On Tue, Nov 15, 2016 at 01:39:42PM -0800, Tim Harvey wrote:
>> > On Tue, Nov 15, 2016 at 1:35 PM, Russell King - ARM Linux
>> > <linux@armlinux.org.uk> wrote:
>> > > On Tue, Nov 15, 2016 at 12:27:53PM -0800, Tim Harvey wrote:
>> > >> On Mon, Nov 14, 2016 at 11:08 AM, Russell King - ARM Linux
>> > >> <linux@armlinux.org.uk> wrote:
>> > >> > So, someone merged a patch which makes mmcblk devices follow the
>> > >> > host controller numbering.
>> > >> >
>> > >> > Now my cubox-i fails to boot correctly because the SD card in the
>> > >> > _only_ SD card slot now gets called "mmcblk1" and not "mmcblk0".
>> > >> >
>> > >> > USDHC1 is wired to the on-microsom WiFi, and never has anything
>> > >> > remotely near a SD card or eMMC present. So, this change is
>> > >> > confusing on these platforms.
>> > >> >
>> > >> > Moreover, this is _going_ to break SolidRun distros if people upgrade
>> > >> > their kernels.
>> > >> >
>> > >> > It may be appropriate for eMMC, but it's not appropriate everywhere.
>> > >> >
>> > >> > This is a user visible _regression_ in 4.9-rc. Whoever did this,
>> > >> > please revert whatever change caused this, and next time limit it
>> > >> > to only eMMC.
>> > >> >
>> > >> > Thanks.
>> > >>
>> > >> I see the same thing on newer kernels, which is why I asked the
>> > >> question. I didn't expect (or even want honestly) a non mmcblk0 boot
>> > >> device and was looking for a way to control that via dt. Now I'm
>> > >> understanding that to avoid this kind of bootloader/kernel dependence
>> > >> issue I should be using UUID's to identify the boot device.
>> > >>
>> > >> >From my testing it looks like the change your looking for occurred
>> > >> some time ago and is somewhere between 4.5 and 4.6 and not a 4.9
>> > >> regression specifically.
>> > >
>> > > That depends how you look at it. Yes, there's a change in 4.5 to 4.6
>> > > which ties the block device number to the host device index, but that's
>> > > really only part of the story here.
>> > >
>> > > 4.8 definitely identifies the SD card in iMX6 usdhc2 as "mmcblk0".
>> > > 4.9-rc identifies the SD card as "mmcblk1". This makes it a 4.9 change
>> > > of behaviour - there can be no argument about that.
>> > >
>> > > Now, digging further into this today, it appears that:
>> > >
>> > > v4.8: usdhc2 was probed first, and is given mmc0.
>> > > usdhc1 is probed second, and is given mmc1.
>> > >
>> > > v4.9-rc: usdhc1 is probed first, and is given mmc0.
>> > > usdhc2 is probed second, and is given mmc1.
>> > >
>> > > I haven't yet been able to figure out why there's been this change
>> > > of probe order. There's no change that I can see in the iMX6 DT
>> > > files that would account for this.
>> > >
>> >
>> > I bisected it and the commit your looking for is
>> > 9aaf3437aa72ed5370bf32c99580a3fa2c330e3d
>>
>> No it's not.
>>
>> Let me try and put it plainer:
>>
>> * Commit 9aaf3437aa72ed5370bf32c99580a3fa2c330e3d ties the mmc block
>> device number (mmcblkN) to the mmc host interface number (mmcN).
>> This change happened between 4.5 and 4.6.
>>
>> * The change I'm seeing happened between 4.8 and 4.9-rc. I'm not
>> seeing a change of behaviour between 4.5 and 4.6.
>>
>> * The change I'm seeing changes the order of the physical device
>> associated with the hosts named mmc0 and mmc1 in the kernel.
>>
>> * Because physical devices associated with the mmc0 and mmc1 hosts
>> swap over, the mmcblkN number changes due to the commit you point
>> out.
>>
>> * So, the change that I'm seeing between 4.8 and 4.9-rc is not caused
>> by commit 9aaf3437aa72ed5370bf32c99580a3fa2c330e3d, but by something
>> else changing the order in which the two usdhc physical hardware
>> blocks get probed.
>>
>> Does this make it clearer?
>
> It turns out to be this commit:
>
> commit 6eb1c9496b81680f2cd2e0eda06c531317e2e28d
> Author: Masahiro Yamada <yamada.masahiro@socionext.com>
> Date: Mon Sep 19 01:16:44 2016 +0900
>
> clk: probe common clock drivers earlier
>
> Several SoCs implement platform drivers for clocks rather than
> CLK_OF_DECLARE(). Clocks should come earlier because they are
> prerequisites for many of other drivers. It will help to mitigate
> EPROBE_DEFER issues.
>
> Also, drop the comment since it does not carry much value.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> Acked-by: Michael Turquette <mturquette@baylibre.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> which changes the init order. In 4.8, we get:
Afaik, init order is not guaranteed, it never was. Usually the order
ends up to be in some order of the device tree, but one could also parse
the device tree in reverse order (which would be an interesting
experiment).
If we want to rely on ordering, we need to add alias support.
--
Stefan
^ permalink raw reply
* specifying order of /dev/mmcblk devices via device-tree?
From: Stefan Agner @ 2016-11-19 1:23 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CAPDyKFrpqmvVAKsfQBP1m7vdOjPRx7puVkmmCe3yxe1gVFwgzw@mail.gmail.com>
On 2016-11-16 06:45, Ulf Hansson wrote:
> On 28 October 2016 at 17:37, Mark Rutland <mark.rutland@arm.com> wrote:
>> On Fri, Oct 28, 2016 at 08:23:04AM -0700, Tim Harvey wrote:
>>> Greetings,
>>>
>>> I have an IMX6 board that has the following:
>>> sdhc1: mmc0: sdio radio
>>> sdhc2: mmc1: /dev/mmcblk1: microSD connector
>>> sdhc3: mmc2: /dev/mmcblk2: on-board eMMC
>>>
>>> I would like to have sdhc3 registered as /dev/mmcblk0 and sdhc2
>>> registered as /dev/mmcblk1 so that permanent storage is the first
>>> mmcblk device as I think this is more intuitive however currently
>>> these get instanced in the order they appear in the imx6qdl.dtsi
>>> device-tree configuration and are not able to be mapped the way I want
>>> them in my dts file.
>>>
>>> Is there a way, or if not is there a desire for a way, to specify the
>>> order of /dev/mmcblk devices via device-tree?
>>
>> As with many other devices, there is no standard way of controlling the
>> Linux enumeration (and given the ID space is shared with other dynamic
>> devices it's not something that could generally work).
>>
>> These should be refererd to by UUID if possible.
>>
>> If not, we could cosider adding a by-dt-path or something like that.
>
> So does that mean you think using "DT aliases" would be okay? As
> Javier pointed out, there have been some attempts [1] for that, but
> they didn't make it.
> Perhaps we need to re-consider, and if so please re-review the DT
> bindings patch from that series.
I really would like to see some sort of stable MMC block device
ordering.
by-dt-path solutions requires initramfs, which adds complexity and boot
time. Both not very welcome in simple embedded devices.
PARTUUID is relying on a particular instance of a partition, which is
not the same as to say boot from the second partition of device X.
The main problem I see in my patchset is that it works around the fact
MMC is a bus. Adding the mmc controller number to the block device name
would avoid that issue (mmc0blk0...), not sure if a such a drastic
change would be acceptable.
--
Stefan
^ permalink raw reply
* [GIT PULL 3/5] omap device tree changes for v4.10
From: Tony Lindgren @ 2016-11-19 1:23 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20161119004830.GF15902@localhost>
* Olof Johansson <olof@lixom.net> [161118 17:10]:
> On Tue, Nov 15, 2016 at 01:22:21PM -0800, Tony Lindgren wrote:
> > - Add minimal droid 4 xt894 support
>
> Another phone, cool to see even though it's no longer being sold.
Plenty of them around at about $30 or so used :)
Regards,
Tony
^ permalink raw reply
* [GIT PULL] Second Round of Renesas ARM Based SoC Updates for v4.10
From: Olof Johansson @ 2016-11-19 1:28 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1479387356.git.horms+renesas@verge.net.au>
On Thu, Nov 17, 2016 at 02:34:25PM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these second round of Renesas ARM based SoC updates for v4.10.
>
> This pull request is based on the previous round of
> such requests, tagged as renesas-soc-for-v4.10,
> which I have already sent a pull-request for.
>
>
> The following changes since commit 9652623f8f019edc93a7a934a10b7d0b90421d5a:
>
> ARM: shmobile: r8a7779/marzen: Add board part number to DT bindings (2016-11-04 10:25:45 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-soc2-for-v4.10
>
> for you to fetch changes up to 4af239175d00c1866cc6b41f3eabcf93c45dcc40:
>
> ARM: shmobile: document SK-RZG1E board (2016-11-15 10:59:35 +0100)
>
> ----------------------------------------------------------------
> Second Round of Renesas ARM Based SoC Updates for v4.10
>
> * Basic support for r8a7745 SoC
>
> ----------------------------------------------------------------
> Sergei Shtylyov (2):
> ARM: shmobile: r8a7745: basic SoC support
> ARM: shmobile: document SK-RZG1E board
Hi,
Is there a reason you're adding a config option per SoC?
I think you'd be better off not adding these config options, and just adding
support for the SoCs through compatibles (and adding the drivers to defconfigs,
etc).
Anyway, I've merged this branch since this is along the lines of what you
already have, but it could be worth looking at cleaning up and removing
some of these options.
-Olof
^ permalink raw reply
* [GIT PULL] Second Round of Renesas ARM Based SoC Drivers Updates for v4.10
From: Olof Johansson @ 2016-11-19 1:35 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1479389981.git.horms+renesas@verge.net.au>
On Thu, Nov 17, 2016 at 03:04:35PM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these second round of Renesas ARM based SoC drivers updates for v4.10.
>
> This pull request is based on a merge of:
>
> * The previous round of such requests, tagged as renesas-drivers-for-v4.10,
> which you have already pulled.
> * The soc-device-match-tag1 tag of Geert Uytterhoeven's renesas-driver's tree.
> This is included to provide core soc_device_match() infrastructure which
> is a dependency of identifying SoC and registering with SoC bus.
>
>
> The following changes since commit 437c4eeb0bd4c1d68817be997716f52b8c22a9c3:
>
> Merge tag 'soc-device-match-tag1' of https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers into HEAD (2016-11-15 14:12:57 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-drivers2-for-v4.10
>
> for you to fetch changes up to 63ee9e2ba47dbdb42156c9b940515cfd49e78c91:
>
> soc: renesas: Identify SoC and register with the SoC bus (2016-11-17 14:37:20 +0100)
>
> ----------------------------------------------------------------
> Second Round of Renesas ARM Based SoC Drivers Updates for v4.10
>
> * Identify SoC and register with the SoC bus
> * Add support for the r8a7745 SoC to rcar-sysc
>
> ----------------------------------------------------------------
> Geert Uytterhoeven (2):
> ARM: shmobile: Document DT bindings for Product Register
> soc: renesas: Identify SoC and register with the SoC bus
>
> Sergei Shtylyov (2):
> ARM: shmobile: r8a7745: add power domain index macros
> soc: renesas: rcar-sysc: add R8A7745 support
>
So, this pull request contains 8 patches, not 4. Seems like your pull
request doesn't show any of the code from Geert's branch, didn't mention
it in the tag and only in the email text above. Furthermore, Geert's
branch modifies driver core code, so it's extra important to make sure
it's clear that it's an unusual pull request.
Given that this modifies driver core, please either merge that code
through Greg first, or get an ack from him. If you merge through him,
make sure it's on a standalone topic branch that we can share.
-Olof
^ permalink raw reply
* [GIT PULL] Second Round of Renesas ARM64 Based SoC DT Updates for v4.10
From: Olof Johansson @ 2016-11-19 1:41 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1479388193.git.horms+renesas@verge.net.au>
On Thu, Nov 17, 2016 at 03:04:55PM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these second round of Renesas ARM64 based SoC DT updates
> for v4.10.
>
> This pull request is based on a merge of:
>
> * The previous round of such requests, tagged as renesas-arm64-dt-for-v4.10,
> which I have already sent a pull-request for.
> * The "Second Round of Renesas ARM Based SoC Drivers Updates for v4.10",
> tagged as renesas-drivers2-for-v4.10, which I have also sent a pull
> request for. This is included to provide dependencies for adding device
> nodes for PRR.
Please avoid entangling these pull requests, since now I can't merge DT since
I'm rejecting your drivers pull request.
I also don't understand why you need a driver branch as base. The PRR
nodes are literally just a compatible field and a reg entry. It should
depend on nothing.
So, I'm a little confused here. Please disentangle this and send a separate
pull request, I'll be happy to merge that.
-Olof
^ permalink raw reply
* [GIT PULL] Renesas ARM Based SoC EtherAVB Updates for v4.10
From: Olof Johansson @ 2016-11-19 1:43 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1479390880.git.horms+renesas@verge.net.au>
On Thu, Nov 17, 2016 at 03:05:08PM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC EtherAVB updates for v4.10.
>
> This pull request is based on the "Second Round of Renesas ARM64 Based SoC
> DT Updates for v4.10", tagged as arm64-dt-for-v4.10, which I have also sent
> a pull-request for.
>
> The reason for this base is to provide dependencies. For the same reason
> an ack has been provided by David Miller to facilitate a merge of the patch
> via the Renesas tree.
And now we have cascading dependencies. Can't merge this either.
Why is the DT branch and this driver branch entangled?! Again, there is
absolutely no functional dependency between them.
-Olof
^ permalink raw reply
* [GIT PULL] Second Round of Renesas ARM Based SoC DT Updates for v4.10
From: Olof Johansson @ 2016-11-19 1:49 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1479391750.git.horms+renesas@verge.net.au>
On Thu, Nov 17, 2016 at 03:11:45PM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these second round of Renesas ARM based SoC DT updates for v4.10.
>
> This pull request is based on a merge of:
>
> * The previous round of such requests, tagged as renesas-dt-for-v4.10,
> which I have already sent a pull-request for.
> * The rzg-clock-defs tag of Geert Uytterhoeven's renesas-driver's tree.
> This is to provide dependencies for adding the r8a7743 and r8a7745 SoCs.
> * The "Second Round of Renesas ARM Based SoC Drivers Updates for v4.10",
> tagged as renesas-drivers2-for-v4.10, which I have also sent a pull
> request for. This is included to provide dependencies for adding device
> nodes for PRR, and adding the r8a7743 and r8a7745 SoCs..
Again, nack. And again, I don't understand why you create dependencies that
aren't needed. Please fix.
-Olof
^ permalink raw reply
* [GIT PULL] ARM: mvebu: drivers for v4.10 (#1)
From: Olof Johansson @ 2016-11-19 1:51 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <87r369bwvn.fsf@free-electrons.com>
Hi,
On Thu, Nov 17, 2016 at 10:49:00PM +0100, Gregory CLEMENT wrote:
> Hi,
>
> Here is the first pull request for drivers for mvebu for v4.10.
>
> Gregory
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.infradead.org/linux-mvebu.git tags/mvebu-drivers-4.10-1
>
> for you to fetch changes up to d6ea689345ecc27b636a8bb62bf07080f21f110c:
>
> ARM/orion/gpio: Replace three seq_printf() calls by seq_puts() in orion_gpio_dbg_show() (2016-10-17 17:40:24 +0200)
>
> ----------------------------------------------------------------
> mvebu drivers for 4.10 (part 1)
>
> Clean-up on thegpio driver for old SoCs(non DT)
>
> ----------------------------------------------------------------
> Markus Elfring (1):
> ARM/orion/gpio: Replace three seq_printf() calls by seq_puts() in orion_gpio_dbg_show()
This is next/soc material, not driver. Merged there. Thanks.
(Also, please be mindful of patch prefixes. This is again a nonstandard
one).
-Olof
^ permalink raw reply
* [PATCH] arm64: dts: qcom: msm8996: Fixup smp2p node
From: Sarangdhar Joshi @ 2016-11-19 1:53 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1479499609-13336-1-git-send-email-bjorn.andersson@linaro.org>
On 11/18/2016 12:06 PM, Bjorn Andersson wrote:
> The SMEM state property name changes between the integration branch and
> mainline, update to use the correct one.
>
> Fixes: 2f45d9fcd531 ("arm64: dts: msm8996: Add SMP2P and APCS nodes")
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Thanks for the change and sorry for missing it earlier.
Reviewed-by: Sarangdhar Joshi <spjoshi@codeaurora.org>
^ permalink raw reply
* [GIT PULL] ARM: mvebu: dt for v4.10 (#1)
From: Olof Johansson @ 2016-11-19 1:58 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <87poltbwt2.fsf@free-electrons.com>
Hi,
On Thu, Nov 17, 2016 at 10:50:33PM +0100, Gregory CLEMENT wrote:
> Hi,
>
> Here is the first pull request for dt for mvebu for v4.10.
>
> I hope being able to send a second part very soon with the series
> removing all the DT warning.
>
> Gregory
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://git.infradead.org/linux-mvebu.git tags/mvebu-dt-4.10-1
>
> for you to fetch changes up to cf20c489de6fcef88405d4febef7a078d2053b9e:
>
> ARM: dt: orion5x: convert ls-chl to FDT (2016-11-07 17:23:34 +0100)
>
> ----------------------------------------------------------------
> mvebu fixes for 4.10 (part 1)
>
> Most of the commit are pinmux and i2c fix for netgear NASes
> Fix on a wrong comment about PLL frequency
> Bigger commit: conversion of on otion5x based board to the device tree
>
> ----------------------------------------------------------------
> Ashley Hughes (1):
> ARM: dt: orion5x: convert ls-chl to FDT
This is a great conversion, but I'd like to see the code handled a
little differently.
First of all, there's no longer a need to have a config option for
MACH_LINKSTATION_LSCHL, as long as ARCH_ORION5X_DT is enabled you'll
be fine. So you can remove that Kconfig entry alltogether.
Also, there's no need to make the DT addition and the legacy platform
removal in one commit. It's common that we build up the DT support to the point
that it's at parity, and then remove the legacy board. That way we also don't
entangle DT commits with non-DT commits, which can sometimes be a bit of a pain
(in particular for those who maintain a copy of the DT subdir in another git
repo).
So, mind respinning with this fixed? Thanks!
-Olof
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox