On Sat, Sep 10, 2016 at 3:33 AM, Jagan Teki <jagan@xxxxxxxxxxxxxxxxxxxx> wrote:
> On Sat, Sep 10, 2016 at 3:29 AM, Fabio Estevam <festevam@xxxxxxxxx> wrote:
>> On Fri, Sep 9, 2016 at 6:45 PM, Jagan Teki <jagannadh.teki@xxxxxxxxx> wrote:
>>
>>> +&iomuxc {
>>> + pinctrl_flexcan1: flexcan1grp {
>>> + fsl,pins = <
>>> + MX6QDL_PAD_KEY_ROW2__FLEXCAN1_RX 0x1b020
>>> + MX6QDL_PAD_KEY_COL2__FLEXCAN1_TX 0x1b020
>>
>> In the previous version you had "0x80000000", which means: use the pad
>> value that comes from the bootloader.
>>
>> Does your bootloader configure the CAN pins? If not, then it should be
>> 1b0b0, which is the POR value of register
>> IOMUXC_SW_PAD_CTL_PAD_KEY_ROW2.
>>
>> To confirm, you can do this in your bootloader:
>>
>> => md.l 20E05DC 1
>> 020e05dc: 0001b0b0
>>
>> and see if returns 1b0b0 or 1b020.
>
> Yeah, I got 1b0b0
>
> U-Boot > md.l 20E05DC 1
> 020e05dc: 0001b0b0
So I'm assigning change value to 1b020 Linux that's ok right?
thanks!
--
Jagan Teki
Free Software Engineer | Amarula Solutions
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
