From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 01/14] mmc: tegra: support Tegra124
Date: Mon, 27 Jan 2014 09:53:19 -0700 [thread overview]
Message-ID: <52E68EFF.3090203@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ0Lizk1RFyU6ZfCoe7GH5aJErdFFGEPnXndJ7VSMrRpWw@mail.gmail.com>
On 01/26/2014 09:11 AM, Simon Glass wrote:
> Hi Stephen,
>
> On 24 January 2014 12:46, Stephen Warren <swarren@wwwdotorg.org
> <mailto:swarren@wwwdotorg.org>> wrote:
>
> From: Stephen Warren <swarren at nvidia.com <mailto:swarren@nvidia.com>>
>
> Tegra124's MMC controller is very similar to earlier SoC generations,
> and can be supported by the same driver.
>
> However, there are some non-backwards-compatible HW differences, and
> hence a new DT compatible value must be used to describe the HW. This
> patch updates the driver to support that new compatible value.
>
> That said, the HW differences are only relevant when enabling certain
> high-performance transfer modes. Since the driver is currently very
> simple and doesn't enable those modes, we don't actually need to address
> any of these HW differences in the code yet, hence the simple nature of
> this patch.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com
> <mailto:swarren@nvidia.com>>
> Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com
> <mailto:panto@antoniou-consulting.com>>
> Tested-by: Thierry Reding <treding@nvidia.com
> <mailto:treding@nvidia.com>>
>
>
> As a general comment on this series (not this patch) there is is
> distressing amount of code duplication. It seems to me that this is just
> going to get more and more painful unless it is addressed. Removing and
> refactoring duplicated code is a difficult task. In particular defining
> almost identical clock functions in multiple files just doesn't seem
> like a good idea.
Granted this is true. I am in the process of filing a bug to
de-duplicate the drivers.
> Other than that this series looks good to me.
Thanks. Is that an ack? :-)
next prev parent reply other threads:[~2014-01-27 16:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 19:46 [U-Boot] [PATCH V3 01/14] mmc: tegra: support Tegra124 Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 02/14] ARM: tegra: misc cleanups triggered by Tegra124 review Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 03/14] ARM: tegra: pass just partition ID to power_partition() Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 04/14] ARM: tegra: enable PLLX only once it's been fully configured Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 05/14] ARM: tegra: remove a conditional for CSITE rate Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 06/14] ARM: tegra: only build __pinmux_nand() when it's needed Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 07/14] ARM: tegra: fix a typo in the tegra114.dtsi Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 08/14] ARM: tegra: add/edit headers for Tegra124 Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 09/14] ARM: tegra: add SPL/AVP (arm720t) CPU files " Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 10/14] ARM: tegra: Add CPU (armv7) " Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 11/14] ARM: tegra: add common (shared) CPU files Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 12/14] ARM: tegra: add DT files for Tegra124 and Venice2 Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 13/14] ARM: tegra: add Venice2 (Tegra124) board Stephen Warren
2014-01-24 19:46 ` [U-Boot] [PATCH V3 14/14] ARM: tegra: fix "bootp" issue for Tegra124 too Stephen Warren
2014-01-26 16:11 ` [U-Boot] [PATCH V3 01/14] mmc: tegra: support Tegra124 Simon Glass
2014-01-27 16:53 ` Stephen Warren [this message]
2014-01-27 17:17 ` Simon Glass
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=52E68EFF.3090203@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 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.