From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-mtd@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 00/12] mtd: nand: davinci: stop using pdev->id as chipselect
Date: Mon, 30 Apr 2018 18:47:51 +0200 [thread overview]
Message-ID: <20180430184751.574550cc@bbrezillon> (raw)
In-Reply-To: <CAMRc=Mf2TKsuiudxPdEFStrstHH65jHb6JFJ0Ort9GvWDSo9bQ@mail.gmail.com>
On Mon, 30 Apr 2018 18:45:06 +0200
Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> 2018-04-30 12:09 GMT+02:00 Boris Brezillon <boris.brezillon@bootlin.com>:
> > Hi Bartosz,
> >
> > On Mon, 30 Apr 2018 10:24:41 +0200
> > Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> >
> >> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> >>
> >> We have the 'ti,davinci-chipselect' property in the device tree, but
> >> when using platform data the driver silently uses the id field of
> >> struct platform_device as the chipselect. This is confusing and we
> >> almost broke the nand support again recently after converting the
> >> platform to common clock framework (which changed the device id in the
> >> clock lookup - the problem is gone now that we no longer acquire the
> >> clock in the nand driver.
> >>
> >> This series adds a new field to davinci-nand platform data, then makes
> >> all board use it and finally modifies the two drivers that make use of
> >> it.
> >>
> >> Bartosz Golaszewski (12):
> >> mtd: nand: davinci: store the core chipselect number in platform data
> >
> > Raw NAND related patches (that is, everything that is not onenand or
> > SPI NAND) should use the "mtd: rawnand: " prefix now. Other than that,
> > I'm fine with the patch series, just let me know how you want to have it
> > merged (through the MTD tree or the davinci tree).
> >
> > Thanks,
> >
> > Boris
>
> I think Sekhar could pick all those patches up for 4.18.
Okay, then I'd need an immutable branch containing these changes.
>
> Sekhar - do you want me to resend the series with the commit message
> changed as requested by Boris, or can you fix it when applying the
> series?
>
> Best regards,
> Bartosz Golaszewski
WARNING: multiple messages have this Message-ID (diff)
From: boris.brezillon@bootlin.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/12] mtd: nand: davinci: stop using pdev->id as chipselect
Date: Mon, 30 Apr 2018 18:47:51 +0200 [thread overview]
Message-ID: <20180430184751.574550cc@bbrezillon> (raw)
In-Reply-To: <CAMRc=Mf2TKsuiudxPdEFStrstHH65jHb6JFJ0Ort9GvWDSo9bQ@mail.gmail.com>
On Mon, 30 Apr 2018 18:45:06 +0200
Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> 2018-04-30 12:09 GMT+02:00 Boris Brezillon <boris.brezillon@bootlin.com>:
> > Hi Bartosz,
> >
> > On Mon, 30 Apr 2018 10:24:41 +0200
> > Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> >
> >> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> >>
> >> We have the 'ti,davinci-chipselect' property in the device tree, but
> >> when using platform data the driver silently uses the id field of
> >> struct platform_device as the chipselect. This is confusing and we
> >> almost broke the nand support again recently after converting the
> >> platform to common clock framework (which changed the device id in the
> >> clock lookup - the problem is gone now that we no longer acquire the
> >> clock in the nand driver.
> >>
> >> This series adds a new field to davinci-nand platform data, then makes
> >> all board use it and finally modifies the two drivers that make use of
> >> it.
> >>
> >> Bartosz Golaszewski (12):
> >> mtd: nand: davinci: store the core chipselect number in platform data
> >
> > Raw NAND related patches (that is, everything that is not onenand or
> > SPI NAND) should use the "mtd: rawnand: " prefix now. Other than that,
> > I'm fine with the patch series, just let me know how you want to have it
> > merged (through the MTD tree or the davinci tree).
> >
> > Thanks,
> >
> > Boris
>
> I think Sekhar could pick all those patches up for 4.18.
Okay, then I'd need an immutable branch containing these changes.
>
> Sekhar - do you want me to resend the series with the commit message
> changed as requested by Boris, or can you fix it when applying the
> series?
>
> Best regards,
> Bartosz Golaszewski
next prev parent reply other threads:[~2018-04-30 16:47 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 8:24 [PATCH 00/12] mtd: nand: davinci: stop using pdev->id as chipselect Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 01/12] mtd: nand: davinci: store the core chipselect number in platform data Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-05-01 9:25 ` Sekhar Nori
2018-05-01 9:25 ` Sekhar Nori
2018-05-01 9:53 ` Sekhar Nori
2018-05-01 9:53 ` Sekhar Nori
2018-05-01 10:29 ` Sekhar Nori
2018-05-01 10:29 ` Sekhar Nori
2018-05-01 10:39 ` Sekhar Nori
2018-05-01 10:39 ` Sekhar Nori
2018-05-02 10:45 ` Bartosz Golaszewski
2018-05-02 10:45 ` Bartosz Golaszewski
2018-05-02 15:00 ` Sekhar Nori
2018-05-02 15:00 ` Sekhar Nori
2018-04-30 8:24 ` [PATCH 02/12] ARM: davinci: da830-evm: specify the chipselect in davinci_nand_pdata Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 03/12] ARM: davinci: da850-evm: " Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 04/12] ARM: davinci: dm355-evm: " Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 05/12] ARM: davinci: dm355-leopard: " Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 06/12] ARM: davinci: dm365-evm: " Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 07/12] ARM: davinci: dm644x-evm: " Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 08/12] ARM: davinci: mityomapl138: " Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 09/12] ARM: davinci: dm646x-evm: " Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 10/12] ARM: davinci: neuros-osd2: " Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 11/12] mtd: nand: davinci: stop using pdev->id as chipselect Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 8:24 ` [PATCH 12/12] ARM: davinci: aemif: stop using pdev->id as nand chipselect Bartosz Golaszewski
2018-04-30 8:24 ` Bartosz Golaszewski
2018-04-30 10:09 ` [PATCH 00/12] mtd: nand: davinci: stop using pdev->id as chipselect Boris Brezillon
2018-04-30 10:09 ` Boris Brezillon
2018-04-30 16:45 ` Bartosz Golaszewski
2018-04-30 16:45 ` Bartosz Golaszewski
2018-04-30 16:47 ` Boris Brezillon [this message]
2018-04-30 16:47 ` Boris Brezillon
2018-05-01 10:12 ` Sekhar Nori
2018-05-01 10:12 ` Sekhar Nori
2018-05-03 9:41 ` Sekhar Nori
2018-05-03 9:41 ` Sekhar Nori
2018-05-01 10:31 ` Sekhar Nori
2018-05-01 10:31 ` Sekhar Nori
2018-05-01 15:02 ` Boris Brezillon
2018-05-01 15:02 ` Boris Brezillon
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=20180430184751.574550cc@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=khilman@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=marek.vasut@gmail.com \
--cc=nsekhar@ti.com \
--cc=richard@nod.at \
--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.