linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: florian.vaussard@epfl.ch (Florian Vaussard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] ARM: OMAP4: Fix gpmc_fck clock
Date: Tue, 25 Feb 2014 09:10:21 +0100	[thread overview]
Message-ID: <530C4FED.80403@epfl.ch> (raw)
In-Reply-To: <20140225062615.22529.88499@quantum>

On 02/25/2014 07:26 AM, Mike Turquette wrote:
> Quoting Florian Vaussard (2014-02-23 21:44:25)
>> On 02/23/2014 10:23 PM, Mike Turquette wrote:
>>> Quoting Florian Vaussard (2014-02-19 11:26:43)
>>>>
>>>> On 02/19/2014 05:22 PM, Tero Kristo wrote:
>>>>> On 02/19/2014 11:15 AM, Florian Vaussard wrote:
>>>>>> Hello,
>>>>>>
>>>>>> Trying to get my SMSC9221 working on OMAP4 with DT,
>>>>>> I faced a misconfigured gpmc_fck (dummy clock set to 0)
>>>>>> resulting in serveral division-by-zero, misconfigured
>>>>>> timings and driver lost in the La La Land.
>>>>>>
>>>>>> To solve this, patch 1 removes gpmc_fck from the dummy
>>>>>> clocks, and patch 2 adds the gpmc_fck DT node and
>>>>>> reference it from the gpmc node.
>>>>>>
>>>>>> Tested on DuoVero/Parlor (OMAP4430) with SMSC9221.
>>>>>
>>>>> I can't test GPMC myself, but other than that, this set looks good to go.
>>>>>
>>>>
>>>> Thank you. Would you like more test coverage by other people? I would
>>>> like to see this in -rc if possible, as it is needed to boot my OMAP4
>>>> system.
>>>
>>> What OMAP4 system is this? Is this a regression for board that already
>>> has support merged into mainline?
>>>
>>
>> No, it is not yet merged into mainline. I was planning to post the DTS
>> this week, when most issues are cleared. Looking at the current mainline
>> boards, no one seems to use the GPMC, so I am just the first one to hit
>> this issue.
> 
> OK, well typically the later -rc's are for fixing observed regressions.
> Since your platform is not yet merged in then it's probably fine to push
> this for 3.15.
> 

Fair enough. 3.15 is fine.

> This also gives time to test the fix for other OMAP-ish processors.
> 

I can do the v3, including OMAP5 and DRA7. But for DRA7, I will need
someone with the TRM telling me where is connected gpmc_fclk (Suman?).

BTW, your mail client seems to have corrupted the To: header, double
quotes " are missing between Tero, Beno?t and Tony's addresses, mixing
them as the same person. Maybe an indigestion caused by the UTF8
character of Beno?t?

Regards,
Florian

  parent reply	other threads:[~2014-02-25  8:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19  9:15 [PATCH v2 0/2] ARM: OMAP4: Fix gpmc_fck clock Florian Vaussard
2014-02-19  9:15 ` [PATCH v2 1/2] CLK: TI: OMAP4: Remove gpmc_fck from dummy clocks Florian Vaussard
2014-02-19  9:15 ` [PATCH v2 2/2] ARM: DTS: OMAP4: Use l3_ick for the gpmc node Florian Vaussard
2014-02-19 16:22 ` [PATCH v2 0/2] ARM: OMAP4: Fix gpmc_fck clock Tero Kristo
2014-02-19 19:26   ` Florian Vaussard
2014-02-20  9:51     ` Tero Kristo
2014-02-21 23:23       ` Tony Lindgren
2014-02-23 20:36         ` Florian Vaussard
     [not found]     ` <20140223212309.22529.75068@quantum>
2014-02-24  5:44       ` Florian Vaussard
     [not found]         ` <20140225062615.22529.88499@quantum>
2014-02-25  8:10           ` Florian Vaussard [this message]
2014-02-26  0:05             ` Suman Anna
2014-02-26  5:11               ` Florian Vaussard

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=530C4FED.80403@epfl.ch \
    --to=florian.vaussard@epfl.ch \
    --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;
as well as URLs for NNTP newsgroup(s).