From: Brian Norris <computersforpeace@gmail.com>
To: Jonas Gorski <jogo@openwrt.org>
Cc: Zhiqiang Hou <B48286@freescale.com>,
MTD Maling List <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
Mingkai.Hu@freescale.com, Rafa?? Mi??ecki <zajec5@gmail.com>,
mike@steroidmicros.com
Subject: Re: [PATCH V6] mtd: m25p80: Modify the name of mtd_info
Date: Mon, 17 Aug 2015 18:30:19 -0700 [thread overview]
Message-ID: <20150818013019.GB17499@localhost> (raw)
In-Reply-To: <CAOiHx=mFoke2sTQGsjyNF+k8DFq4GAt9AgU8ednxn5Kx4R7SNw@mail.gmail.com>
On Mon, Aug 17, 2015 at 06:27:36PM +0200, Jonas Gorski wrote:
> On Mon, Aug 17, 2015 at 6:27 AM, Zhiqiang Hou <B48286@freescale.com> wrote:
> > From: Hou Zhiqiang <B48286@freescale.com>
> >
> > Set the mtd_info's name to a fixed one, so spi flash layouts can
> > be specified by "mtdparts=..." in kernel cmdline, because the
> > cmdlinepart's parser will match the name of mtd_info with the name
> > given in cmdline.
> >
> > So far, if DT is used, the mtd_info's name will be set to the name
> > of spi->dev. It includes spi_master->bus_num, and the bus_num may
> > be dynamically allocated. So, replace the component bus_num with
> > the physical address of spi controller.
>
> You can easily enforce fixed bus numers in linux using aliases in the
> DT, this is supported
> by the spi core since v3.9 or so.
Interesting. Thanks for the suggestion. I haven't verified it myself,
but if this is a workable solution, then I'd much prefer that to
fiddling with the name here. So, tentative NAK.
> Also won't this change break it for everyone relying on the old naming
> in their commandline mtdparts?
Yes, and that's been my comment on the first several versions. I didn't
have time to bother repeating it on these latter revisions.
Brian
next prev parent reply other threads:[~2015-08-18 1:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 4:27 [PATCH V6] mtd: m25p80: Modify the name of mtd_info Zhiqiang Hou
2015-08-17 16:27 ` Jonas Gorski
2015-08-17 16:44 ` Michal Suchanek
2015-08-18 1:30 ` Brian Norris [this message]
2015-08-18 8:38 ` Jonas Gorski
2015-08-18 9:00 ` Hou Zhiqiang
2015-08-18 8:29 ` Hou Zhiqiang
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=20150818013019.GB17499@localhost \
--to=computersforpeace@gmail.com \
--cc=B48286@freescale.com \
--cc=Mingkai.Hu@freescale.com \
--cc=dwmw2@infradead.org \
--cc=jogo@openwrt.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mike@steroidmicros.com \
--cc=zajec5@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox