Hi Bjorn,
> What problem does this patch solve, Ben? I assume you have devices
> that do change TotalVFs when ARI is enabled, and you do want the new
> value?
>
> Or is the problem something like the following:
>
> - ...
> - Linux PCI core sees TotalVFs = X (saved as iov->total_VFs)
> -
Hi Bjorn,
> What problem does this patch solve, Ben? I assume you have devices
> that do change TotalVFs when ARI is enabled, and you do want the new
> value?
>
> Or is the problem something like the following:
>
> - ...
> - Linux PCI core sees TotalVFs = X (saved as iov->total_VFs)
> -
bit, the check fails, and the VFs cannot be
enabled.
To fix the issue, write SRIOV_CTRL first, and then read SRIOV_NUM_VF.
Signed-off-by: Ben Shelton
---
Changes since v1:
* Moved read of SRIOV_NUM_VF rather than re-reading it if ARI was enabled.
drivers/pci/iov.c | 9 +
1 file changed
bit, the check fails, and the VFs cannot be
enabled.
To fix the issue, write SRIOV_CTRL first, and then read SRIOV_NUM_VF.
Signed-off-by: Ben Shelton <benjamin.h.shel...@intel.com>
---
Changes since v1:
* Moved read of SRIOV_NUM_VF rather than re-reading it if ARI was enabled.
drivers/pci/
Hi Bjorn,
On Wed, Oct 07, 2015 at 02:29:40PM -0500, Bjorn Helgaas wrote:
> Hi Ben,
>
> On Fri, Sep 11, 2015 at 04:55:00PM -0500, Ben Shelton wrote:
> > For some SR-IOV devices, the number of available virtual functions
> > increases after enabling ARI. Currently, SRIOV_NUM
Hi Bjorn,
On Wed, Oct 07, 2015 at 02:29:40PM -0500, Bjorn Helgaas wrote:
> Hi Ben,
>
> On Fri, Sep 11, 2015 at 04:55:00PM -0500, Ben Shelton wrote:
> > For some SR-IOV devices, the number of available virtual functions
> > increases after enabling ARI. Currently, SRIOV_NUM
ils,
and the VFs cannot be enabled.
To fix the issue, after ARI is enabled for a device, reread SRIOV_NUM_VF.
Signed-off-by: Ben Shelton
---
drivers/pci/iov.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
index ee0ebff..88b1
ils,
and the VFs cannot be enabled.
To fix the issue, after ARI is enabled for a device, reread SRIOV_NUM_VF.
Signed-off-by: Ben Shelton <benjamin.h.shel...@intel.com>
---
drivers/pci/iov.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/pci/iov.c b/dr
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for an MTD.
Signed-off-by: Jeff Westfahl
---
drivers/mtd/mtdpart.c | 12
include/linux/mtd/mtd.h | 1 +
2 files changed, 13 insertions(+)
diff --git
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.
Currently, the UBIFS code computes the bad PEB limit based on the
worst-case assumption that all the bad blocks could be in a single
From: Jeff Westfahl
Implement the new mtd function 'max_bad_blocks'. Use the "bad blocks
maximum per LUN" field in the ONFI parameter page to find the maximum
number of bad blocks to reserve for an MTD, taking into account the
number of LUNs in the NAND device and how many LUNs the MTD spans.
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 UBIFS bad PEB limit.
These patches are ordered in terms
From: Jeff Westfahl jeff.westf...@ni.com
Implement the new mtd function 'max_bad_blocks'. Use the bad blocks
maximum per LUN field in the ONFI parameter page to find the maximum
number of bad blocks to reserve for an MTD, taking into account the
number of LUNs in the NAND device and how many LUNs
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 UBIFS bad PEB limit.
These patches are ordered in terms
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.
Currently, the UBIFS code computes the bad PEB limit based on the
worst-case assumption that all the bad blocks
From: Jeff Westfahl jeff.westf...@ni.com
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for an MTD.
Signed-off-by: Jeff Westfahl jeff.westf...@ni.com
---
drivers/mtd/mtdpart.c | 12
include/linux/mtd/mtd.h | 1 +
2 files changed, 13
On 04/27, Brian Norris wrote:
> On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
> > On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
> > wrote:
> > > On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
> > >> Oh, I thought every driver has to implement that
On 04/27, Brian Norris wrote:
On Tue, Apr 28, 2015 at 08:18:12AM +0530, punnaiah choudary kalluri wrote:
On Tue, Apr 28, 2015 at 4:53 AM, Brian Norris
computersforpe...@gmail.com wrote:
On Tue, Apr 28, 2015 at 12:19:16AM +0200, Richard Weinberger wrote:
Oh, I thought every driver has to
the bad block table will go.
Signed-off-by: Ben Shelton
---
drivers/mtd/cmdlinepart.c | 33 ++---
1 file changed, 26 insertions(+), 7 deletions(-)
diff --git a/drivers/mtd/cmdlinepart.c b/drivers/mtd/cmdlinepart.c
index c850300..2d0eda2 100644
--- a/drivers/mtd
the bad block table will go.
Signed-off-by: Ben Shelton ben.shel...@ni.com
---
drivers/mtd/cmdlinepart.c | 33 ++---
1 file changed, 26 insertions(+), 7 deletions(-)
diff --git a/drivers/mtd/cmdlinepart.c b/drivers/mtd/cmdlinepart.c
index c850300..2d0eda2 100644
Hi Paul,
On 05/01, Paul Bolle wrote:
> While you're discussing more substantial questions with Brian, I found
> some nits.
>
> On Wed, 2015-04-29 at 14:28 -0500, Ben Shelton wrote:
> > --- a/drivers/mtd/Kconfig
> > +++ b/drivers/mtd/Kconfig
>
>
> > +config M
Hi Brian,
On 04/29, Brian Norris wrote:
> > + This can be useful if, for example, the BBT is stored at the end
> > + of the flash, and you don't want those blocks counted as part of
> > + the last MTD partition.
>
> And why is that a problem? We don't add Kconfig options just because
Hi Brian,
On 04/29, Brian Norris wrote:
+ This can be useful if, for example, the BBT is stored at the end
+ of the flash, and you don't want those blocks counted as part of
+ the last MTD partition.
And why is that a problem? We don't add Kconfig options just because you
Hi Paul,
On 05/01, Paul Bolle wrote:
While you're discussing more substantial questions with Brian, I found
some nits.
On Wed, 2015-04-29 at 14:28 -0500, Ben Shelton wrote:
--- a/drivers/mtd/Kconfig
+++ b/drivers/mtd/Kconfig
+config MTD_RESERVE_END
+ int Reserved space
From: Jeff Westfahl
Add a new config parameter CONFIG_MTD_RESERVE_END. This is used with
command line partition parsing to reserve space at the end of a
partition defined with a size of '-', which indicates it should use all
remaining space.
Signed-off-by: Jeff Westfahl
---
From: Jeff Westfahl jeff.westf...@ni.com
Add a new config parameter CONFIG_MTD_RESERVE_END. This is used with
command line partition parsing to reserve space at the end of a
partition defined with a size of '-', which indicates it should use all
remaining space.
Signed-off-by: Jeff Westfahl
Hi Punnaiah,
On 04/13, Punnaiah Choudary Kalluri wrote:
> Add driver for arm pl353 static memory controller nand interface with
> HW ECC support. This controller is used in xilinx zynq soc for interfacing
> the nand flash memory.
>
> Signed-off-by: Punnaiah Choudary Kalluri
[...]
> +
>
Hi Punnaiah,
> +/**
> + * pl353_smc_set_cycles - Set memory timing parameters
> + * @dev: Pointer to the device struct
> + * @t0: t_rcread cycle time
> + * @t1: t_wcwrite cycle time
> + * @t2: t_rea/t_ceoeoutput enable assertion delay
> + * @t3:
Hi Punnaiah,
+/**
+ * pl353_smc_set_cycles - Set memory timing parameters
+ * @dev: Pointer to the device struct
+ * @t0: t_rcread cycle time
+ * @t1: t_wcwrite cycle time
+ * @t2: t_rea/t_ceoeoutput enable assertion delay
+ * @t3: t_wp
Hi Punnaiah,
On 04/13, Punnaiah Choudary Kalluri wrote:
Add driver for arm pl353 static memory controller nand interface with
HW ECC support. This controller is used in xilinx zynq soc for interfacing
the nand flash memory.
Signed-off-by: Punnaiah Choudary Kalluri punn...@xilinx.com
[...]
On 04/28, Richard Weinberger wrote:
> Am 27.04.2015 um 23:35 schrieb Ben Shelton:
> > I tested this against the latest version of the PL353 NAND driver that
> > Punnaiah
> > has been working to upstream (copying her on this message). With a few
> > changes
> &
Hi Richard,
On 03/25, Richard Weinberger wrote:
> Some Micron NAND chips offer an on-die ECC (AKA internal ECC)
> feature. It is useful when the host-platform does not offer
> multi-bit ECC and software ECC is not feasible.
>
> Based on original work by David Mosberger
>
> Signed-off-by:
Hi Richard,
On 03/25, Richard Weinberger wrote:
Some Micron NAND chips offer an on-die ECC (AKA internal ECC)
feature. It is useful when the host-platform does not offer
multi-bit ECC and software ECC is not feasible.
Based on original work by David Mosberger dav...@egauge.net
On 04/28, Richard Weinberger wrote:
Am 27.04.2015 um 23:35 schrieb Ben Shelton:
I tested this against the latest version of the PL353 NAND driver that
Punnaiah
has been working to upstream (copying her on this message). With a few
changes
to that driver, I got it most of the way
-by: Ben Shelton
---
drivers/net/ethernet/cadence/macb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/cadence/macb.c
b/drivers/net/ethernet/cadence/macb.c
index 9f53872..665c290 100644
--- a/drivers/net/ethernet/cadence/macb.c
+++ b/drivers/net
Hi all,
We're currently carrying a patch out of tree to add subpage read and
write support to the pl353_nand driver. Xilinx is currently working to
mainline this driver; see
http://www.spinics.net/lists/devicetree/msg76307.html
We'd like to upstream our patch, but my concern is that UBIFS
Hi all,
We're currently carrying a patch out of tree to add subpage read and
write support to the pl353_nand driver. Xilinx is currently working to
mainline this driver; see
http://www.spinics.net/lists/devicetree/msg76307.html
We'd like to upstream our patch, but my concern is that UBIFS
-by: Ben Shelton ben.shel...@ni.com
---
drivers/net/ethernet/cadence/macb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/cadence/macb.c
b/drivers/net/ethernet/cadence/macb.c
index 9f53872..665c290 100644
--- a/drivers/net/ethernet/cadence/macb.c
+++ b
>
> CC'ing authors/reviewers.
>
> Brian
This is indeed a bug, and this patch looks like the right fix. Good catch!
Reviewed-by: Ben Shelton
Ben
>
> > Signed-off-by: Taesoo Kim
> > ---
> > fs/ubifs/dir.c | 11 +++
> > 1 file changed, 7 inse
a bug, and this patch looks like the right fix. Good catch!
Reviewed-by: Ben Shelton ben.shel...@ni.com
Ben
Signed-off-by: Taesoo Kim tsgat...@gmail.com
---
fs/ubifs/dir.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/fs/ubifs/dir.c b/fs/ubifs/dir.c
On 02/27, David Miller wrote:
> From: Ben Shelton
> Date: Fri, 27 Feb 2015 15:26:32 -0600
>
> > On 02/20, David Miller wrote:
> >> From: Ben Shelton
> >> Date: Mon, 16 Feb 2015 13:47:06 -0600
> >>
> >> > The National Instruments USB Host
On 02/27, David Miller wrote:
From: Ben Shelton ben.shel...@ni.com
Date: Fri, 27 Feb 2015 15:26:32 -0600
On 02/20, David Miller wrote:
From: Ben Shelton ben.shel...@ni.com
Date: Mon, 16 Feb 2015 13:47:06 -0600
The National Instruments USB Host-to-Host Cable is based on the Prolific
On 02/20, David Miller wrote:
> From: Ben Shelton
> Date: Mon, 16 Feb 2015 13:47:06 -0600
>
> > The National Instruments USB Host-to-Host Cable is based on the Prolific
> > PL-25A1 chipset. Add its VID/PID so the plusb driver will recognize it.
> >
> > Signed-
On 02/20, David Miller wrote:
From: Ben Shelton ben.shel...@ni.com
Date: Mon, 16 Feb 2015 13:47:06 -0600
The National Instruments USB Host-to-Host Cable is based on the Prolific
PL-25A1 chipset. Add its VID/PID so the plusb driver will recognize it.
Signed-off-by: Ben Shelton
The National Instruments USB Host-to-Host Cable is based on the Prolific
PL-25A1 chipset. Add its VID/PID so the plusb driver will recognize it.
Signed-off-by: Ben Shelton
---
drivers/net/usb/plusb.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/net/usb/plusb.c b/drivers/net
The National Instruments USB Host-to-Host Cable is based on the Prolific
PL-25A1 chipset. Add its VID/PID so the plusb driver will recognize it.
Signed-off-by: Ben Shelton ben.shel...@ni.com
---
drivers/net/usb/plusb.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/net/usb
On 11/11, Artem Bityutskiy wrote:
> Pushed this, but made some amendments.
>
> Now all 4 are in the master branch. Would you please re-test them again
> and confirm that they are fine. Then I'll push them to the linux-next
> branch, unless you report that my amendments broke something.
>
> Thank
On 11/11, Artem Bityutskiy wrote:
Pushed this, but made some amendments.
Now all 4 are in the master branch. Would you please re-test them again
and confirm that they are fine. Then I'll push them to the linux-next
branch, unless you report that my amendments broke something.
Thank you!
On 11/10, Artem Bityutskiy wrote:
> Could you please re-test this with any kernel and carefully verify
> symlinks. I think this should not work, because in case of symlinks we
> already store the link target path in the inode, and with this patch the
> target patch will be over-written with the
On 11/10, Artem Bityutskiy wrote:
Could you please re-test this with any kernel and carefully verify
symlinks. I think this should not work, because in case of symlinks we
already store the link target path in the inode, and with this patch the
target patch will be over-written with the
On 11/07, Artem Bityutskiy wrote:
> On Fri, 2014-10-31 at 13:50 -0500, Ben Shelton wrote:
> > From: Subodh Nijsure
> >
> > Signed-off-by: Subodh Nijsure
> > Signed-off-by: Marc Kleine-Budde
> > Signed-off-by: Ben Shelton
> > Acked-by: Brad Mouring
>
On 11/07, Artem Bityutskiy wrote:
On Fri, 2014-10-31 at 13:50 -0500, Ben Shelton wrote:
From: Subodh Nijsure snijs...@grid-net.com
Signed-off-by: Subodh Nijsure snijs...@grid-net.com
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
Signed-off-by: Ben Shelton ben.shel...@ni.com
From: Subodh Nijsure
This patch adds ubifs_err() output to some error paths to tell the user
what's going on.
Signed-off-by: Subodh Nijsure
Signed-off-by: Marc Kleine-Budde
Signed-off-by: Ben Shelton
Acked-by: Brad Mouring
Acked-by: Terry Wilcox
Acked-by: Gratian Crisan
---
fs/ubifs
I'm reposting the patch series for security xattr / SELinux support on UBIFS
from Subodh Nijsure and Marc Kleine-Budde [1] in order to restart the process
of getting this support upstream.
Notes:
- I removed 'UBIFS: xattr: protect ui_size and data_len by ui_mutex' because
after looking
From: Subodh Nijsure
Signed-off-by: Subodh Nijsure
Signed-off-by: Marc Kleine-Budde
Signed-off-by: Ben Shelton
Acked-by: Brad Mouring
Acked-by: Gratian Crisan
---
fs/ubifs/journal.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/fs/ubifs/journal.c b/fs
From: Subodh Nijsure
Signed-off-by: Subodh Nijsure
Signed-off-by: Marc Kleine-Budde
Signed-off-by: Ben Shelton
Acked-by: Brad Mouring
Acked-by: Terry Wilcox
Acked-by: Gratian Crisan
---
fs/ubifs/dir.c | 20 ++
fs/ubifs/super.c | 1 +
fs/ubifs/ubifs.h | 4 +++
fs/ubifs
From: Subodh Nijsure
Signed-off-by: Subodh Nijsure
Signed-off-by: Marc Kleine-Budde
Signed-off-by: Ben Shelton
Acked-by: Terry Wilcox
Acked-by: Gratian Crisan
---
fs/ubifs/file.c | 4
fs/ubifs/xattr.c | 17 -
2 files changed, 16 insertions(+), 5 deletions(-)
diff
From: Subodh Nijsure snijs...@grid-net.com
Signed-off-by: Subodh Nijsure snijs...@grid-net.com
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
Signed-off-by: Ben Shelton ben.shel...@ni.com
Acked-by: Terry Wilcox terry.wil...@ni.com
Acked-by: Gratian Crisan gratian.cri...@ni.com
---
fs/ubifs
From: Subodh Nijsure snijs...@grid-net.com
Signed-off-by: Subodh Nijsure snijs...@grid-net.com
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
Signed-off-by: Ben Shelton ben.shel...@ni.com
Acked-by: Brad Mouring brad.mour...@ni.com
Acked-by: Terry Wilcox terry.wil...@ni.com
Acked-by: Gratian
From: Subodh Nijsure snijs...@grid-net.com
Signed-off-by: Subodh Nijsure snijs...@grid-net.com
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
Signed-off-by: Ben Shelton ben.shel...@ni.com
Acked-by: Brad Mouring brad.mour...@ni.com
Acked-by: Gratian Crisan gratian.cri...@ni.com
---
fs/ubifs
I'm reposting the patch series for security xattr / SELinux support on UBIFS
from Subodh Nijsure and Marc Kleine-Budde [1] in order to restart the process
of getting this support upstream.
Notes:
- I removed 'UBIFS: xattr: protect ui_size and data_len by ui_mutex' because
after looking
From: Subodh Nijsure snijs...@grid-net.com
This patch adds ubifs_err() output to some error paths to tell the user
what's going on.
Signed-off-by: Subodh Nijsure snijs...@grid-net.com
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
Signed-off-by: Ben Shelton ben.shel...@ni.com
Acked
62 matches
Mail list logo
