s, the phy will stall, since interrupts are off. This patch
fixes the issue by calling config_intr after resetting the phy.
Fixes: d2fd719bcb0e ("net/phy: micrel: Add workaround for bad autoneg ")
Signed-off-by: Zach Brown
---
v2:
* Check phy_intterupt_is_valid before calling conf
s, the phy will stall, since interrupts
are off.
This patch fixes the issue by calling config_intr after resetting the
phy.
Fixes: d2fd719bcb0e ("net/phy: micrel: Add workaround for bad autoneg ")
Signed-off-by: Zach Brown
---
drivers/net/phy/micrel.c | 2 ++
1 file changed, 2 in
On Wed, May 17, 2017 at 12:36:35PM +0200, Honza Petrouš wrote:
> 2017-05-16 20:22 GMT+02:00 Richard Weinberger :
> > Zach,
> >
> > Am 16.05.2017 um 19:58 schrieb Zach Brown:
> >> From: Ben Shelton
> >>
> >> Add a file under debugfs to allow easy
From: Ben Shelton
Add a file under debugfs to allow easy access to the erase count for
each physical erase block on an UBI device. This is useful when
debugging data integrity issues with UBIFS on NAND flash devices.
Signed-off-by: Ben Shelton
Signed-off-by: Zach Brown
---
v2:
* If
From: Ben Shelton
Add a file under debugfs to allow easy access to the erase count for
each physical erase block on an UBI device. This is useful when
debugging data integrity issues with UBIFS on NAND flash devices.
Signed-off-by: Ben Shelton
Signed-off-by: Zach Brown
v2:
* If
From: Ben Shelton
Add a file under debugfs to allow easy access to the erase count for
each physical erase block on an UBI device. This is useful when
debugging data integrity issues with UBIFS on NAND flash devices.
Signed-off-by: Ben Shelton
Signed-off-by: Zach Brown
v2:
* If
From: Nathan Sullivan
If the PHY is halted on stop, then do not set the state to PHY_UP. This
ensures the phy will be restarted later in phy_start when the machine is
started again.
Signed-off-by: Nathan Sullivan
Signed-off-by: Brad Mouring
Acked-by: Xander Huff
Acked-by: Kyle Roeschley
---
From: Ben Shelton
Add a file under debugfs to allow easy access to the erase count for
each physical erase block on an UBI device. This is useful when
debugging data integrity issues with UBIFS on NAND flash devices.
Signed-off-by: Ben Shelton
Signed-off-by: Zach Brown
---
drivers/mtd/ubi
troduce function max_bad_blocks
mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available
Zach Brown (3):
mtd: nand: Add max_bb_per_die and blocks_per_die fields to nand_chip
mtd: nand: implement 'max_bad_blocks' mtd function
mtd: nand: set max_bb_per_die an
From: Jeff Westfahl
If the user has not set max_beb_per1024 using either the cmdline or
Kconfig options for doing so, use the MTD function 'max_bad_blocks' to
compute the UBI bad_peb_limit.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drive
The fields max_bb_per_die and blocks_per_die are useful determining the
number of bad blocks a MTD needs to allocate. How they are set will
depend on if the chip is ONFI, JEDEC or a full-id entry in the nand_ids
table.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by: Brian Norris
Implement the new mtd function 'max_bad_blocks'. Using the chip's
max_bb_per_die and blocks_per_die fields to determine the maximum bad
blocks to reserve for an MTD.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by: Brian Norris
---
d
ONFI compliant chips contain the values for the max_bb_per_die and
blocks_per_die fields in the parameter page. When the ONFI paged is
retrieved/parsed the chip's fields are set by the corresponding fields
in the param page.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by:
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for a MTD. An implementation for NAND is coming soon.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by: Brian Norris
---
drivers/mtd
ONFI compliant chips contain the values for the max_bb_per_die and
blocks_per_die fields in the parameter page. When the ONFI paged is
retrieved/parsed the chip's fields are set by the corresponding fields
in the param page.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by:
Implement the new mtd function 'max_bad_blocks'. Using the chip's
max_bb_per_die and blocks_per_die fields to determine the maximum bad
blocks to reserve for an MTD.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by: Brian Norris
---
d
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for a MTD. An implementation for NAND is coming soon.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by: Brian Norris
---
drivers/mtd
From: Jeff Westfahl
If the user has not set max_beb_per1024 using either the cmdline or
Kconfig options for doing so, use the MTD function 'max_bad_blocks' to
compute the UBI bad_peb_limit.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drive
The fields max_bb_per_die and blocks_per_die are useful determining the
number of bad blocks a MTD needs to allocate. How they are set will
depend on if the chip is ONFI, JEDEC or a full-id entry in the nand_ids
table.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by: Brian Norris
peb_limit: cmdline > Kconfig > automatic with mtd_max_bad_blocks
v7:
* Moved mtd_max_bad_blocks function to be with other static inline functions
so it would not look like the odd man out.
Jeff Westfahl (2):
mtd: introduce function max_bad_blocks
mtd: ubi: use 'max_bad_blocks
From: Jeff Westfahl
If the user has not set max_beb_per1024 using either the cmdline or
Kconfig options for doing so, use the MTD function 'max_bad_blocks' to
compute the UBI bad_peb_limit.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drive
The fields max_bb_per_die and blocks_per_die are useful determining the
number of bad blocks a MTD needs to allocate. How they are set will
depend on if the chip is ONFI, JEDEC or a full-id entry in the nand_ids
table.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by: Brian Norris
ONFI compliant chips contain the values for the max_bb_per_die and
blocks_per_die fields in the parameter page. When the ONFI paged is
retrieved/parsed the chip's fields are set by the corresponding fields
in the param page.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by:
bad_peb_limit: cmdline > Kconfig > automatic with mtd_max_bad_blocks
Jeff Westfahl (2):
mtd: introduce function max_bad_blocks
mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available
Zach Brown (3):
mtd: nand: Add max_bb_per_die and blocks_per_die fields to nand_
Implement the new mtd function 'max_bad_blocks'. Using the chip's
max_bb_per_die and blocks_per_die fields to determine the maximum bad
blocks to reserve for an MTD.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by: Brian Norris
---
d
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for a MTD. An implementation for NAND is coming soon.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
Acked-by: Brian Norris
---
drivers/mtd
ers_unregister(phydev);
> -
> /*
>* The phydev might go away on the put_device() below, so avoid
>* a use-after-free bug by reading the underlying bus first.
> --
> 1.9.1
>
I was able to recreate the issue and confirmed this patch fixes it.
Tested-by: Zach Brown
--Zach
the two versions of ni_byt_sdio_probe_slot with new version that
calls ni_set_max_freq.
* Created ni_set_max_freq which sets the slot's max_freq if CONFIG_ACPI is
set.
Zach Brown (2):
mmc: sdhci-pci: Add PCI ID for Intel byt sdio host controller
sub-vended by NI
mmc: sdhc
Amero
Reviewed-by: Josh Cartwright
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 32
1 file changed, 32 insertions(+)
diff --git a/drivers/mmc/host/sdhci-pci-core.c
b/drivers/mmc/host/sdhci-pci-core.c
index 9741505..c9e51b1 100644
--- a
Add PCI ID for Intel byt sdio host controller sub-vended by NI.
The controller has different behavior because of the board layout NI
puts it on.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers
Add PCI ID for Intel byt sdio host controller sub-vended by NI.
The controller has different behavior because of the board layout NI
puts it on.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers
()/acpi_evaluate_object()
pv1:
* Removed redundant comment
* Print info message if MXFQ not found in acpi table
pv2:
* Changed info message to error message if MXFQ not found
* Replaced ni_byt_sdio_probe_slot with one of two versions depending on
whether CONFIG_ACPI is set.
Zach Brown (2
Amero
Reviewed-by: Josh Cartwright
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/mmc/host/sdhci-pci-core.c
b/drivers/mmc/host/sdhci-pci-core.c
index 9741505..34284b8 100644
--- a/drivers
ke sure to include a history.
When switching from RFC to PATCH should the version number of the PATCH
be 1 or the lastest RFC version plus 1? Or does it not matter either way
as long as the history is present?
--
Zach
frequency.
The first patch creates a PCI ID and support for the Intel byt sdio where NI is
the subvendor.
The second patch uses the ACPI table to set f_max during the new
ni_byt_sdio_probe_slot.
Zach Brown (2):
mmc: sdhci-pci: Add PCI ID for Intel byt sdio host controller
sub-vended by NI
Amero
Reviewed-by: Josh Cartwright
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/drivers/mmc/host/sdhci-pci-core.c
b/drivers/mmc/host/sdhci-pci-core.c
index 9741505..a855c97 100644
--- a/drivers/mmc/host
Add PCI ID for Intel byt sdio host controller sub-vended by NI.
The controller has different behavior because of the board layout NI
puts it on.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers
Implement the new mtd function 'max_bad_blocks'. Using the chip's
max_bb_per_die and blocks_per_die fields to determine the maximum bad
blocks to reserve for an MTD.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drivers/mtd/nand/n
The fields max_bb_per_die and blocks_per_die are useful determining the
number of bad blocks a MTD needs to allocate. How they are set will
depend on if the chip is ONFI, JEDEC or a full-id entry in the nand_ids
table.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
include/linux/mtd
ONFI compliant chips contain the values for the max_bb_per_die and
blocks_per_die fields in the parameter page. When the ONFI paged is
retrieved/parsed the chip's fields are set by the corresponding fields
in the param page.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
driver
tyle issue
[1]
http://lkml.iu.edu/hypermail/linux/kernel/1505.1/04822.html
Jeff Westfahl (2):
mtd: introduce function max_bad_blocks
mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available
Zach Brown (3):
mtd: nand: Add max_bb_per_die and blocks_per_die fields to na
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for an MTD. An implementation for NAND is coming soon.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drivers/mtd/mtdpar
From: Jeff Westfahl
Use the MTD function 'max_bad_blocks' to compute the UBI bad_peb_limit,
if the function is implemented for an MTD and doesn't return an error.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drivers/mtd/ubi/build.c |
frequency.
The first patch creates a PCI ID and support for the Intel byt sdio where NI is
the subvendor.
The second patch uses the ACPI table to set f_max during the new
ni_byt_sdio_probe_slot.
v2:
* Use acpi_evaluate_integer() instead of
acpi_get_handle()/acpi_evaluate_object()
Zach Brown
Amero
Reviewed-by: Josh Cartwright
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/mmc/host/sdhci-pci-core.c
b/drivers/mmc/host/sdhci-pci-core.c
index 9741505..4c31d16 100644
--- a/drivers/mmc/host/sdhci
Add PCI ID for Intel byt sdio host controller sub-vended by NI.
The controller has different behavior because of the board layout NI
puts it on.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers
On Wed, Nov 09, 2016 at 03:24:24PM +0200, Adrian Hunter wrote:
> On 08/11/16 22:07, Zach Brown wrote:
> > On NI 9037 boards the max SDIO frequency is limited by trace lengths
> > and other layout choices. The max SDIO frequency is stored in an ACPI
> > table, as MXFQ.
> &g
Add PCI ID for Intel byt sdio host controller sub-vended by NI.
The controller has different behavior because of the board layout NI
puts it on.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/mmc
frequency.
The first patch creates a PCI ID and support for the Intel byt sdio where NI is
the subvendor.
The second patch uses the ACPI table to set f_max during the new
ni_byt_sdio_probe_slot.
Zach Brown (2):
mmc: sdhci-pci: Add PCI ID for Intel byt sdio host controller
sub-vended by NI
Reviewed-by: Jaeden Amero
Reviewed-by: Josh Cartwright
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci-pci-core.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/drivers/mmc/host/sdhci-pci-core.c
b/drivers/mmc/host/sdhci-pci-core.c
index c333ce2..4ac7f16
ONFI compliant chips contain the values for the max_bb_per_die and
blocks_per_die fields in the parameter page. When the ONFI paged is
retrieved/parsed the chip's fields are set by the corresponding fields
in the param page.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
driver
The fields max_bb_per_die and blocks_per_die are useful determining the
number of bad blocks a MTD needs to allocate. How they are set will
depend on if the chip is ONFI, JEDEC or a full-id entry in the nand_ids
table.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
include/linux/mtd
Implement the new mtd function 'max_bad_blocks'. Using the chip's
max_bb_per_die and blocks_per_die fields to determine the maximum bad
blocks to reserve for an MTD.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drivers/mtd/nand/n
tyle issue
[1]
http://lkml.iu.edu/hypermail/linux/kernel/1505.1/04822.html
Jeff Westfahl (2):
mtd: introduce function max_bad_blocks
mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available
Zach Brown (3):
mtd: nand: Add max_bb_per_die and blocks_per_die fields to na
From: Jeff Westfahl
Use the MTD function 'max_bad_blocks' to compute the UBI bad_peb_limit,
if the function is implemented for an MTD and doesn't return an error.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drivers/mtd/ubi/build.c |
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for an MTD. An implementation for NAND is coming soon.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drivers/mtd/mtdpar
__sdhci_read_caps
Use the sdhci-caps-mask property to turn off the incorrect bits of the
sdhci register after reading them.
Use the sdhci-caps to turn on bits after using sdhci-caps-mask to turn
off the incorrect ones.
Signed-off-by: Zach Brown
Acked-by: Adrian Hunter
---
drivers/mmc/host/sdhci.c | 24
.
Signed-off-by: Zach Brown
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/mmc/sdhci.txt | 14 ++
1 file changed, 14 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mmc/sdhci.txt
diff --git a/Documentation/devicetree/bindings/mmc/sdhci.txt
b
issue, all branches of 'if' should have {}
Zach Brown (2):
mmc: sdhci: dt: Add device tree properties sdhci-caps and
sdhci-caps-mask
mmc: sdhci: Use sdhci-caps-mask and sdhci-caps to change the caps read
during __sdhci_read_caps
Documentation/devicetree/bindings/mmc
On Tue, Nov 01, 2016 at 02:50:58PM +0100, Boris Brezillon wrote:
> On Fri, 28 Oct 2016 15:27:42 -0500
> Zach Brown wrote:
>
> > The fields bb_per_lun and blocks_per_lun are useful determining the
> > number of bad blocks a MTD needs to allocate. How they are set will
> &g
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for an MTD. An implementation for NAND is coming soon.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/mtdpart.c | 13 +
include/linux/mtd/
l
Jeff Westfahl (2):
mtd: introduce function max_bad_blocks
mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available
Zach Brown (3):
mtd: nand: Add bb_per_die and blocks_per_die fields to nand_chip
mtd: nand: implement 'max_bad_blocks' mtd function
mtd:
From: Jeff Westfahl
Use the MTD function 'max_bad_blocks' to compute the UBI bad_peb_limit,
if the function is implemented for an MTD and doesn't return an error.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/ubi/build.c | 4
1 file change
The fields bb_per_die and blocks_per_die are useful determining the
number of bad blocks a MTD needs to allocate. How they are set will
depend on if the chip is ONFI, JEDEC or a full-id entry in the nand_ids
table.
Signed-off-by: Zach Brown
---
include/linux/mtd/nand.h | 5 +
1 file changed
Implement the new mtd function 'max_bad_blocks'. Using the chip's
bb_per_die and blocks_per_die fields to determine the maximum bad blocks
to reserve for an MTD.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/nand/nand_base.c | 35 +++
ONFI compliant chips contain the values for the bb_per_die and
blocks_per_die fields in the parameter page. When the ONFI paged is
retrieved/parsed the chip's fields are set by the corresponding fields
in the param page.
Signed-off-by: Zach Brown
---
drivers/mtd/nand/nand_base.c | 4 ++
On Tue, Nov 01, 2016 at 07:13:29AM +0900, Jaehoon Chung wrote:
> On 10/31/2016 09:34 PM, Adrian Hunter wrote:
> > On 31/10/16 13:59, Jaehoon Chung wrote:
> >> On 10/28/2016 05:12 PM, Ulf Hansson wrote:
> >>> On 25 October 2016 at 21:58, Zach Brown wrote:
> >>
Implement the new mtd function 'max_bad_blocks'. Using the chip's
bb_per_lun and blocks_per_lun fields to determine the maximum bad blocks
to reserve for an MTD.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/nand/nand_base.c | 35 +++
From: Jeff Westfahl
Use the MTD function 'max_bad_blocks' to compute the UBI bad_peb_limit,
if the function is implemented for an MTD and doesn't return an error.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/ubi/build.c | 4
1 file change
ONFI compliant chips contain the values for the bb_per_lun and
blocks_per_lun fields in the parameter page. When the ONFI paged is
retrieved/parsed the chip's fields are set by the corresponding fields
in the param page.
Signed-off-by: Zach Brown
---
drivers/mtd/nand/nand_base.c | 5 +++
fi
* Max bad blocks calculation now uses the new nand_chip fields
[1]
http://lkml.iu.edu/hypermail/linux/kernel/1505.1/04822.html
Jeff Westfahl (2):
mtd: introduce function max_bad_blocks
mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available
Zach Brown (3):
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for an MTD. An implementation for NAND is coming soon.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/mtdpart.c | 13 +
include/linux/mtd/
The fields bb_per_lun and blocks_per_lun are useful determining the
number of bad blocks a MTD needs to allocate. How they are set will
depend on if the chip is ONFI, JEDEC or a fuill-id entry in the nand_ids
table.
Signed-off-by: Zach Brown
---
include/linux/mtd/nand.h | 5 +
1 file
represent the correction to the sdhci caps register.
The second patch uses the new dt properties to correct the caps from the
register as they read during __sdhci_read_caps.
Changes from RFC:
* /s/registers/register
* Moved sdhci dt properties into new documentation file sdhci.txt
Zach Brown (2
__sdhci_read_caps
Use the sdhci-caps-mask property to turn off the incorrect bits of the
sdhci register after reading them.
Use the sdhci-caps to turn on bits after using sdhci-caps-mask to turn
off the incorrect ones.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci.c | 24
.
Signed-off-by: Zach Brown
---
Documentation/devicetree/bindings/mmc/sdhci.txt | 14 ++
1 file changed, 14 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mmc/sdhci.txt
diff --git a/Documentation/devicetree/bindings/mmc/sdhci.txt
b/Documentation/devicetree
From: Jeff Westfahl
Implement the new mtd function 'max_bad_blocks'. Use the ONFI parameter
page to find the maximum bad blocks to reserve for an MTD, taking into
account how many LUNs the MTD spans.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/nand/nand_b
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for an MTD. An implementation for NAND is coming soon.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/mtdpart.c | 12
include/linux/mtd/
For ONFI-compliant NAND devices, the ONFI parameters report the maximum number
of bad blocks per LUN that will be encountered over the lifetime of the device,
so we can use that information to get a more accurate (and smaller) value for
the UBI bad PEB limit.
The ONFI parameter "maxiumum number of
From: Jeff Westfahl
Use the MTD function 'max_bad_blocks' to compute the UBI bad_peb_limit,
if the function is implemented for an MTD and doesn't return an error.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/ubi/build.c | 9 +
1 file change
On Fri, Oct 21, 2016 at 11:41:46AM -0700, Eric Dumazet wrote:
> On Fri, 2016-10-21 at 13:03 -0500, Zach Brown wrote:
> > Is there a way to get NAPI to poll all the time?
> > Or just any way to get netdevices to use only polling and no interrupts?
> >
> > We have some
On Tue, Oct 25, 2016 at 02:30:25PM +0300, Adrian Hunter wrote:
> On 24/10/16 18:48, Zach Brown wrote:
> > On Mon, Oct 24, 2016 at 10:34:46AM +0300, Adrian Hunter wrote:
> >> On 22/10/16 00:35, Zach Brown wrote:
> >>> When the sdhci-cap-speed-modes-broken DT property
__sdhci_read_caps
Use the sdhci-caps-mask property to turn off the incorrect bits of the
sdhci registers after reading them.
Use the sdhci-caps to turn on bits after using sdhci-caps-mask to turn
off the incorrect ones.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci.c | 24
represent the correction to the sdhci caps register.
The second patch uses the new dt properties to correct the caps from the
register as they read during __sdhci_read_caps.
Zach Brown (2):
mmc: sdhci: dt: Add device tree properties sdhci-caps and sdhci-caps-mask
mmc: sdhci: Use sdhci-caps-mask
on.
Signed-off-by: Zach Brown
---
Documentation/devicetree/bindings/mmc/mmc.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt
b/Documentation/devicetree/bindings/mmc/mmc.txt
index 8a37782..1415aa0 100644
--- a/Documentation/devicetree
.
Signed-off-by: Zach Brown
---
Documentation/devicetree/bindings/mmc/mmc.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt
b/Documentation/devicetree/bindings/mmc/mmc.txt
index 8a37782..671d6c0 100644
--- a/Documentation/devicetree/bindings/mmc
When the sdhci-cap-speed-modes-broken DT property is set, the driver
will ignore the bits of the capability registers that correspond to
speed modes.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci.c | 25 +++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff
bits to clear in sdhci cap1, not
sure that's all of the them now, but I think so.
v3:
* Read "sdhci-cap-speed-modes-broken" only once.
* If caps are provided to sdhci_read_caps the speed bits are not overwritten.
Zach Brown (2):
mmc: sdhci: Add device tree property sdhci-
On Mon, Oct 24, 2016 at 10:34:46AM +0300, Adrian Hunter wrote:
> On 22/10/16 00:35, Zach Brown wrote:
> > When the sdhci-cap-speed-modes-broken DT property is set, the driver
> > will ignore the bits of the capability registers that correspond to
> > speed modes.
> >
&g
bits to clear in sdhci cap1, not sure
that's all of the them now, but I think so.
Zach Brown (2):
mmc: sdhci: Add device tree property sdhci-cap-speed-modes-broken
mmc: sdhci: Ignore capability register when it comes to speeds and use
DT binding instead when sdhci-cap-speed-
When the sdhci-cap-speed-modes-broken DT property is set, the driver
will ignore the bits of the capability registers that correspond to
speed modes.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/mmc/host/sdhci.c b
.
Signed-off-by: Zach Brown
---
Documentation/devicetree/bindings/mmc/mmc.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt
b/Documentation/devicetree/bindings/mmc/mmc.txt
index 8a37782..671d6c0 100644
--- a/Documentation/devicetree/bindings/mmc
Is there a way to get NAPI to poll all the time?
Or just any way to get netdevices to use only polling and no interrupts?
We have some rt targets where the jitter can be improved by disabling
interrupts and using just polling. In these cases we're okay with the
performance downsides that come with
From: Jeff Westfahl
Implement the new mtd function 'max_bad_blocks'. Use the ONFI parameter
page to find the maximum bad blocks to reserve for an MTD, taking into
account how many LUNs the MTD spans.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/nand/nand_b
For ONFI-compliant NAND devices, the ONFI parameters report the maximum number
of bad blocks per LUN that will be encountered over the lifetime of the device,
so we can use that information to get a more accurate (and smaller) value for
the UBI bad PEB limit.
The ONFI parameter "maxiumum number of
From: Jeff Westfahl
Use the MTD function 'max_bad_blocks' to compute the UBI bad_peb_limit,
if the function is implemented for an MTD and doesn't return an error.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/ubi/build.c | 9 +
1 file change
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for an MTD. An implementation for NAND is coming soon.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
---
drivers/mtd/mtdpart.c | 12
include/linux/mtd/
implements the get_ringparam and set_ringparam fucntions.
Zach Brown (2):
net: macb: Use variables with defaults for tx/rx ring sizes instead of
hardcoded values
net: macb: Add ethtool get_ringparam and set_ringparam functionality
drivers/net/ethernet/cadence/macb.c | 173
Some applications want to tune the size of the macb rx/tx ring buffers.
The ethtool set_ringparam function is the standard way of doing it.
Signed-off-by: Zach Brown
---
drivers/net/ethernet/cadence/macb.c | 59 +
1 file changed, 59 insertions(+)
diff --git
respective
replacements.
Signed-off-by: Zach Brown
---
drivers/net/ethernet/cadence/macb.c | 114
drivers/net/ethernet/cadence/macb.h | 3 +
2 files changed, 65 insertions(+), 52 deletions(-)
diff --git a/drivers/net/ethernet/cadence/macb.c
b/drivers/net/ethernet
1 - 100 of 593 matches
Mail list logo
