All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Simon Horman <horms@verge.net.au>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Wolfram Sang <wsa@the-dreams.de>,
	Richard Weinberger <richard@nod.at>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Boris Brezillon <boris.brezillon@bootlin.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Marek Vasut <marek.vasut+renesas@gmail.com>
Subject: Re: [PATCH 6/9] ARM: dts: wheat: Drop MTD partitioning from DT
Date: Wed, 30 May 2018 12:13:31 +0200	[thread overview]
Message-ID: <d78bb8a8-a351-409c-54d2-33ee02fd8afe@gmail.com> (raw)
In-Reply-To: <20180528093602.eb36j34bbfzmpmw2@verge.net.au>

On 05/28/2018 11:36 AM, Simon Horman wrote:
> On Mon, May 28, 2018 at 10:54:57AM +0200, Geert Uytterhoeven wrote:
>> Hi Simon,
>>
>> On Mon, May 28, 2018 at 10:41 AM, Simon Horman <horms@verge.net.au> wrote:
>>> On Thu, May 24, 2018 at 04:52:59PM +0200, Marek Vasut wrote:
>>>> On 05/23/2018 08:25 AM, Geert Uytterhoeven wrote:
>>>>> On Wed, May 23, 2018 at 12:01 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
>>>>>> On 05/22/2018 04:43 PM, Geert Uytterhoeven wrote:
>>>>>>> On Tue, May 22, 2018 at 2:02 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
>>>>>>>> Drop the MTD partitioning from DT, since it does not describe HW
>>>>>>>> and to give way to a more flexible kernel command line partition
>>>>>>>> passing.
>>>>>>>>
>>>>>>>> To retain the original partitioning, assure you have enabled
>>>>>>>> CONFIG_MTD_CMDLINE_PARTS in your kernel config and add the
>>>>>>>> following to your kernel command line:
>>>>>>>>
>>>>>>>>   mtdparts=spi0.0:256k@0(loader),4096k(user),-(flash)
>>>>>>>
>>>>>>> I think the "@0" can be dropped, as it's optional?
>>>>>>> 4m?
>>>>>>
>>>>>> My take on this is that the loader is actually at offset 0x0 of the MTD
>>>>>> device and we explicitly state that in the mtdparts to anchor the first
>>>>>> partition within the MTD device and all the other partitions are at
>>>>>> offset +(sum of the sizes of all partitions listed before the current
>>>>>> one) relative to that first partition.
>>>>>
>>>>> Where is this explicitly states for the first partition?
>>>>>
>>>>>> Removing the @0 feels fragile at best and it seems to depend on the
>>>>>> current behavior of the code.
>>>>>
>>>>> Better, it also depends on the documented behavior:
>>>>>
>>>>> Documentation/admin-guide/kernel-parameters.txt refers to
>>>>> drivers/mtd/cmdlinepart.c, which states:
>>>>>
>>>>>  * <offset>  := standard linux memsize
>>>>>  *              if omitted the part will immediately follow the previous part
>>>>>  *              or 0 if the first part
>>>>>
>>>>> None of the examples listed there or under the MTD_CMDLINE_PARTS Kconfig
>>>>> help text, or in a defconfig bundled with the kernel, use @0 for the first
>>>>> partition.
>>>>
>>>> I think this is exceptionally fragile and dangerous to depend on this,
>>>> but so be it.
>>>
>>> Could you respin with this change?
>>>
>>> I would also like to ask for another change, in light of recent
>>> feedback from Olof Johansson ("Re: [GIT PULL] Renesas ARM64 Based SoC DT
>>> Updates for v4.18").
>>>
>>> Please consolidate the dts patches into a single patch?
>>
>> I think it's better to keep them split, as each commit description mentions
>> what needs to be passed on the kernel command line for the corresponding
>> board.
>>
>> Combining it in a single patch makes it much harder to extract this information.
>> Unless you're fine with a list:
>>
>>    koelsch: ...
>>    wheat: mtdparts=spi0.0:256k@0(loader),4096k(user),-(flash)
> 
> Lets try a list.

Reposted with a list, twice :/

-- 
Best regards,
Marek Vasut

WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marek.vasut@gmail.com>
To: Simon Horman <horms@verge.net.au>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	Marek Vasut <marek.vasut+renesas@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Wolfram Sang <wsa@the-dreams.de>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Richard Weinberger <richard@nod.at>,
	Boris Brezillon <boris.brezillon@bootlin.com>
Subject: Re: [PATCH 6/9] ARM: dts: wheat: Drop MTD partitioning from DT
Date: Wed, 30 May 2018 12:13:31 +0200	[thread overview]
Message-ID: <d78bb8a8-a351-409c-54d2-33ee02fd8afe@gmail.com> (raw)
In-Reply-To: <20180528093602.eb36j34bbfzmpmw2@verge.net.au>

On 05/28/2018 11:36 AM, Simon Horman wrote:
> On Mon, May 28, 2018 at 10:54:57AM +0200, Geert Uytterhoeven wrote:
>> Hi Simon,
>>
>> On Mon, May 28, 2018 at 10:41 AM, Simon Horman <horms@verge.net.au> wrote:
>>> On Thu, May 24, 2018 at 04:52:59PM +0200, Marek Vasut wrote:
>>>> On 05/23/2018 08:25 AM, Geert Uytterhoeven wrote:
>>>>> On Wed, May 23, 2018 at 12:01 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
>>>>>> On 05/22/2018 04:43 PM, Geert Uytterhoeven wrote:
>>>>>>> On Tue, May 22, 2018 at 2:02 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
>>>>>>>> Drop the MTD partitioning from DT, since it does not describe HW
>>>>>>>> and to give way to a more flexible kernel command line partition
>>>>>>>> passing.
>>>>>>>>
>>>>>>>> To retain the original partitioning, assure you have enabled
>>>>>>>> CONFIG_MTD_CMDLINE_PARTS in your kernel config and add the
>>>>>>>> following to your kernel command line:
>>>>>>>>
>>>>>>>>   mtdparts=spi0.0:256k@0(loader),4096k(user),-(flash)
>>>>>>>
>>>>>>> I think the "@0" can be dropped, as it's optional?
>>>>>>> 4m?
>>>>>>
>>>>>> My take on this is that the loader is actually at offset 0x0 of the MTD
>>>>>> device and we explicitly state that in the mtdparts to anchor the first
>>>>>> partition within the MTD device and all the other partitions are at
>>>>>> offset +(sum of the sizes of all partitions listed before the current
>>>>>> one) relative to that first partition.
>>>>>
>>>>> Where is this explicitly states for the first partition?
>>>>>
>>>>>> Removing the @0 feels fragile at best and it seems to depend on the
>>>>>> current behavior of the code.
>>>>>
>>>>> Better, it also depends on the documented behavior:
>>>>>
>>>>> Documentation/admin-guide/kernel-parameters.txt refers to
>>>>> drivers/mtd/cmdlinepart.c, which states:
>>>>>
>>>>>  * <offset>  := standard linux memsize
>>>>>  *              if omitted the part will immediately follow the previous part
>>>>>  *              or 0 if the first part
>>>>>
>>>>> None of the examples listed there or under the MTD_CMDLINE_PARTS Kconfig
>>>>> help text, or in a defconfig bundled with the kernel, use @0 for the first
>>>>> partition.
>>>>
>>>> I think this is exceptionally fragile and dangerous to depend on this,
>>>> but so be it.
>>>
>>> Could you respin with this change?
>>>
>>> I would also like to ask for another change, in light of recent
>>> feedback from Olof Johansson ("Re: [GIT PULL] Renesas ARM64 Based SoC DT
>>> Updates for v4.18").
>>>
>>> Please consolidate the dts patches into a single patch?
>>
>> I think it's better to keep them split, as each commit description mentions
>> what needs to be passed on the kernel command line for the corresponding
>> board.
>>
>> Combining it in a single patch makes it much harder to extract this information.
>> Unless you're fine with a list:
>>
>>    koelsch: ...
>>    wheat: mtdparts=spi0.0:256k@0(loader),4096k(user),-(flash)
> 
> Lets try a list.

Reposted with a list, twice :/

-- 
Best regards,
Marek Vasut

WARNING: multiple messages have this Message-ID (diff)
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/9] ARM: dts: wheat: Drop MTD partitioning from DT
Date: Wed, 30 May 2018 12:13:31 +0200	[thread overview]
Message-ID: <d78bb8a8-a351-409c-54d2-33ee02fd8afe@gmail.com> (raw)
In-Reply-To: <20180528093602.eb36j34bbfzmpmw2@verge.net.au>

On 05/28/2018 11:36 AM, Simon Horman wrote:
> On Mon, May 28, 2018 at 10:54:57AM +0200, Geert Uytterhoeven wrote:
>> Hi Simon,
>>
>> On Mon, May 28, 2018 at 10:41 AM, Simon Horman <horms@verge.net.au> wrote:
>>> On Thu, May 24, 2018 at 04:52:59PM +0200, Marek Vasut wrote:
>>>> On 05/23/2018 08:25 AM, Geert Uytterhoeven wrote:
>>>>> On Wed, May 23, 2018 at 12:01 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
>>>>>> On 05/22/2018 04:43 PM, Geert Uytterhoeven wrote:
>>>>>>> On Tue, May 22, 2018 at 2:02 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
>>>>>>>> Drop the MTD partitioning from DT, since it does not describe HW
>>>>>>>> and to give way to a more flexible kernel command line partition
>>>>>>>> passing.
>>>>>>>>
>>>>>>>> To retain the original partitioning, assure you have enabled
>>>>>>>> CONFIG_MTD_CMDLINE_PARTS in your kernel config and add the
>>>>>>>> following to your kernel command line:
>>>>>>>>
>>>>>>>>   mtdparts=spi0.0:256k at 0(loader),4096k(user),-(flash)
>>>>>>>
>>>>>>> I think the "@0" can be dropped, as it's optional?
>>>>>>> 4m?
>>>>>>
>>>>>> My take on this is that the loader is actually at offset 0x0 of the MTD
>>>>>> device and we explicitly state that in the mtdparts to anchor the first
>>>>>> partition within the MTD device and all the other partitions are at
>>>>>> offset +(sum of the sizes of all partitions listed before the current
>>>>>> one) relative to that first partition.
>>>>>
>>>>> Where is this explicitly states for the first partition?
>>>>>
>>>>>> Removing the @0 feels fragile at best and it seems to depend on the
>>>>>> current behavior of the code.
>>>>>
>>>>> Better, it also depends on the documented behavior:
>>>>>
>>>>> Documentation/admin-guide/kernel-parameters.txt refers to
>>>>> drivers/mtd/cmdlinepart.c, which states:
>>>>>
>>>>>  * <offset>  := standard linux memsize
>>>>>  *              if omitted the part will immediately follow the previous part
>>>>>  *              or 0 if the first part
>>>>>
>>>>> None of the examples listed there or under the MTD_CMDLINE_PARTS Kconfig
>>>>> help text, or in a defconfig bundled with the kernel, use @0 for the first
>>>>> partition.
>>>>
>>>> I think this is exceptionally fragile and dangerous to depend on this,
>>>> but so be it.
>>>
>>> Could you respin with this change?
>>>
>>> I would also like to ask for another change, in light of recent
>>> feedback from Olof Johansson ("Re: [GIT PULL] Renesas ARM64 Based SoC DT
>>> Updates for v4.18").
>>>
>>> Please consolidate the dts patches into a single patch?
>>
>> I think it's better to keep them split, as each commit description mentions
>> what needs to be passed on the kernel command line for the corresponding
>> board.
>>
>> Combining it in a single patch makes it much harder to extract this information.
>> Unless you're fine with a list:
>>
>>    koelsch: ...
>>    wheat: mtdparts=spi0.0:256k at 0(loader),4096k(user),-(flash)
> 
> Lets try a list.

Reposted with a list, twice :/

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2018-05-30 10:13 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22 12:02 [PATCH 1/9] ARM: shmobile: defconfig: Enable MTD command line partition parsing Marek Vasut
2018-05-22 12:02 ` Marek Vasut
2018-05-22 12:02 ` Marek Vasut
2018-05-22 12:02 ` [PATCH 2/9] ARM: dts: lager: Drop MTD partitioning from DT Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:34   ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 14:32   ` Geert Uytterhoeven
2018-05-22 14:32     ` Geert Uytterhoeven
2018-05-22 14:32     ` Geert Uytterhoeven
2018-05-22 21:55     ` Marek Vasut
2018-05-22 21:55       ` Marek Vasut
2018-05-22 21:55       ` Marek Vasut
2018-05-22 12:02 ` [PATCH 3/9] ARM: dts: stout: " Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:34   ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 14:33   ` Geert Uytterhoeven
2018-05-22 14:33     ` Geert Uytterhoeven
2018-05-22 14:33     ` Geert Uytterhoeven
2018-05-22 12:02 ` [PATCH 4/9] ARM: dts: koelsch: " Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:34   ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 14:29   ` Geert Uytterhoeven
2018-05-22 14:29     ` Geert Uytterhoeven
2018-05-22 14:29     ` Geert Uytterhoeven
2018-05-22 12:02 ` [PATCH 5/9] ARM: dts: porter: " Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:34   ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 14:34   ` Geert Uytterhoeven
2018-05-22 14:34     ` Geert Uytterhoeven
2018-05-22 14:34     ` Geert Uytterhoeven
2018-05-22 12:02 ` [PATCH 6/9] ARM: dts: wheat: " Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:34   ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 14:43   ` Geert Uytterhoeven
2018-05-22 14:43     ` Geert Uytterhoeven
2018-05-22 14:43     ` Geert Uytterhoeven
2018-05-22 22:01     ` Marek Vasut
2018-05-22 22:01       ` Marek Vasut
2018-05-22 22:01       ` Marek Vasut
2018-05-23  6:25       ` Geert Uytterhoeven
2018-05-23  6:25         ` Geert Uytterhoeven
2018-05-23  6:25         ` Geert Uytterhoeven
2018-05-24 14:52         ` Marek Vasut
2018-05-24 14:52           ` Marek Vasut
2018-05-24 14:52           ` Marek Vasut
2018-05-28  8:41           ` Simon Horman
2018-05-28  8:41             ` Simon Horman
2018-05-28  8:41             ` Simon Horman
2018-05-28  8:54             ` Geert Uytterhoeven
2018-05-28  8:54               ` Geert Uytterhoeven
2018-05-28  8:54               ` Geert Uytterhoeven
2018-05-28  9:36               ` Simon Horman
2018-05-28  9:36                 ` Simon Horman
2018-05-28  9:36                 ` Simon Horman
2018-05-30 10:13                 ` Marek Vasut [this message]
2018-05-30 10:13                   ` Marek Vasut
2018-05-30 10:13                   ` Marek Vasut
2018-05-31 11:40                   ` Simon Horman
2018-05-31 11:40                     ` Simon Horman
2018-05-31 11:40                     ` Simon Horman
2018-05-22 12:02 ` [PATCH 7/9] ARM: dts: gose: " Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:34   ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 14:44   ` Geert Uytterhoeven
2018-05-22 14:44     ` Geert Uytterhoeven
2018-05-22 14:44     ` Geert Uytterhoeven
2018-05-22 12:02 ` [PATCH 8/9] ARM: dts: alt: " Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:34   ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 14:45   ` Geert Uytterhoeven
2018-05-22 14:45     ` Geert Uytterhoeven
2018-05-22 14:45     ` Geert Uytterhoeven
2018-05-22 12:02 ` [PATCH 9/9] ARM: dts: silk: " Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:02   ` Marek Vasut
2018-05-22 12:34   ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 12:34     ` Wolfram Sang
2018-05-22 14:46   ` Geert Uytterhoeven
2018-05-22 14:46     ` Geert Uytterhoeven
2018-05-22 14:46     ` Geert Uytterhoeven
2018-05-22 12:32 ` [PATCH 1/9] ARM: shmobile: defconfig: Enable MTD command line partition parsing Wolfram Sang
2018-05-22 12:32   ` Wolfram Sang
2018-05-22 12:32   ` Wolfram Sang
2018-05-22 14:29 ` Geert Uytterhoeven
2018-05-22 14:29   ` Geert Uytterhoeven
2018-05-22 14:29   ` Geert Uytterhoeven
2018-05-28  8:40 ` Simon Horman
2018-05-28  8:40   ` Simon Horman
2018-05-28  8:40   ` Simon Horman

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=d78bb8a8-a351-409c-54d2-33ee02fd8afe@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=boris.brezillon@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=richard@nod.at \
    --cc=wsa@the-dreams.de \
    /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.