From: Cory Maccarrone <darkstar6262@gmail.com>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: linux-omap@vger.kernel.org, linwizard-devel@lists.sf.net
Subject: Re: [PATCH 1/4] [OMAP1] Add MMC board code common to HTC devices
Date: Tue, 1 Jun 2010 08:33:03 -0700 [thread overview]
Message-ID: <AANLkTilYNPttOPe24ZUw2kB6nDs9KRR1FfPx9nPfRvZL@mail.gmail.com> (raw)
In-Reply-To: <20100601101947.GB4085@localhost.localdomain>
On Tue, Jun 1, 2010 at 3:19 AM, Ladislav Michl <Ladislav.Michl@seznam.cz> wrote:
> On Fri, May 28, 2010 at 10:28:04PM -0700, Cory Maccarrone wrote:
>> This change adds the htc-mmc.c and htc-mmc.h files that
>> contain common setup code for many OMAP850-based HTC
>> smartphones. This code is a port of the code used by
>> the linwizard project to support devices such as the
>> HTC Wizard, HTC Herald, HTC Opal, etc.
>>
>> Signed-off-by: Cory Maccarrone <darkstar6262@gmail.com>
>> ---
>> arch/arm/mach-omap1/htc-mmc.c | 104 +++++++++++++++++++++++++++++++++++++++++
>> arch/arm/mach-omap1/htc-mmc.h | 26 ++++++++++
>> 2 files changed, 130 insertions(+), 0 deletions(-)
>> create mode 100644 arch/arm/mach-omap1/htc-mmc.c
>> create mode 100644 arch/arm/mach-omap1/htc-mmc.h
>>
>> diff --git a/arch/arm/mach-omap1/htc-mmc.c b/arch/arm/mach-omap1/htc-mmc.c
>> new file mode 100644
>> index 0000000..4fa8bb4
>> --- /dev/null
>> +++ b/arch/arm/mach-omap1/htc-mmc.c
>> @@ -0,0 +1,104 @@
>> +/*
>> + * linux/arch/arm/mach-omap1/htc-mmc.c
>> + *
>> + * Copyright (C) 2007 Instituto Nokia de Tecnologia - INdT
>> + * Author: Felipe Balbi <felipe.lima@indt.org.br>
>> + *
>> + * This code is based on linux/arch/arm/mach-omap2/board-n800-mmc.c, which is:
>> + * Copyright (C) 2006 Nokia Corporation
>> + *
>> + * This program is free software; you can redistribute it and/or modify
>> + * it under the terms of the GNU General Public License version 2 as
>> + * published by the Free Software Foundation.
>> + */
>> +
>> +#include <plat/mmc.h>
>> +#include <asm/mach-types.h>
>> +
>> +#include <linux/gpio.h>
>> +#include <linux/delay.h>
>> +
>> +#if defined(CONFIG_MMC_OMAP) || defined(CONFIG_MMC_OMAP_MODULE)
>> +
>> +#define OMAP_MMC_REG_SYSC (0xfffb7800 + 0x32)
>> +#define OMAP_MMC_REG_SYSS (0xfffb7800 + 0x34)
>
> Where are these used?
>
>> +static int slot_cover_open;
>> +static struct device *mmc_device;
>> +
>> +static int htc_mmc_set_power(struct device *dev, int slot, int power_on,
>> + int vdd)
>> +{
>> +#ifdef CONFIG_MMC_DEBUG
>> + dev_dbg(dev, "Set slot %d power: %s (vdd %d)\n", slot + 1,
>> + power_on ? "on" : "off", vdd);
>> +#endif
>> + if (slot != 0) {
>> + dev_err(dev, "No such slot %d\n", slot + 1);
>> + return -ENODEV;
>> + }
>> +
>> + return 0;
>> +}
>
> No-op?
>
>> +static int htc_mmc_set_bus_mode(struct device *dev, int slot, int bus_mode)
>> +{
>> +#ifdef CONFIG_MMC_DEBUG
>> + dev_dbg(dev, "Set slot %d bus_mode %s\n", slot + 1,
>> + bus_mode == MMC_BUSMODE_OPENDRAIN ? "open-drain" : "push-pull");
>> +#endif
>> + if (slot != 0) {
>> + dev_err(dev, "No such slot %d\n", slot + 1);
>> + return -ENODEV;
>> + }
>> +
>> + /* Treated on upper level */
>> +
>> + return bus_mode;
>> +}
>> +
>> +static int htc_mmc_get_cover_state(struct device *dev, int slot)
>> +{
>> + BUG_ON(slot != 0);
>> + return slot_cover_open;
>> +}
>
> Just a complicated way to return zero...
>
>> +static int htc_mmc_late_init(struct device *dev)
>> +{
>> + mmc_device = dev;
>> + return 0;
>> +}
>
> What is this good for?
>
>> +static void htc_mmc_cleanup(struct device *dev)
>> +{
>> +}
>> +
>> +static struct omap_mmc_platform_data htc_mmc1_data = {
>> + .nr_slots = 1,
>> + .switch_slot = NULL,
>> + .init = htc_mmc_late_init,
>> + .cleanup = htc_mmc_cleanup,
>> + .slots[0] = {
>> + .set_power = htc_mmc_set_power,
>> + .set_bus_mode = htc_mmc_set_bus_mode,
>> + .get_ro = NULL,
>> + .get_cover_state = htc_mmc_get_cover_state,
>> + .ocr_mask = MMC_VDD_28_29 | MMC_VDD_30_31 |
>> + MMC_VDD_32_33 | MMC_VDD_33_34,
>> + .name = "mmcblk",
>> + .nomux = 1,
>> + .wires = 4,
>> + .switch_pin = -1,
>> + },
>> +};
>
> To me above seems completely no-op, so it could be simplified this way:
> static struct omap_mmc_platform_data htc_mmc1_data = {
> .nr_slots = 1,
> .switch_slot = NULL,
> .slots[0] = {
> .ocr_mask = MMC_VDD_28_29 | MMC_VDD_30_31 |
> MMC_VDD_32_33 | MMC_VDD_33_34,
> .name = "mmcblk",
> .nomux = 1,
> .wires = 4,
> .switch_pin = -1,
> },
> };
>
> Now, once this file contains only one structure definition, is it worth
> to let it exist at all? What about adding it to board-htcherald.c instead?
>
>> +
>> +static struct omap_mmc_platform_data *htc_mmc_data[1];
>> +
>> +void __init htc_mmc_init(void)
>> +{
>> + /* register it */
>> + htc_mmc_data[0] = &htc_mmc1_data;
>> + omap1_init_mmc(htc_mmc_data, 1);
>> +}
>> +#endif
>> +
>> diff --git a/arch/arm/mach-omap1/htc-mmc.h b/arch/arm/mach-omap1/htc-mmc.h
>> new file mode 100644
>> index 0000000..480de14
>> --- /dev/null
>> +++ b/arch/arm/mach-omap1/htc-mmc.h
>> @@ -0,0 +1,26 @@
>> +/*
>> + * linux/arch/arm/mach-omap1/htc-mmc.h
>> + *
>> + * Copyright (C) 2007 Instituto Nokia de Tecnologia - INdT
>> + * Author: Felipe Balbi <felipe.lima@indt.org.br>
>> + *
>> + * This code is based on linux/arch/arm/mach-omap2/board-n800-mmc.c, which is:
>> + * Copyright (C) 2006 Nokia Corporation
>> + *
>> + * This program is free software; you can redistribute it and/or modify
>> + * it under the terms of the GNU General Public License version 2 as
>> + * published by the Free Software Foundation.
>> + */
>> +#ifndef __HTC_MMC_H
>> +#define __HTC_MMC_H
>> +
>> +#if defined(CONFIG_MMC_OMAP) || defined(CONFIG_MMC_OMAP_MODULE)
>> +extern void htc_mmc_init(void);
>> +#else
>> +static inline void htc_mmc_init(void)
>> +{
>> +}
>> +#endif
>> +
>> +#endif /* __HTC_MMC_H */
>> +
>> --
>> 1.7.0.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Thanks for the feedback. I had originally intended this code to be
used by other devices that have yet to be submitted, but looking at
your comments, you're right -- most of that is a no-op. It can very
easily be moved directly into the board file.
This patch can be disregarded, and I'll submit a revised version of
patch 4 for the herald.
Thanks.
- Cory
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-01 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 5:28 [PATCH 0/4] MMC, I2C, HTCPLD for HTC Herald Cory Maccarrone
2010-05-29 5:28 ` [PATCH 1/4] [OMAP1] Add MMC board code common to HTC devices Cory Maccarrone
2010-06-01 10:19 ` Ladislav Michl
2010-06-01 15:33 ` Cory Maccarrone [this message]
2010-05-29 5:28 ` [PATCH 2/4] [OMAP] gpio: Allow for extended GPIO space Cory Maccarrone
2010-05-29 5:28 ` [PATCH 3/4] [OMAP] Add allowance for extra IRQ space Cory Maccarrone
2010-05-29 5:28 ` [PATCH 4/4] [OMAP] HTCHERALD: MMC, I2C, HTCPLD and related devices Cory Maccarrone
2010-06-01 15:37 ` Cory Maccarrone
2010-06-01 15:41 ` [PATCHv2 " Cory Maccarrone
2010-06-01 15:50 ` Cory Maccarrone
2010-06-01 15:54 ` [PATCHv3 " Cory Maccarrone
2010-07-06 8:44 ` Tony Lindgren
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=AANLkTilYNPttOPe24ZUw2kB6nDs9KRR1FfPx9nPfRvZL@mail.gmail.com \
--to=darkstar6262@gmail.com \
--cc=ladis@linux-mips.org \
--cc=linux-omap@vger.kernel.org \
--cc=linwizard-devel@lists.sf.net \
/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;
as well as URLs for NNTP newsgroup(s).