public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] davinci: Initial support for MityDSP-L138/MityARM-1808
Date: Thu, 02 Sep 2010 11:17:26 -0700	[thread overview]
Message-ID: <87tym857t5.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4C7FE773.5070005@mvista.com> (Sergei Shtylyov's message of "Thu, 02 Sep 2010 22:05:39 +0400")

Sergei Shtylyov <sshtylyov@mvista.com> writes:

> Hello.
>
> Michael Williamson wrote:
>
>> This patch adds initial support for the MityDSP-L138 and MityDSP-1808 system
>> on Module (SOM) under the machine name "mityomapl138".  These SOMs are based
>> on the da850 davinci CPU architecture.  Information on these SOMs may be
>> found at http://www.mitydsp.com.
>
>> Basic support for the console UART, NAND, and EMAC (MII interface) is
>> included in this patch.
>
>> Signed-off-by: Michael Williamson <michael.williamson@criticallink.com>
>
> [...]
>
>> diff --git a/arch/arm/mach-davinci/board-mityomapl138.c b/arch/arm/mach-davinci/board-mityomapl138.c
>> new file mode 100644
>> index 0000000..78c972b
>> --- /dev/null
>> +++ b/arch/arm/mach-davinci/board-mityomapl138.c
>> @@ -0,0 +1,220 @@
> [...]
>> +static const short mityomap_mii_pins[] = {
>> +	DA850_MII_TXEN, DA850_MII_TXCLK, DA850_MII_COL, DA850_MII_TXD_3,
>> +	DA850_MII_TXD_2, DA850_MII_TXD_1, DA850_MII_TXD_0, DA850_MII_RXER,
>> +	DA850_MII_CRS, DA850_MII_RXCLK, DA850_MII_RXDV, DA850_MII_RXD_3,
>> +	DA850_MII_RXD_2, DA850_MII_RXD_1, DA850_MII_RXD_0, DA850_MDIO_CLK,
>> +	DA850_MDIO_D,
>> +	-1
>> +};
>> +
>> +static const short mityomap_rmii_pins[] = {
>> +	DA850_RMII_TXD_0, DA850_RMII_TXD_1, DA850_RMII_TXEN,
>> +	DA850_RMII_CRS_DV, DA850_RMII_RXD_0, DA850_RMII_RXD_1,
>> +	DA850_RMII_RXER, DA850_RMII_MHZ_50_CLK, DA850_MDIO_CLK,
>> +	DA850_MDIO_D,
>> +	-1
>> +};
>> +
>> +static void __init mityomapl138_config_emac(void)
>> +{
>> +	void __iomem *cfg_chip3_base;
>> +	int ret;
>> +	u32 val;
>> +	struct davinci_soc_info *soc_info = &davinci_soc_info;
>
>    Should be an empty line here...

I'll add this before pushing.

>> +	soc_info->emac_pdata->rmii_en = 0; /* hardcoded for now */
>> +
>> +	cfg_chip3_base = DA8XX_SYSCFG0_VIRT(DA8XX_CFGCHIP3_REG);
>> +	val = __raw_readl(cfg_chip3_base);
>> +
>> +	if (soc_info->emac_pdata->rmii_en) {
>
>    If it's hard coded to 0, why handle the other case?

He's planning to add support for the other options in subsequent
patches, so I'm OK with leaving this as is.


>> +		val |= BIT(8);
>> +		ret = davinci_cfg_reg_list(mityomap_rmii_pins);
>> +		pr_info("RMII PHY configured\n");
>> +	} else {
>> +		val &= ~BIT(8);
>> +		ret = davinci_cfg_reg_list(mityomap_mii_pins);
>> +		pr_info("MII PHY configured\n");
>> +	}
>
> WBR, Sergei

Kevin

  reply	other threads:[~2010-09-02 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 17:58 [PATCH v3] davinci: Initial support for MityDSP-L138/MityARM-1808 Michael Williamson
2010-09-02 18:05 ` Sergei Shtylyov
2010-09-02 18:17   ` Kevin Hilman [this message]
2010-09-02 18:10 ` Kevin Hilman

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=87tym857t5.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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