From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH 1/3] mtd: create a partition type device tree binding Date: Sat, 14 Nov 2015 11:46:59 +0100 Message-ID: References: <1446123152-22666-1-git-send-email-linus.walleij@linaro.org> <20151029162908.GA13275@localhost> <20151030175145.GF13239@google.com> <20151113220039.GA74382@google.com> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro_org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PL7N7OtQGT9S7vCwojK2nvw+YUYxOHOJq0PjM7f1USY=; b=WPFCD/xoPeA8p8VunxeOK40u2QpWOXi7giGi+fPdxogTkqGY3rbthCGpDgSIhIks+H uNf3o3ZU3Lyq7JszLW2x1OndJa13eo7gB0GSVeAGYuYp1IoVn0Le/bSoa5UkmbQLrY4y ZrkDOZb5qpNtJEU9S5SY0I+awDHbsJsLqVtXMH66V3TUSZrdPzdYKaw/37IZ+6lo/XHe /WCqLpEvAnH3Ro+4MWrU8cRL6QwCyrSIyWmpo09j7itKK9iHwf+0qLukv1DaAHJOGGUU 4gu+6M0k5Kz2oZMy4FOJz+QJyzEo5LByglhkOHHhPfXXFHkOzao158TateIELVQft2Ln dIrg== In-Reply-To: <20151113220039.GA74382-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> Sender: devicetree-spec-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Brian Norris Cc: Rob Herring , "devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , David Woodhouse , "linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Jason Gunthorpe , Liviu Dudau , =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Hauke Mehrtens , Michal Suchanek On Fri, Nov 13, 2015 at 11:00 PM, Brian Norris wrote: (...) > (2) we should define a comptible property for the hard-coded > partitioning case (e.g., compatible = "partitions") (...) > If we went with option (2), then ofpart.c could just check only for > 'compatible = "partitions"' (or similar), and if not found bail out. So this "hard-coded partitioning case" the case is where all partitions are defined in the device tree as described in Documentation/devicetree/bindings/mtd/partition.txt ? Or is it a way to indicate that this array static const char * const part_probe_types_def[] = { "cmdlinepart", "RedBoot", "ofpart", "ofoldpart", NULL }; in physmap_of.c should be used? Sorry if I don't fully follow, I'm a bit stupid when it comes to the MTD helicopter view of the situation.... :( > I think option (2) makes more sense. But it would require an update to > the binding and code for 4.4, since [1] was only introduced during this > release cycle. Does that mean all old device trees that specify no compatible string all of a sudden stop working? We can't break the DT ABI, so I guess not. A bit confused here, I can't really see what I should do with the patch... Yours, Linus Walleij