From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.co
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
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.co
on.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
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.
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
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.co
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 <zach.br...@ni.com>
---
include/linux/mtd/nand
<nathan.sulli...@ni.com>
Reviewed-by: Jaeden Amero <jaeden.am...@ni.com>
Reviewed-by: Josh Cartwright <jo...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/mmc/host/sdhci-pci-core.c | 30 ++
1 file changed, 30 insertions(+)
diff
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 <zach.br...@ni.com>
---
drivers/mmc/host/sdhci-pci-core.c | 20
1 file changed, 20 insertions(+)
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
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.
>
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 nand_chip
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br..
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com&g
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 <zach.br...@ni.com>
Acked-by: Boris Bre
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
Acked-by: Bor
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 <zach.br...@ni.com>
Acked-by: Boris Bre
highspeed
impossible. For example, we send the SDIO lines through a fpga so we
need the data to change on the falling edge of the clock or there will
be issues with hold time.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/mmc/host/sdhci.c | 4 +++-
1 file changed, 3 insertions
that
highspeed will not work.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
Documentation/devicetree/bindings/mmc/mmc.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt
b/Documentation/devicetree/bindings/mmc/mmc.txt
index 8a37782..a2b298c
would've checked quirk
Zach Brown (2):
sdhci: Add device tree property broken-highspeed
sdhci: Prevent SD from doing high-speed timing when broken-highspeed
property is set
Documentation/devicetree/bindings/mmc/mmc.txt | 2 ++
drivers/mmc/host/sdhci.c | 4 +++-
2
On Thu, Oct 06, 2016 at 10:03:56AM +0200, Ulf Hansson wrote:
> On 5 October 2016 at 22:03, Rob Herring <robh...@kernel.org> wrote:
> > On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson <ulf.hans...@linaro.org> wrote:
> >> On 23 September 2016 at 22:01, Zach Brown <zach.b
highspeed
impossible. For example, we send the SDIO lines through a fpga so we
need the data to change on the falling edge of the clock or there will
be issues with hold time.
Signed-off-by: Zach Brown <zach.br...@ni.com>
Acked-by: Adrian Hunter <adrian.hun...@intel.com>
---
drivers/mmc/
that
highspeed will not work.
Signed-off-by: Zach Brown <zach.br...@ni.com>
Acked-by: Rob Herring <r...@kernel.org>
---
Documentation/devicetree/bindings/mmc/mmc.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt
b/Documentation/devicetree/
.
The first patch adds documentation about a new devicetree property
broken-highspeed.
The second patch keeps the sd controller and card from going into highspeed
mode when the property is set.
Zach Brown (2):
sdhci: Add device tree property broken-highspeed
sdhci: Prevent SD from doing high-speed
On Tue, Oct 18, 2016 at 09:13:50AM +0200, Andrew Lunn wrote:
> On Mon, Oct 17, 2016 at 10:49:55AM -0500, Zach Brown wrote:
> > Create an option CONFIG_LED_TRIGGER_PHY (default n), which will create a
> > set of led triggers for each instantiated PHY device. There is one LED
>
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
.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
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/Documen
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 <zach.br...@ni.com>
---
drivers/mmc/host/sdhci.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/d
of 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-modes
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
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 <zach.br...@ni.com>
---
drivers/mmc/host/sdhci.c | 25 +++--
1 file changed, 23 insertions
of 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-cap-s
.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
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/Documen
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.co
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.co
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
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-
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 <zach.br...@ni.com>
---
drivers/net/ethernet/cadence/macb.c | 59 +
1 file chang
to their respective
replacements.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
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/mac
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
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 and will read the of properties of the device to determine
which speeds are supported.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
d
sent up.
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1251944.html
Zach Brown (2):
mmc: sdhci: dt: 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-modes
.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
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/Documen
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 <zach.br...@ni.com>
Acked-by: Boris Bre
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 nand_chip
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com&g
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br..
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
Acked-by: Bor
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 <zach.br...@ni.com>
Acked-by: Boris Bre
lli...@ni.com>
Reviewed-by: Jaeden Amero <jaeden.am...@ni.com>
Reviewed-by: Josh Cartwright <jo...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/mmc/host/sdhci-pci-core.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/mmc/
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 <zach.br...@ni.com>
---
drivers/mmc/host/sdhci-pci-core.c | 24
1 file changed, 24 inse
lli...@ni.com>
Reviewed-by: Jaeden Amero <jaeden.am...@ni.com>
Reviewed-by: Josh Cartwright <jo...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/mmc/host/sdhci-pci-core.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/drivers/mmc/host/sdhci-p
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
On Tue, Nov 22, 2016 at 09:27:29AM +0100, Ulf Hansson wrote:
>
> Please try to not forget to bump the version number and to provide a
> history of the what changes between revisions. It makes life easier
> when reviewing and when I am about to apply patches.
>
Sorry, I'll make sure to include a
()/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
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 <zach.br...@ni.com>
---
drivers/mmc/host/sdhci-pci-core.c | 24
1 file changed, 24 inse
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: sdhci-pci
lli...@ni.com>
Reviewed-by: Jaeden Amero <jaeden.am...@ni.com>
Reviewed-by: Josh Cartwright <jo...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/mmc/host/sdhci-pci-core.c | 32
1 file changed, 32 insertions(+)
diff --git a/drivers/m
hy_led_triggers_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.br...@ni.com>
--Zach
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 <zach.br...@ni.com>
---
drivers/mmc/host/sdhci-pci-core.c | 24
1 file changed, 24 inse
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
lli...@ni.com>
Reviewed-by: Jaeden Amero <jaeden.am...@ni.com>
Reviewed-by: Josh Cartwright <jo...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/mmc/host/sdhci-pci-core.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/mmc/host/sdhci-p
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 <zach.br...@ni.com>
---
drivers/mmc/host/sdhci-pci-core.c | 24
1 file changed, 24 inse
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 <zach.br...@ni.c
On Tue, Nov 01, 2016 at 02:50:58PM +0100, Boris Brezillon wrote:
> On Fri, 28 Oct 2016 15:27:42 -0500
> Zach Brown <zach.br...@ni.com> wrote:
>
> > The fields bb_per_lun and blocks_per_lun are useful determining the
> > number of bad blocks a MTD needs to allocate. How t
__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 <zach.br...@ni.com>
---
drivers/mmc/host/sdhci.
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/sdhci.txt
__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 <zach.br...@ni.com>
Acked-by: Adrian Hunter <a
on.
Signed-off-by: Zach Brown <zach.br...@ni.com>
Acked-by: Rob Herring <r...@kernel.org>
---
Documentation/devicetree/bindings/mmc/sdhci.txt | 14 ++
1 file changed, 14 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mmc/sdhci.txt
diff --git a/D
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
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/mtd/nand
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.co
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 <zach.br...@ni.com>
---
drivers/mt
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):
mtd:
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 <zach.br...@ni.com>
---
drivers/mt
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.co
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 <zach.br...@ni.com>
---
include/linux/mtd/nand
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/mtd/nand
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.co
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: nand: set bb_per_di
On Tue, Oct 11, 2016 at 02:14:07PM -0700, Stephen Hemminger wrote:
> On Tue, 11 Oct 2016 15:26:18 -0500
> Zach Brown <zach.br...@ni.com> wrote:
>
> > Adding led support for phy causes namespace conflicts for some
> > phy drivers.
> >
> > The marvel skge d
On Thu, Oct 13, 2016 at 10:46:34AM -0400, David Miller wrote:
> From: Zach Brown <zach.br...@ni.com>
> Date: Tue, 11 Oct 2016 15:26:20 -0500
>
> > From: Josh Cartwright <josh.cartwri...@ni.com>
> >
> > Create an option CONFIG_LED_TRIGGER_PHY (default
ore. Actions that should
occur whenever the phy link is adjusted can now be added to the
phy_adjust_link function.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/net/phy/phy.c | 21 +
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/drivers/net/phy/phy.c
changed LED_ON to LED_REG_ON to avoid possible future conflict and
for consistency.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/net/ethernet/marvell/skge.c | 6 +++---
drivers/net/ethernet/marvell/skge.h | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/d
f LEDs
to represent link state changes on the phy.
Signed-off-by: Josh Cartwright <josh.cartwri...@ni.com>
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/net/phy/Kconfig| 13 +++-
drivers/net/phy/
and improve consistency.
* Dropped rtl8712 patch that was accepted separately.
v4:
* tweaked commit message
Josh Cartwright (1):
net: phy: leds: add support for led triggers on phy link state change
Zach Brown (2):
skge: Rename LED_OFF and LED_ON in marvel skge driver to avoid
conflicts
On Mon, Oct 10, 2016 at 02:03:32AM -0700, Florian Fainelli wrote:
> > +
> > +#ifdef CONFIG_LED_TRIGGER_PHY
> > +
> > +#include
> > +#include
> > +
> > +#define PHY_LINK_LED_MAX_TRIGGERS 5
> > +#define PHY_LED_TRIGGER_SPEED_SUFFIX_SIZE 7
> > +#define PHY_MII_BUS_ID_SIZE(20 - 3)
>
>
ore. Actions that should
occur whenever the phy link is adjusted can now be added to the
phy_adjust_link function.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/net/phy/phy.c | 21 +
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/drivers/net/phy/phy.c
changed LED_ON to LED_REG_ON to avoid possible future conflict and
for consistency.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/net/ethernet/marvell/skge.c | 6 +++---
drivers/net/ethernet/marvell/skge.h | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/d
phy_supported_speeds provides a means to get a list of all the speeds a
phy device currently supports.
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/net/phy/phy.c | 35 +++
include/linux/phy.h | 15 +++
2 files changed, 50 inse
ist of triggers to dynamic list determined by speeds
return by phy_supported_speeds.
Zach Brown (4):
skge: Rename LED_OFF and LED_ON in marvel skge driver to avoid
conflicts with leds namespace
net: phy: Encapsulate actions performed during link state changes into
funct
by this patch the leds not controlled by the phy can
be configured to show the current speed of the ethernet connection. The
leds controlled by the phy are unaffected.
Signed-off-by: Josh Cartwright <josh.cartwri...@ni.com>
Signed-off-by: Nathan Sullivan <nathan.sulli...@ni.com>
Signed-off-by
m>
Signed-off-by: Zach Brown <zach.br...@ni.com>
---
drivers/mtd/ubi/debug.c | 151 +++-
1 file changed, 150 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/ubi/debug.c b/drivers/mtd/ubi/debug.c
index f101a49..6086822 100644
--- a/drivers/mtd
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com&g
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 <zach.br...@ni.com>
Acked-by: Boris Bre
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 <jeff.westf...@ni.com>
Signed-off-by: Zach Brown <zach.br...@ni.com>
Acked-by: Bor
nction 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 and blocks_per_die for ONFI comp
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 <zach.br...@ni.com>
Acked-by: Boris Bre
From: Jeff Westfahl <jeff.westf...@ni.com>
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 <jeff.westf...@ni.com>
Signed-off-by
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 <zach.br...@ni.com>
Acked-by: Boris Bre
401 - 500 of 1040 matches
Mail list logo
