From: Valentine Barshak <vbarshak@ru.mvista.com>
To: Dale Farnsworth <dale@farnsworth.org>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] PowerPC 440EPx Sequoia USB OHCI DTS entry
Date: Wed, 24 Oct 2007 17:44:51 +0400 [thread overview]
Message-ID: <471F4C53.1070506@ru.mvista.com> (raw)
In-Reply-To: <20071024120804.GA1180@xyzzy.farnsworth.org>
Dale Farnsworth wrote:
> On Wed, Oct 24, 2007 at 03:19:14PM +0400, Valentine Barshak wrote:
>> Dale Farnsworth wrote:
>>> Valentine wrote:
>>>> Actually I also don't see much reason for the
>>>> USB_OHCI_HCD_PPC_OF_BE/USB_OHCI_HCD_PPC_OF_LE stuff.
>>>> Is this really needed?
>>> I think so. The SOC host controllers are BE and the PCI
>>> host controllers are LE. Or, do you have an alternative
>>> method of handling both types?
>> Yes, PCI controllers are LE, but do we really need user-selectable
>> USB_OHCI_HCD_PPC_OF_LE option, since USB_OHCI_LITTLE_ENDIAN is selected
>> by default for USB_OHCI_HCD_PCI?
>> The USB_OHCI_HCD_PPC_OF_LE/BE stuff is related to PPC OF glue only.
>> I think it's useless. We should always enable
>> USB_OHCI_BIG_ENDIAN_DESC and USB_OHCI_BIG_ENDIAN_MMIO for PPC OF
>> and the real LE/BE implementation should be selected by the
>> corresponding properties in the device tree.
>
> I agree that they don't need to be user selectable. It is far preferable
> to deduce their values from existing information, if possible.
>
> -Dale
This is the original thread:
http://ozlabs.org/pipermail/linuxppc-embedded/2006-November/025054.html
I think the USB_OHCI_HCD_PPC_OF_LE/BE should be removed.
We can't avoid the slight overhead even using these options, since
USB_OHCI_BIG_ENDIAN_MMIO/DESC should always be anabled for PPC OF and we
we still enable USB_OHCI_LITTLE_ENDIAN for USB_OHCI_HCD_PCI even if
USB_OHCI_HCD_PPC_OF_LE is not set.
Thanks,
Valentine.
next prev parent reply other threads:[~2007-10-24 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 14:26 [PATCH] PowerPC 440EPx Sequoia USB OHCI DTS entry Valentine Barshak
2007-10-23 15:33 ` Josh Boyer
2007-10-23 15:35 ` Valentine Barshak
2007-10-23 15:50 ` Josh Boyer
2007-10-23 17:03 ` Segher Boessenkool
2007-10-23 17:18 ` Valentine Barshak
2007-10-23 21:40 ` Dale Farnsworth
2007-10-24 11:19 ` Valentine Barshak
2007-10-24 12:08 ` Dale Farnsworth
2007-10-24 13:44 ` Valentine Barshak [this message]
2007-10-24 14:10 ` Dale Farnsworth
2007-10-24 14:23 ` Valentine Barshak
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=471F4C53.1070506@ru.mvista.com \
--to=vbarshak@ru.mvista.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=dale@farnsworth.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.