On Mon, Aug 07, 2017 at 05:26:48PM +0200, Ralf Baechle wrote:
> On Tue, Jul 18, 2017 at 01:29:09PM -0500, Nathan Sullivan wrote:
>
> > Support the National Instruments 169445 board.
>
> Thanks, applied with minor changes:
>
> Ralf
Thank you for your patience!
Nathan
On Mon, Aug 07, 2017 at 05:26:48PM +0200, Ralf Baechle wrote:
> On Tue, Jul 18, 2017 at 01:29:09PM -0500, Nathan Sullivan wrote:
>
> > Support the National Instruments 169445 board.
>
> Thanks, applied with minor changes:
>
> Ralf
Thank you for your patience!
Nathan
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
Changes since v5:
- make device tree addresses on the internal bus relative, and compile with
W=2 to be sure they are in the right format.
Documentation/devicetree/bindings/mips/
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan
---
Changes since v5:
- make device tree addresses on the internal bus relative, and compile with
W=2 to be sure they are in the right format.
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
MAINTAINERS
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
Changes from v4:
- Address Rob Herring's device tree feedback
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
MAINTAINERS | 8 ++
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan
---
Changes from v4:
- Address Rob Herring's device tree feedback
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
MAINTAINERS | 8 ++
arch/mips/boot/dts/Makefile
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
MAINTAINERS | 8 ++
arch/mips/boot/dts/Makefile | 1 +
arch/mip
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan
---
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
MAINTAINERS | 8 ++
arch/mips/boot/dts/Makefile | 1 +
arch/mips/boot/dts/ni/169445.dts
---
Changes from v4:
- Address Rob Herring's device tree feedback
---
Changes from v4:
- Address Rob Herring's device tree feedback
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
Changes from v4:
- Address Rob Herring's device tree feedback
I'm still unclear on the vmlinux.its.S changes. The linux-mti tree has a
config in the image tree for each board it su
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan
---
Changes from v4:
- Address Rob Herring's device tree feedback
I'm still unclear on the vmlinux.its.S changes. The linux-mti tree has a
config in the image tree for each board it supports, and I followed
On Thu, Mar 23, 2017 at 05:29:45PM -0500, Rob Herring wrote:
> On Tue, Mar 14, 2017 at 11:13:23AM -0500, Nathan Sullivan wrote:
> > Support the National Instruments 169445 board.
> >
> > Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
> > ---
> >
On Thu, Mar 23, 2017 at 05:29:45PM -0500, Rob Herring wrote:
> On Tue, Mar 14, 2017 at 11:13:23AM -0500, Nathan Sullivan wrote:
> > Support the National Instruments 169445 board.
> >
> > Signed-off-by: Nathan Sullivan
> > ---
> > Documentation/device
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
MAINTAINERS | 8 ++
arch/mips/boot/dts/Makefile | 1 +
arch/mip
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan
---
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
MAINTAINERS | 8 ++
arch/mips/boot/dts/Makefile | 1 +
arch/mips/boot/dts/ni/169445.dts
Add support for the National Instruments 169445 board
Changes from v3:
- Remove unused ngpios DT property from documentation for the NAND GPIO
bindings and the actual board device tree.
- Add no-output property to the same, for the GPIO controller that is only
used for input signals from
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
.../bindings/gpio/ni,169445-nand-gpio.txt | 38 ++
drivers/gpio/gpio-
Add support for the National Instruments 169445 board
Changes from v3:
- Remove unused ngpios DT property from documentation for the NAND GPIO
bindings and the actual board device tree.
- Add no-output property to the same, for the GPIO controller that is only
used for input signals from
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan
---
.../bindings/gpio/ni,169445-nand-gpio.txt | 38 ++
drivers/gpio/gpio-mmio.c
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
MAINTAINERS | 8 ++
arch/mips/boot/dts/Makefile | 1 +
arch/mip
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan
---
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
MAINTAINERS | 8 ++
arch/mips/boot/dts/Makefile | 1 +
arch/mips/boot/dts/ni/169445.dts
Add support for the National Instruments 169445 board
Changes from v2:
- Hand write the board config fragment, and make it more minimal.
- Add myself as the maintainer of new dirs and files.
Add support for the National Instruments 169445 board
Changes from v2:
- Hand write the board config fragment, and make it more minimal.
- Add myself as the maintainer of new dirs and files.
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
.../bindings/gpio/ni,169445-nand-gpio.txt | 36 ++
drivers/gpio/gpio-
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan
---
.../bindings/gpio/ni,169445-nand-gpio.txt | 36 ++
drivers/gpio/gpio-mmio.c
This adds support for the National Instruments 169445 MIPS system.
Changes from v1:
- Add GPIO patch and board support patch to one set
- Address Rob Herring's device tree feedback
- Convert the 169445 to a generic MIPS board
- Switch to the newer stmmac driver for the board's ethernet
This adds support for the National Instruments 169445 MIPS system.
Changes from v1:
- Add GPIO patch and board support patch to one set
- Address Rob Herring's device tree feedback
- Convert the 169445 to a generic MIPS board
- Switch to the newer stmmac driver for the board's ethernet
On Mon, Mar 06, 2017 at 11:04:13PM +, James Hogan wrote:
> Hi Nathan,
>
> On Mon, Mar 06, 2017 at 02:06:01PM -0600, Nathan Sullivan wrote:
> > Support the National Instruments 169445 board.
> >
> > Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
>
On Mon, Mar 06, 2017 at 11:04:13PM +, James Hogan wrote:
> Hi Nathan,
>
> On Mon, Mar 06, 2017 at 02:06:01PM -0600, Nathan Sullivan wrote:
> > Support the National Instruments 169445 board.
> >
> > Signed-off-by: Nathan Sullivan
> > ---
> > Docume
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
arch/mips/boot/dts/Makefile | 1 +
arch/mips/boot/dts/ni/169445.dts
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan
---
Documentation/devicetree/bindings/mips/ni.txt | 7 ++
arch/mips/boot/dts/Makefile | 1 +
arch/mips/boot/dts/ni/169445.dts| 101
arch/mips/boot/dts/ni
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
.../bindings/gpio/ni,169445-nand-gpio.txt | 36 ++
drivers/gpio/gpio-
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan
---
.../bindings/gpio/ni,169445-nand-gpio.txt | 36 ++
drivers/gpio/gpio-mmio.c
On Thu, Jan 05, 2017 at 06:33:53PM +, Joao Pinto wrote:
> Hi,
>
> Às 6:28 PM de 1/5/2017, Niklas Cassel escreveu:
> > On 01/04/2017 05:38 PM, Nathan Sullivan wrote:
> >> On Tue, Dec 20, 2016 at 05:34:34PM +0100, Ralf Baechle wrote:
> >>> On Fri, Dec
On Thu, Jan 05, 2017 at 06:33:53PM +, Joao Pinto wrote:
> Hi,
>
> Às 6:28 PM de 1/5/2017, Niklas Cassel escreveu:
> > On 01/04/2017 05:38 PM, Nathan Sullivan wrote:
> >> On Tue, Dec 20, 2016 at 05:34:34PM +0100, Ralf Baechle wrote:
> >>> On Fri, Dec
On Tue, Dec 20, 2016 at 05:34:34PM +0100, Ralf Baechle wrote:
> On Fri, Dec 02, 2016 at 09:42:09AM -0600, Nathan Sullivan wrote:
> > Date: Fri, 2 Dec 2016 09:42:09 -0600
> > From: Nathan Sullivan <nathan.sulli...@ni.com>
> > To: r...@linux-mips.org, mark.rutl...@
On Tue, Dec 20, 2016 at 05:34:34PM +0100, Ralf Baechle wrote:
> On Fri, Dec 02, 2016 at 09:42:09AM -0600, Nathan Sullivan wrote:
> > Date: Fri, 2 Dec 2016 09:42:09 -0600
> > From: Nathan Sullivan
> > To: r...@linux-mips.org, mark.rutl...@arm.com, robh...@kernel.org
>
On Fri, Dec 09, 2016 at 03:18:28PM -0600, Rob Herring wrote:
> On Fri, Dec 02, 2016 at 09:42:09AM -0600, Nathan Sullivan wrote:
> > Support the National Instruments 169445 board.
> >
> > Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
> > ---
> >
On Fri, Dec 09, 2016 at 03:18:28PM -0600, Rob Herring wrote:
> On Fri, Dec 02, 2016 at 09:42:09AM -0600, Nathan Sullivan wrote:
> > Support the National Instruments 169445 board.
> >
> > Signed-off-by: Nathan Sullivan
> > ---
> > "gpio: mmi
On Tue, Dec 13, 2016 at 06:40:31PM +, Paul Burton wrote:
> Hi Nathan,
>
> On Friday, 2 December 2016 09:42:09 GMT Nathan Sullivan wrote:
> > Support the National Instruments 169445 board.
> >
> > Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
>
On Tue, Dec 13, 2016 at 06:40:31PM +, Paul Burton wrote:
> Hi Nathan,
>
> On Friday, 2 December 2016 09:42:09 GMT Nathan Sullivan wrote:
> > Support the National Instruments 169445 board.
> >
> > Signed-off-by: Nathan Sullivan
> > ---
> > "gpi
On Fri, Dec 02, 2016 at 04:21:59PM +, Zubair Lutfullah Kakakhel wrote:
> Hi,
>
> On 12/02/2016 03:42 PM, Nathan Sullivan wrote:
> >Support the National Instruments 169445 board.
>
> Interesting patch.
>
> But do you happen to have a link to a description of t
On Fri, Dec 02, 2016 at 04:21:59PM +, Zubair Lutfullah Kakakhel wrote:
> Hi,
>
> On 12/02/2016 03:42 PM, Nathan Sullivan wrote:
> >Support the National Instruments 169445 board.
>
> Interesting patch.
>
> But do you happen to have a link to a description of t
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
"gpio: mmio: add support for NI 169445 NAND GPIO" and
"devicetree: add vendor prefix for National Instruments" are required for the
NAND on this board to work.
Support the National Instruments 169445 board.
Signed-off-by: Nathan Sullivan
---
"gpio: mmio: add support for NI 169445 NAND GPIO" and
"devicetree: add vendor prefix for National Instruments" are required for the
NAND on this board to work.
Documentation/devicetree/bindin
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
"devicetree: add vendor prefix for National Instruments" added the ni vendor
prefix.
This
The GPIO-based NAND controller on National Instruments 169445 hardware
exposes a set of simple lines for the control signals.
Signed-off-by: Nathan Sullivan
---
"devicetree: add vendor prefix for National Instruments" added the ni vendor
prefix.
This patch is needed for "MIPS:
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
This is required by "gpio: mmio: add support for NI 169445 NAND GPIO"
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor
Signed-off-by: Nathan Sullivan
---
This is required by "gpio: mmio: add support for NI 169445 NAND GPIO"
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/
Table 7-62 on page 338 of the i210 datasheet lists TX and RX latencies
for the various speeds the chip supports. To give better ptp timestamp
accuracy, adjust the timestamps by the amounts Intel gives based on
current link speed.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.
Table 7-62 on page 338 of the i210 datasheet lists TX and RX latencies
for the various speeds the chip supports. To give better ptp timestamp
accuracy, adjust the timestamps by the amounts Intel gives based on
current link speed.
Signed-off-by: Nathan Sullivan
---
drivers/net/ethernet/intel
On Thu, Apr 28, 2016 at 08:43:03PM +0200, Andrew Lunn wrote:
> > I agree that is a valid fix for AT91, however it won't solve our problem,
> > since
> > we have no children on the second ethernet MAC in our devices' device
> > trees. I'm
> > starting to feel like our second MAC shouldn't even
On Thu, Apr 28, 2016 at 08:43:03PM +0200, Andrew Lunn wrote:
> > I agree that is a valid fix for AT91, however it won't solve our problem,
> > since
> > we have no children on the second ethernet MAC in our devices' device
> > trees. I'm
> > starting to feel like our second MAC shouldn't even
On Thu, Apr 28, 2016 at 06:32:07PM +0200, Andrew Lunn wrote:
> > Hmm, are AT91 platforms special in this regard? As far as I can tell, this
> > driver (macb) and Marvell PXA are the only ethernet drivers that call
> > mdiobus_scan directly, and PXA does it on a known address. I do see that
> >
On Thu, Apr 28, 2016 at 06:32:07PM +0200, Andrew Lunn wrote:
> > Hmm, are AT91 platforms special in this regard? As far as I can tell, this
> > driver (macb) and Marvell PXA are the only ethernet drivers that call
> > mdiobus_scan directly, and PXA does it on a known address. I do see that
> >
On Thu, Apr 28, 2016 at 05:44:14PM +0200, Nicolas Ferre wrote:
> Le 28/04/2016 16:46, Nathan Sullivan a écrit :
> > Since of_mdiobus_register and mdiobus_register will scan automatically,
> > do not manually scan for PHY devices in the macb ethernet driver. Doing
> > s
On Thu, Apr 28, 2016 at 05:44:14PM +0200, Nicolas Ferre wrote:
> Le 28/04/2016 16:46, Nathan Sullivan a écrit :
> > Since of_mdiobus_register and mdiobus_register will scan automatically,
> > do not manually scan for PHY devices in the macb ethernet driver. Doing
> > s
Since of_mdiobus_register and mdiobus_register will scan automatically,
do not manually scan for PHY devices in the macb ethernet driver. Doing
so will result in many nonexistent PHYs on the MDIO bus if the MDIO
lines are floating or grounded, such as when they are not used.
Signed-off-by: Nathan
Since of_mdiobus_register and mdiobus_register will scan automatically,
do not manually scan for PHY devices in the macb ethernet driver. Doing
so will result in many nonexistent PHYs on the MDIO bus if the MDIO
lines are floating or grounded, such as when they are not used.
Signed-off-by: Nathan
Since of_mdiobus_register and mdiobus_register will scan automatically,
do not manually scan for PHY devices in the macb ethernet driver. Doing
so will result in many nonexistent PHYs on the MDIO bus if the MDIO
lines are floating or grounded, such as when they are not used.
Signed-off-by: Nathan
Since of_mdiobus_register and mdiobus_register will scan automatically,
do not manually scan for PHY devices in the macb ethernet driver. Doing
so will result in many nonexistent PHYs on the MDIO bus if the MDIO
lines are floating or grounded, such as when they are not used.
Signed-off-by: Nathan
On Tue, Nov 03, 2015 at 07:56:55AM -0600, Felipe Balbi wrote:
>
> Hi,
>
> Nathan Sullivan writes:
> > The USB OTG support currently depends on power management
> > (CONFIG_PM) being enabled, but does not actually need it enabled.
> > Remove this dependency.
> &
On Tue, Nov 03, 2015 at 07:56:55AM -0600, Felipe Balbi wrote:
>
> Hi,
>
> Nathan Sullivan <nathan.sulli...@ni.com> writes:
> > The USB OTG support currently depends on power management
> > (CONFIG_PM) being enabled, but does not actually need it enabl
The USB OTG support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-by: Nathan Sullivan
---
drivers/usb/core/Kconfig |1 -
1 file changed, 1 deletion
The USB OTG support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
drivers/usb/core/Kconfig |1 -
The USB OTG support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Remove the unneeded "default n" from USB_OTG as well, the default is
already n.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-
The USB OTG support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Remove the unneeded "default n" from USB_OTG as well, the default is
already n.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-
The USB OTG support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-by: Nathan Sullivan
---
drivers/usb/core/Kconfig |2 --
1 file changed, 2 deletions
The USB OTG support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
drivers/usb/core/Kconfig |2 --
The USB gadget support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-by: Nathan Sullivan
---
drivers/usb/core/Kconfig |1 -
1 file changed, 1 deletion
The USB gadget support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
drivers/usb/core/Kconfig |
From: Ben Shelton
The USB gadget support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-by: Nathan Sullivan
---
drivers/usb/core/Kconfig |1 -
1 file
On Wed, Oct 21, 2015 at 12:20:21PM -0700, Florian Fainelli wrote:
> 2015-10-21 12:17 GMT-07:00 Nathan Sullivan :
> > Very rarely, the KSZ9031 will appear to complete autonegotiation, but
> > will drop all traffic afterwards. When this happens, the idle error
> > count
Very rarely, the KSZ9031 will appear to complete autonegotiation, but
will drop all traffic afterwards. When this happens, the idle error
count will read 0xFF after autonegotiation completes. Reset the PHY
when in that state.
Signed-off-by: Nathan Sullivan
---
drivers/net/phy/micrel.c | 23
Very rarely, the KSZ9031 will appear to complete autonegotiation, but
will drop all traffic afterwards. When this happens, the idle error
count will read 0xFF after autonegotiation completes. Reset the PHY
when in that state.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
d
On Wed, Oct 21, 2015 at 12:20:21PM -0700, Florian Fainelli wrote:
> 2015-10-21 12:17 GMT-07:00 Nathan Sullivan <nathan.sulli...@ni.com>:
> > Very rarely, the KSZ9031 will appear to complete autonegotiation, but
> > will drop all traffic afterwards. When this happens, the
From: Ben Shelton <ben.shel...@ni.com>
The USB gadget support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-by: Nathan Sullivan <nathan.sulli.
On Mon, Oct 05, 2015 at 02:33:56PM -0500, Felipe Balbi wrote:
>
> IIRC we had this dependency because OTG needs support USB bus suspend
> and afaict, that's only available on PM builds
>
> --
> balbi
Hmm, our use case is separate device and host controllers on a Bay Trail
system. We don't
From: Ben Shelton
The USB gadget support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-by: Nathan Sullivan
---
drivers/usb/core/Kconfig |1 -
1 file
From: Ben Shelton <ben.shel...@ni.com>
The USB gadget support currently depends on power management
(CONFIG_PM) being enabled, but does not actually need it enabled.
Remove this dependency.
Tested on Bay Trail hardware with dwc3 USB.
Signed-off-by: Nathan Sullivan <nathan.sulli.
On Mon, Oct 05, 2015 at 02:33:56PM -0500, Felipe Balbi wrote:
>
> IIRC we had this dependency because OTG needs support USB bus suspend
> and afaict, that's only available on PM builds
>
> --
> balbi
Hmm, our use case is separate device and host controllers on a Bay Trail
system. We don't
.
Signed-off-by: Nathan Sullivan
---
Changes from v1 - better describe the issue in the description, the root cause
is that the Zynq hardware does not have big enough tx buffers to hold entire
packets, so streaming must be on.
---
drivers/usb/chipidea/ci_hdrc_usb2.c | 25 +++--
1
Document the binding for the zynq specific chipidea UDC binding.
Signed-off-by: Nathan Sullivan
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
b/Documentation/devicetree
Document the binding for the zynq specific chipidea UDC binding.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.
.
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
---
Changes from v1 - better describe the issue in the description, the root cause
is that the Zynq hardware does not have big enough tx buffers to hold entire
packets, so streaming must be on.
---
drivers/usb/chipidea/ci_hdrc_usb2.c
On Fri, Aug 28, 2015 at 09:30:12AM +0800, Peter Chen wrote:
> On Thu, Aug 27, 2015 at 09:33:07AM -0500, Nathan Sullivan wrote:
> > On Thu, Aug 27, 2015 at 01:11:30PM +0530, punnaiah choudary kalluri wrote:
> > > Hi,
> > >
> > > On Thu, Aug 27, 2015 a
On Fri, Aug 28, 2015 at 09:30:12AM +0800, Peter Chen wrote:
On Thu, Aug 27, 2015 at 09:33:07AM -0500, Nathan Sullivan wrote:
On Thu, Aug 27, 2015 at 01:11:30PM +0530, punnaiah choudary kalluri wrote:
Hi,
On Thu, Aug 27, 2015 at 10:03 AM, Peter Chen peter.c...@freescale.com
wrote
On Thu, Aug 27, 2015 at 01:11:30PM +0530, punnaiah choudary kalluri wrote:
> Hi,
>
> On Thu, Aug 27, 2015 at 10:03 AM, Peter Chen wrote:
> > On Thu, Aug 27, 2015 at 10:59:22AM +0530, sundeep subbaraya wrote:
> >> Hi,
> >>
> >>
> >> On Wed, Au
On Thu, Aug 27, 2015 at 01:11:30PM +0530, punnaiah choudary kalluri wrote:
Hi,
On Thu, Aug 27, 2015 at 10:03 AM, Peter Chen peter.c...@freescale.com wrote:
On Thu, Aug 27, 2015 at 10:59:22AM +0530, sundeep subbaraya wrote:
Hi,
On Wed, Aug 26, 2015 at 8:57 PM, Nathan Sullivan
Document the binding for the zynq specific chipidea UDC binding.
Signed-off-by: Nathan Sullivan
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
b/Documentation/devicetree
The Xilinx Zynq udc does not need the CI_HDRC_DISABLE_STREAMING flag,
unlike the default platform data. Add platform data specific to the
Zynq udc.
Based on a patch by the same name from the Xilinx vendor tree.
Signed-off-by: Nathan Sullivan
---
drivers/usb/chipidea/ci_hdrc_usb2.c | 25
The Xilinx Zynq udc does not need the CI_HDRC_DISABLE_STREAMING flag,
unlike the default platform data. Add platform data specific to the
Zynq udc.
Based on a patch by the same name from the Xilinx vendor tree.
Signed-off-by: Nathan Sullivan nathan.sulli...@ni.com
---
drivers/usb/chipidea
Document the binding for the zynq specific chipidea UDC binding.
Signed-off-by: Nathan Sullivan nathan.sulli...@ni.com
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
b
On Fri, Jul 31, 2015 at 12:22:04AM -0700, David Miller wrote:
> From: Nathan Sullivan
> Date: Thu, 30 Jul 2015 18:09:05 -0500
>
> > On Thu, Jul 30, 2015 at 10:00:34AM -0700, David Miller wrote:
> >> From: Nathan Sullivan
> >> Date: Thu, 30 Jul 2015 10:15:48
On Fri, Jul 31, 2015 at 12:22:04AM -0700, David Miller wrote:
From: Nathan Sullivan nathan.sulli...@ni.com
Date: Thu, 30 Jul 2015 18:09:05 -0500
On Thu, Jul 30, 2015 at 10:00:34AM -0700, David Miller wrote:
From: Nathan Sullivan nathan.sulli...@ni.com
Date: Thu, 30 Jul 2015 10:15:48
On Thu, Jul 30, 2015 at 10:00:34AM -0700, David Miller wrote:
> From: Nathan Sullivan
> Date: Thu, 30 Jul 2015 10:15:48 -0500
>
> > Changes for V2: Actually make sure it compiles this time.
>
> If V1 didn't compile, even for you, then I have a big problem.
>
> A
The ksz9031 has a behavior where it will clear the interrupt enable bits
when leaving power down. To work around this, make sure the interrupt
bits are in the state they are expected to be when resuming.
Signed-off-by: Nathan Sullivan
---
Changes for V2: Actually make sure it compiles
The ksz9031 has a behavior where it will clear the interrupt enable bits
when leaving power down. To work around this, make sure the interrupt
bits are in the state they are expected to be when resuming.
Signed-off-by: Nathan Sullivan nathan.sulli...@ni.com
---
Changes for V2: Actually make
On Thu, Jul 30, 2015 at 10:00:34AM -0700, David Miller wrote:
From: Nathan Sullivan nathan.sulli...@ni.com
Date: Thu, 30 Jul 2015 10:15:48 -0500
Changes for V2: Actually make sure it compiles this time.
If V1 didn't compile, even for you, then I have a big problem.
And that problem
1 - 100 of 126 matches
Mail list logo
