From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Is there a omap_gpmc.c maintainer?
Date: Fri, 3 Aug 2018 11:08:29 -0400 [thread overview]
Message-ID: <20180803150829.GI32145@bill-the-cat> (raw)
In-Reply-To: <CAHCN7xLmFGoHMtv+VQ82bGCaooCW_QZ4YpYdoPjndcn4TSPY7w@mail.gmail.com>
On Thu, Aug 02, 2018 at 07:47:35AM -0500, Adam Ford wrote:
> Is there a maintainer for the omap_gpmc driver? Only the u-boot open
> list is returned when queried.
>
> ./scripts/get_maintainer.pl ./drivers/mtd/nand/omap_gpmc.c
> u-boot at lists.denx.de (open list)
>
> I was thinking about (but not promising) adding some device tree
> support to enable fetching GPMC timings from device tree and
> configuring and/or re-configuring the GPMC timings based on DT
> contents.
>
> I wanted to shoot my ideas off someone else and/or not duplicate any
> work, but I am not volunteering to take over this driver.
>
> Mostly because the GPMC timings setup for NAND and NOR are fairly
> generic for NAND/NOR, and it would be nice to optimize them a bit to
> see if we could get a little faster performance when loading ramdisks
> or kernels via GPMC. Some peripherals (like ethernet) use the GPMC
> bus, and we have some hard-coded values, but this kind of information
> can be fetched from device trees and may also yield a little bit of
> optimization.
Ah, there is not a specific maintainer for the driver.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180803/3790c6a6/attachment.sig>
prev parent reply other threads:[~2018-08-03 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 12:47 [U-Boot] Is there a omap_gpmc.c maintainer? Adam Ford
2018-08-03 15:08 ` Tom Rini [this message]
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=20180803150829.GI32145@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox