Sending to the list in plain text, argh!
-- Ashwin
---------- Forwarded message ----------
From: Ashwin Bihari <abihari@xxxxxxxxx>
Date: Thu, Jan 29, 2009 at 10:45 AM
Subject: Re: Naming convention used in mux.c
To: "Hiremath, Vaibhav" <hvaibhav@xxxxxx>
Cc: "linux-omap@xxxxxxxxxxxxxxx" <linux-omap@xxxxxxxxxxxxxxx>
Vaibhav,
I was also confused by that when I began playing with the OMAP and
only found those references to make sense when I looked at the
schematics of the board I'm working on. If you look at the Terminal
Pin documents for your specific OMAP you will see the alphabet and
numbers make sense. But you need to know which alphabet/number
specifically is designated to a particular function and this is
something the hardware engineer would do while connecting the OMAP to
the rest of the peripherals on the board.
Regards
-- Ashwin
On Thu, Jan 29, 2009 at 10:34 AM, Hiremath, Vaibhav <hvaibhav@xxxxxx> wrote:
>
> Hi,
>
> Can anybody tell me the meaning of naming convention used in mux.c file, e.g. -
>
> MUX_CFG_34XX("AH8_34XX_GPIO29", 0x5fa,
> OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT)
> MUX_CFG_34XX("J25_34XX_GPIO170", 0x1c6,
> OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT)
>
> What the suffix "AH8_" and "J25_" means here? I looked into TRM and could not able to co-relate with any meaningful?
>
> Thanks,
> Vaibhav Hiremath
> Platform Support Products
> Texas Instruments Inc
> Ph: +91-80-25099927
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
