From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND] Altera socfpga big endian work
Date: Wed, 01 Apr 2015 11:50:31 +0100 [thread overview]
Message-ID: <551BCD77.6060906@codethink.co.uk> (raw)
In-Reply-To: <551ADDA0.5010500@opensource.altera.com>
On 31/03/15 18:47, Dinh Nguyen wrote:
>
>
> On 3/31/15 10:34 AM, Ben Dooks wrote:
>> On 31/03/15 15:13, Dinh Nguyen wrote:
>>> Hi Ben,
>>>
>>> On 3/25/15 6:27 AM, Ben Dooks wrote:
>>>> This series enables the core of the socfpga systen to run in big endian
>>>> mode. It inclusdes support for debug uart, secondary core boot and has
>>>> support for timers and initial conversion patches for the mmc.
>>>>
>>>> The two drivers that are known to not work are the Ethernet and the
>>>> dwc2 usb. I do not have data for either, so I currently do not know
>>>> if it possible to change the hardware's endian fetch mode.
>>>>
>>>> The dwc2 driver on my cyclone5 socfpga board with v4.0-rc5 does not
>>>> work in little endian mode, which makes testing converting the driver
>>>> difficult. The supplied 3.10 kernel does work so it is not down to the
>>>> hardware. It detects the presence of a new device and then fails to
>>>> enumerate it (no other errors shown)
>>>>
>>>> This is up on git.baserock.org/delta/linux.git in the branch
>>>> baserock/bjdooks/socfpga-v5
>>>>
>>>> Sorry, this is a resend due to incorrect linux-arm-kernel mailing list
>>>> address.
>>>>
>>>
>>> I think I can take patches 1-3 through my tree, but the mmc patches
>>> [4-7] will need to linux-mmc tree.
>>
>> Thanks. I did CC 4-7 to the relevant maintainers.
>>
>> Any idea if dwc2 is going to be fixed before 4.1?
>>
>>
>
> I'll have to double check again, but I thought dwc2 on the socfpga has
> been work fine for quite some time now. What are the errors that you are
> seeing?
With 4.0-rc5 it failed to enumerate a USB memory stick attached to
the board. It looked like VCC was supplied. We know the adapter is
working as it comes up under the default boot supplied on the board.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2015-04-01 10:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 11:27 [RESEND] Altera socfpga big endian work Ben Dooks
2015-03-25 11:27 ` [PATCH RESEND 1/7] ARM: debug: fix big endian operation for 8250 word mode Ben Dooks
2015-03-25 11:27 ` [PATCH RESEND 2/7] ARM: socfpga: enable big endian for secondary core(s) Ben Dooks
2015-03-25 11:27 ` [PATCH RESEND 3/7] ARM: socfpga: support big endian for socfpga Ben Dooks
2015-03-25 11:27 ` [PATCH RESEND 4/7] clocksource: dw_apb_timer_of: make IO endian agnostic Ben Dooks
2015-03-25 11:27 ` [PATCH RESEND 5/7] mmc: host: dw_mmc make IO accessors " Ben Dooks
2015-03-30 0:48 ` Jaehoon Chung
2015-03-25 11:27 ` [PATCH RESEND 6/7] mmc: host: dw_mmc: change idmac descriptor files to __le32 Ben Dooks
2015-03-25 11:27 ` [PATCH RESEND 7/7] mmc: host: dw_mmc: fix fifo ordering in big endian Ben Dooks
2015-03-31 14:13 ` [RESEND] Altera socfpga big endian work Dinh Nguyen
2015-03-31 15:34 ` Ben Dooks
2015-03-31 17:47 ` Dinh Nguyen
2015-04-01 10:50 ` Ben Dooks [this message]
2015-04-01 14:50 ` Dinh Nguyen
2015-04-01 16:01 ` Ben Dooks
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=551BCD77.6060906@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--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).