Hi all,
This patch series adds support for loading bitstreams into the Altera Cyclone II
connected to an EP9302 on a TS-7300 board.
Changes in v2:
- rebased against fpga/for-next
- added defines for configuration bits and delays
- added error mesage if ioremap() fails
- detailed how the configur
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
fs/ubifs/dir.c: In function 'ubifs_readdir':
fs/ubifs/dir.c:629:13: warning: 'fstr_real_len' may be used uninitialized in
this function [-Wmaybe-uninitialized]
fstr.len = fstr_real_len;
Hi Ulf,
2016-12-13 16:52 GMT+09:00 Ulf Hansson :
> [...]
>
+
+Optional properties:
+For eMMC configuration, supported speed modes are not indicated by the
SDHCI
+Capabilities Register. Instead, the following properties should be
specified
+if supported. See m
Hi Arvind,
Thank you for fixing it.
Acked-by: Yoichi Yuasa
2016-12-13 17:20 GMT+09:00 Arvind Yadav :
> Here, If devm_ioremap will fail. It will return NULL.
> Kernel can run into a NULL-pointer dereference.
> This error check will avoid NULL pointer dereference.
>
> Signed-off-by: Arvind Yadav
2016-12-14 10:59 GMT+09:00 Masahiro Yamada :
> Add a Socionext SoC specific compatible (suggested by Rob Herring).
>
> No SoC specific data are associated with the compatible strings for
> now, but other SoC vendors may use this IP and want to differentiate
> IP variants in the future.
>
> Signed-o
Add a Socionext SoC specific compatible (suggested by Rob Herring).
No SoC specific data are associated with the compatible strings for
now, but other SoC vendors may use this IP and want to differentiate
IP variants in the future.
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Add "unip
On Thu, Dec 8, 2016 at 2:36 PM, Michał Kępień wrote:
> The dell-led driver handles a specific WMI GUID present on some Dell
> laptops and as such it belongs in the x86 platform driver subsystem.
> Source code is moved along with the relevant Kconfig and Makefile
> entries with some minor modificat
Add a Socionext SoC specific compatible (suggested by Rob Herring).
No SoC specific data are associated with the compatible strings for
now, but other SoC vendors may use this IP and want to differentiate
IP variants in the future.
Signed-off-by: Masahiro Yamada
---
Documentation/devicetree/bi
On Tue, Dec 13, 2016 at 09:27:59AM -0700, Alex Williamson wrote:
> On Tue, 13 Dec 2016 18:12:34 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Mon, Dec 12, 2016 at 08:39:48PM -0700, Alex Williamson wrote:
> > > On Tue, 13 Dec 2016 05:15:13 +0200
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > O
On Fri, Nov 25, 2016 at 6:11 PM, Benjamin Tissoires
wrote:
> The LID state provided by ACPI on the Surface 3 is not accurate.
> The ACPI node doesn't get notified on LID open, which means the
> LID input switch stays close most of the time.
>
> Fortunatelly, there is a WMI method which directly qu
On Wed, Dec 14, 2016 at 3:54 AM, Andy Shevchenko
wrote:
> On Sun, Dec 11, 2016 at 12:40 PM, Pali Rohár wrote:
>> On Thursday 08 December 2016 13:36:15 Michał Kępień wrote:
>>> All calls to dell_app_wmi_led_set() have been replaced with direct
>>> calls to dell_micmute_led_set(), so the former can
Hi Holger,
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on v4.9]
[cannot apply to ljones-mfd/for-mfd-next next-20161213]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Sun, Dec 11, 2016 at 12:40 PM, Pali Rohár wrote:
> On Thursday 08 December 2016 13:36:15 Michał Kępień wrote:
>> All calls to dell_app_wmi_led_set() have been replaced with direct
>> calls to dell_micmute_led_set(), so the former can be safely removed
>> along with its related enum.
>>
>> Signe
Hi Jacek,
On 12/13/2016 06:44 PM, Jacek Anaszewski wrote:
Could you please verify if leds-lp55xx-common.c driver
really needs a custom firmware loading fallback mechanism?
Thanks for sharing this. The lp55xx-common uses this mechanism to load
and run LED effect manually, so this could be a m
On Mon, Dec 5, 2016 at 5:10 PM, Benjamin Tissoires
wrote:
> The Surface 3 is not following the ACPI spec for PNP0C40, but nearly.
> The device is connected to a I2C device that might have some magic
> but we don't know about.
> Just create the device after the enumeration and use the declared GPIO
On Wed, Dec 14, 2016 at 08:47:55AM +0800, Boqun Feng wrote:
> On Tue, Dec 13, 2016 at 10:36:47AM -0800, Paul E. McKenney wrote:
> > On Wed, Dec 14, 2016 at 02:09:27AM +0800, Boqun Feng wrote:
> > > 2016年12月14日 上午1:17，"Mark Rutland" 写道：
> > > >
> > > > Hi,
> > > >
> > > > On Tue, Dec 13, 2016 at 10:
On Mon, Oct 31, 2016 at 9:22 AM, Vadim Pasternak wrote:
> Since mlx-platform is not an architectural driver, it is moved out
> of arch/x86/platform to drivers/platform/x86.
> Relevant Makefile and Kconfig are updated.
Pushed to testing with fixed Subject (Pattern is "platform/x86:
driver: Descrip
Am 13.12.2016 um 17:46 schrieb Thomas Gleixner:
> On Tue, 13 Dec 2016, Roland Scheidegger wrote:
>
>> Am 13.12.2016 um 14:14 schrieb Thomas Gleixner:
>>> Roland reported interesting TSC ADJUST register wreckage on his DELL
>>> machine, which seems to populate that MSR with a random number generato
On Mon, Nov 7, 2016 at 10:11 PM, Nilesh Bacchewar
wrote:
> This adds TMU (Time Management Unit) support for Intel BXT platform.
> It enables the alarm wake-up functionality in the TMU unit of Whiskey Cove
> PMIC.
>
Pushed to testing with fixed Subject (the pattern is "platform/x86:
Description")
The timer APIs this header needs are ktime_get(), ktime_add_us(),
and ktime_compare(). So, including seems enough.
This commit will cut unnecessary header file parsing.
Signed-off-by: Masahiro Yamada
---
I was not quite sure whom I should send this patch to.
I am sending this to Will Deacon be
Hi Holger,
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on v4.9]
[cannot apply to ljones-mfd/for-mfd-next next-20161213]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Tue, Dec 6, 2016 at 1:27 PM, Andrew Jeffery wrote:
> The registers for the bt-bmc device live under the Aspeed LPC
> controller. Devicetree bindings have recently been introduced for the
> LPC controller where the "host" portion of the LPC register space is
> described as a syscon device. Futur
Without a bool string present, using "# CONFIG_DEVPORT is not set" in
defconfig files would not actually unset devport. This ensured that
/dev/port was always on, but there are reasons a user may wish to disable
it (smaller kernel, attack surface reduction) if it's not being used. Adding
a message
On Tue, Dec 13, 2016 at 3:46 PM, Jeff Moyer wrote:
> Hi, Dan,
>
> In general, I have a couple of concerns with this patchset:
> 1) You're making a case that subdivision shouldn't be persistent, which
>means that all of the code we already have for subdividing devices
>(partitions, libnvdim
On Wed, Dec 14, 2016 at 02:09:27AM +0800, Boqun Feng wrote:
> 2016年12月14日 上午1:17，"Mark Rutland" 写道：
> >
> > Hi,
> >
> > On Tue, Dec 13, 2016 at 10:56:46AM +, Colin King wrote:
> > > From: Colin Ian King
> > >
> > > mask and bit are unsigned longs, so if bit is 31 we end up sign
> > > extending
On Tue, Dec 13, 2016 at 04:32:25PM -0800, Max wrote:
> From: Max Bires
>
> Without a bool string present, using "# CONFIG_DEVPORT is not set" in
> defconfig files would not actually unset devport. This ensured that
> /dev/port was always on, but there are reasons a user may wish to disable
> it (
The LCD bus width does not need to align with the pixel format. The
LCDIF controller automatically converts between pixel formats and
bus width by padding or dropping LSBs.
The DRM subsystem has the notion of bus_format which allows to
determine what bus_formats are supported by the display. Choos
On Wed, Dec 14, 2016 at 10:59:32AM +1100, Andrew Donnellan wrote:
> On 14/12/16 04:15, Greg Kroah-Hartman wrote:
> > 4.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Andrew Donnellan
> >
> > commit 409bf7f8a02ef88db5a0f2cdcf948
On Tue, Dec 13, 2016 at 11:21 AM, Catalin Marinas
wrote:
>
> Please pull the arm64 updates for 4.10 below.
Mind checking that I got the conflict resolution right?
The conflict looked completely trivial, but with stuff moving across
files and since I don't build the end result (much less boot it)
On Wed, 14 Dec 2016, Michal Marek wrote:
> Dne 8.12.2016 v 05:24 Nicolas Pitre napsal(a):
> > Rather than having an asm-prototypes.h file where C prototypes for exported
> > asm symbols are centralized, let's have some macros that can be used
> > directly in the code where those symbols are export
Apply coding style suggested by Documentation/CodingStyle
and checkpatch.pl script. Fix 59 warnings and 24 errors
reported by checkpatch.pl
Signed-off-by: Piotr Gregor
---
include/linux/kernel.h | 180 +
1 file changed, 106 insertions(+), 74 deleti
On 12/13/2016 12:52 PM, Jiri Slaby wrote:
> This is the start of the stable review cycle for the 3.12.69 release.
> There are 38 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be
On Tue, Dec 13, 2016 at 10:36:47AM -0800, Paul E. McKenney wrote:
> On Wed, Dec 14, 2016 at 02:09:27AM +0800, Boqun Feng wrote:
> > 2016年12月14日 上午1:17，"Mark Rutland" 写道：
> > >
> > > Hi,
> > >
> > > On Tue, Dec 13, 2016 at 10:56:46AM +, Colin King wrote:
> > > > From: Colin Ian King
> > > >
> >
This update includes the usual round of major driver updates (ncr5380,
lpfc, hisi_sas, megaraid_sas, ufs, ibmvscsis, mpt3sas). There's also
an assortment of minor fixes, mostly in error legs or other not very
user visible stuff. The major change is the pci_alloc_irq_vectors
replacement for the ol
Sometimes handling FUSE_FSYNC in userspace may take a while. No need
to block incoming writes while userspace processes FUSE_FSYNC.
Signed-off-by: Maxim Patlasov
---
fs/fuse/file.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index 2401c5d..9d52a8a 10
On Tue, Dec 13, 2016 at 04:27:32PM -0800, Joe Perches wrote:
> a, On Tue, 2016-12-13 at 09:19 +, Nicholas Mc Guire wrote:
> > On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> > > On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> > > > useleep_range() with a delta of 0 makes no sens
- "This functions return ..." -> "This function returns ..."
- "I you want ..." -> "If you want ..."
Signed-off-by: Masahiro Yamada
---
drivers/mtd/mtdcore.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/mtd/mtdcore.c b/drivers/mtd/mtdcore.c
index ca661ce..
From: Max Bires
Without a bool string present, using "# CONFIG_DEVPORT is not set" in
defconfig files would not actually unset devport. This ensured that
/dev/port was always on, but there are reasons a user may wish to disable
it (smaller kernel, attack surface reduction) if it's not being used.
On Tue, Dec 13, 2016 at 2:52 AM, Richard Guy Briggs wrote:
> It is actually the audit_pid and audit_nlk_portid that I care about
> more. The audit daemon could vanish or close the socket while the
> kernel sock to which it was attached is still quite valid. Accessing
> the set of three atomicall
Hi!
v1 -> v2 changes:
- use poll-interval instead of ti,poll-interval-ms in the bindings
- properly initialize the shared_lock mutex
- don't share gpios on active low/high mismatch
- don't regress users specifying the old ti,ac-detect-gpio form (without
the trailing s)
I have a board that featu
a, On Tue, 2016-12-13 at 09:19 +, Nicholas Mc Guire wrote:
> On Tue, Dec 13, 2016 at 11:10:50AM +0200, Jani Nikula wrote:
> > On Tue, 13 Dec 2016, Nicholas Mc Guire wrote:
> > > useleep_range() with a delta of 0 makes no sense and only prevents the
> > > timer subsystem from optimizing interru
Many jhash users currently rely on the Nwords functions. In order to
make transitions to siphash fit something people already know about, we
provide analog functions here. This also winds up being nice for the
networking stack, where hashing 32-bit fields is common.
Signed-off-by: Jason A. Donenfe
On 12/12, Imran Khan wrote:
> The SoC info driver provides information such as Chip ID,
> Chip family, serial number and other such details about
> Qualcomm SoCs.
Yes but why do we care?
>
> Signed-off-by: Imran Khan
>
>
> drivers/soc/qcom/Kconfig | 1 +
> drivers/soc/qcom/Makefile |
SipHash is a 64-bit keyed hash function that is actually a
cryptographically secure PRF, like HMAC. Except SipHash is super fast,
and is meant to be used as a hashtable keyed lookup function.
SipHash isn't just some new trendy hash function. It's been around for a
while, and there really isn't any
On Tue, Dec 13, 2016 at 7:03 AM, Richard Guy Briggs wrote:
> @@ -1283,8 +1299,10 @@ static void __net_exit audit_net_exit(struct net *net)
> {
> struct audit_net *aunet = net_generic(net, audit_net_id);
> struct sock *sock = aunet->nlsk;
> + mutex_lock(&audit_cmd_mutex);
>
This gives a clear speed and security improvement. Rather than manually
filling MD5 buffers, we simply create a layout by a simple anonymous
struct, for which gcc generates rather efficient code.
Signed-off-by: Jason A. Donenfeld
---
net/core/secure_seq.c | 153 --
The Eberspaecher Flexcard PMC II is a PMC (PCI Mezzanine Card) II
carrier board. The carrier board can take up to 4 exchangeable physical
layer boards for CAN, FlexRay or Ethernet.
This patchset adds support for the common infrastructure of the carrier
board.
This patch series apply on v4.9.
Fir
On 10/12/16 00:32, Gautham R. Shenoy wrote:
> From: "Gautham R. Shenoy"
>
> The power9_idle_stop method currently takes only the requested stop
> level as a parameter and picks up the rest of the PSSCR bits from a
> hand-coded macro. This is not a very flexible design, especially when
> the fir
The Flexcard comprise an interrupt controller for the attached
tinys, timer, a Flexray related trigger and a second one for DMA.
Both controllers share a single IRQ line.
Add the DMA Controller interrupts.
Signed-off-by: Benedikt Spranger
Signed-off-by: Holger Dengler
cc: Lee Jones
---
driver
Add an UIO device for each Flexcard Flexray related trigger. The trigger
devide into:
- Flexray cycle start (CCYS)
- Flexray timer 0 (CCxT0)
- Bus wakeup (WAKE)
The UIO IRQ devices can be used to synchronize an application
with these events.
Signed-off-by: Benedikt Spranger
Signed-off-by: Hol
The Flexcard timestamp counter can be triggered from two external
trigger inputs or an internal clock at 1 MHz, 10 Mhz or 100 MHz.
Add support for timestamp trigger selection.
Signed-off-by: Holger Dengler
Signed-off-by: Benedikt Spranger
cc: Arnd Bergmann
cc: Greg Kroah-Hartman
---
drivers/m
The Flexcard PCI BAR0 contain registers for configuration but also
for informational purpose like error counter, statistical information
and some timestamps. The read-only mmap of the misc device offers the
userspace a fast access to these registers.
Signed-off-by: Benedikt Spranger
Signed-off-by
The Flexcard interface design split packet receive and transmit. All
received packets and card status information are multiplexed with a
Flexcard specific protocol and handled through a DMA capable ringbuffer.
The TX path has to poke each available component separate.
Add a Flexcard DMA ringbuffer
The Flexcard comprise an interrupt controller for the attached
tinys, timer, a Flexray related trigger and a second one for DMA.
Both controllers share a single IRQ line.
Add an interrupt domain for the non-DMA interrupts.
Signed-off-by: Benedikt Spranger
Signed-off-by: Holger Dengler
cc: Lee J
The Eberspaecher Flexcard PMC II offers a Flexray network synchronized
counter with a selectable resolution of 1us, 100ns or 10ns. Add basic
support for the timestamp counter with 1us resolution, which is the
standard Flexray bus resolution.
Signed-off-by: Benedikt Spranger
Signed-off-by: Holger
The Flexcard interface design split packet receive and transmit. All
received packets and card status information are multiplexed with a
Flexcard specific protocol and handled through a DMA capable ringbuffer.
The TX path has to poke each available component separate.
Add a platform device for the
The Eberspaecher Flexcard PMC II is a PMC (PCI Mezzanine Card) II
carrier board. The carrier board can take up to 4 exchangeable physical
layer boards for e.g. CAN, FlexRay or Ethernet.
Signed-off-by: Benedikt Spranger
Signed-off-by: Holger Dengler
cc: Lee Jones
---
drivers/mfd/Kconfig
The Flexcard offers a Flexray network synchronized counter with a
selectable resolution of 1us, 100ns or 10ns. Add an appropriate MFD-cell
to use the counter.
Signed-off-by: Benedikt Spranger
Signed-off-by: Holger Dengler
cc: Lee Jones
---
drivers/mfd/flexcard_core.c | 40 +
The Flexcard PCI BAR0 contain registers for configuration and
informational purpose. Add an appropriate MFD-cell for these registers.
Signed-off-by: Benedikt Spranger
Signed-off-by: Holger Dengler
cc: Lee Jones
---
drivers/mfd/flexcard_core.c | 58 +++-
During a "perf buildid-cache --add" command, the section
".note.stapsdt" of the "added" binary is scanned in order to list the
available SDT markers available in a binary. The parts containing the
probes arguments were left unscanned.
The whole section is now parsed; the probe arguments are extrac
If several parallel bq24735 chargers have their ac-detect gpios wired
together (or if only one of the parallel bq24735 chargers have its
ac-detect pin wired to a gpio, and the others are assumed to react the
same), then all driver instances need to check the same gpio. But the
gpio subsystem does n
Add device attributes for common flexcard information access. The
attribiutes are read-only execpt "uid" (user ID register).
The "uid" attribute can also be used to change the user-defined ID of a
Flexcard.
Signed-off-by: Benedikt Spranger
Signed-off-by: Holger Dengler
cc: Arnd Bergmann
cc: Gre
An sdt probe can be associated with arguments but they were not passed
to the user probe tracing interface (uprobe_events); this patch adapts
the sdt argument descriptors according to the uprobe input format.
As the uprobe parser does not support scaled address mode, perf will
skip arguments which
If the ac-detect gpio does not support interrupts, provide a fallback
to poll the gpio at a configurable interval.
Signed-off-by: Peter Rosin
---
.../bindings/power/supply/ti,bq24735.txt | 2 +
drivers/power/supply/bq24735-charger.c | 50 +++---
2 files cha
Hi Masami,
Many thanks for your mail.
Here is another patch set which tries to fix the points you mentioned:
* Skip the arguments containing a constant ($123);
* Review the code in charge of the register renaming (search for '%'
and parse it);
* Minor changes (print the argument in case of er
On 2016-12-08 15:38, Marek Vasut wrote:
> On 12/08/2016 09:46 PM, Stefan Agner wrote:
>> On 2016-12-07 18:37, Marek Vasut wrote:
>>> On 12/08/2016 02:26 AM, Stefan Agner wrote:
On 2016-12-07 16:59, Stefan Agner wrote:
> On 2016-12-07 16:49, Marek Vasut wrote:
>> On 12/08/2016 01:27 AM,
On Tue, Dec 13, 2016 at 02:42:18PM -0800, Max Bires wrote:
> On Tue, Dec 13, 2016 at 1:37 PM, Arnd Bergmann wrote:
> >
> > On Tuesday, December 13, 2016 1:30:39 PM CET Max Bires wrote:
> > > While trying to turn off the port device in defconfig, I ran into a bug
> > > caused by the fact that the K
Dear RT Folks,
I'm pleased to announce the 4.1.36-rt42 stable release.
This release is just an update to the new stable 4.1.36 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.g
On 2016-12-08 20:24, Marek Vasut wrote:
> On 12/09/2016 04:44 AM, Stefan Agner wrote:
>> On 2016-12-08 15:33, Marek Vasut wrote:
>>> On 12/08/2016 11:52 PM, Stefan Agner wrote:
The LCD bus width does not need to align with the pixel format. The
LCDIF controller automatically converts betw
Dear RT Folks,
I'm pleased to announce the 3.12.68-rt91 stable release.
This release is just an update to the new stable 3.12.68 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt
Dear RT Folks,
I'm pleased to announce the 3.2.84-rt122 stable release.
This release is just an update to the new stable 3.2.84 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.
Dear RT Folks,
I'm pleased to announce the 3.18.45-rt49 stable release.
This release is just an update to the new stable 3.18.45 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt
Dear RT Folks,
I'm pleased to announce the 4.4.38-rt49 stable release.
This release is just an update to the new stable 4.4.38 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.g
On Tue, Dec 13, 2016 at 03:42:58PM -0800, Mark Salyzyn wrote:
> On 12/12/2016 10:26 PM, Cong Wang wrote:
> > On Mon, Dec 12, 2016 at 4:26 PM, Mark Salyzyn wrote:
> > > The leaks were introduced in 9p, gfs2, jfs and xfs drivers only.
> >
> > Only the 9p case is obvious to me:
> >
> > diff --git a
On 14/12/16 04:15, Greg Kroah-Hartman wrote:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andrew Donnellan
commit 409bf7f8a02ef88db5a0f2cdcf9489914f4b8508 upstream.
In eeh_reset_device(), we take the pci_rescan_remove_lock immediately a
Hi!
On 17/11/16 12:43, Sriram Dash wrote:
> From: Arnd Bergmann
>
> The dma ops for dwc3 devices are not set properly. So, use a
> physical device sysdev, which will be inherited from parent,
> to set the hardware / firmware parameters like dma.
>
> Signed-off-by: Arnd Bergmann
> Signed-off-by
On Tue, Dec 13, 2016 at 3:28 AM, Jan Kara wrote:
> On Mon 12-12-16 22:26:09, Cong Wang wrote:
>> On Mon, Dec 12, 2016 at 4:26 PM, Mark Salyzyn wrote:
>> >
>> > The leaks were introduced in 9p, gfs2, jfs and xfs drivers only.
>>
>>
>> Only the 9p case is obvious to me:
>
> Agreed and the patch bel
On Tue, 13 Dec 2016 16:20:59 +0100
Dmitry Vyukov wrote:
> Now that we have gcc plugins and in particular sancov plugin,
> KCOV can be used with gcc 4.5+. Note this in the docs.
Makes sense. Applied to docs-next, thanks.
jon
Since the new API slightly changes the way a typical NTB client driver
works, the documentation file needs to be appropriately updated.
Acked-by: Allen Hubbe
Signed-off-by: Serge Semin
---
Documentation/ntb.txt | 99 ++-
1 file changed, 91 inserti
Some IDT NTB-capable PCIe-switches have message registers to communicate with
peer devices. This patch adds new NTB API callback methods, which can be used
to utilize these registers functionality:
ntb_msg_count(); - get number of message registers
ntb_msg_inbits(); - get bitfield of inbound mess
Signed-off-by: Serge Semin
---
include/linux/ntb.h | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/include/linux/ntb.h b/include/linux/ntb.h
index 6d46179..dab0a1b 100644
--- a/include/linux/ntb.h
+++ b/include/linux/ntb.h
@@ -326,12 +326,17 @@ static inli
There is some NTB hardware, which can combine more than just two domains
over NTB. For instance, some IDT PCIe-switches can have NTB-functions
activated on more than two-ports. The different domains are distinguished
by ports they are connected to. So the new port-related methods are added to
the N
Acked-by: Allen Hubbe
Signed-off-by: Serge Semin
---
include/linux/ntb.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/ntb.h b/include/linux/ntb.h
index 76c56d5..6d46179 100644
--- a/include/linux/ntb.h
+++ b/include/linux/ntb.h
@@ -108,6 +108,7 @@ static inline char *ntb_t
There are devices, like IDT PCIe-switches, which have more than just two ports.
Particularly one device can have up to eight ports with NTB-function activated.
In order to support such devices, NTB kernel API should be altered since
currently it's optimized to work with two-ports devices only.
Cha
Since link operations are usually performed before memory window access
operations, it's logically better to declare link-related API before any
of MW/Doorbell/Scratchpad methods.
Signed-off-by: Serge Semin
---
include/linux/ntb.h | 137 ++--
1 fil
Multi-port NTB devices permit to share a memory between all accessible peers.
Memory Windows API is altered to correspondingly initialize and map memory
windows for such devices:
ntb_mw_count(pidx); - number of inbound memory windows, which can be allocated
for shared buffer with specified peer de
Multi-port devices permit the NTB connections between multiple domains,
so a local device can have NTB link being up with one peer and being
down with another. NTB link-state API is appropriately altered to return
a bitfield of the link-states between the local device and possible peers.
Acked-by:
Even though there is no any real NTB hardware, which would have both more
than two ports and Scratchpad registers, it is logically correct to have
Scratchpad API accepting a peer port index as well. Intel/AMD drivers utilize
Primary and Secondary topology to split Scratchpad between connected root
Hi, Dan,
In general, I have a couple of concerns with this patchset:
1) You're making a case that subdivision shouldn't be persistent, which
means that all of the code we already have for subdividing devices
(partitions, libnvdimm) has to be re-invented in userspace, and
existing tools ca
On 12/12/2016 10:26 PM, Cong Wang wrote:
On Mon, Dec 12, 2016 at 4:26 PM, Mark Salyzyn wrote:
The leaks were introduced in 9p, gfs2, jfs and xfs drivers only.
Only the 9p case is obvious to me:
diff --git a/fs/9p/acl.c b/fs/9p/acl.c
index b3c2cc7..082d227 100644
--- a/fs/9p/acl.c
+++ b/fs/9p
On Tue, 13 Dec 2016 15:40:57 +0100
Hans Holmberg wrote:
> A bunch of documentation files have moved, correct the paths.
Good catch. Guess I'm as good a messenger as anybody else for this one;
applied to docs-next, thanks.
jon
Dne 11.12.2016 v 02:09 Adam Borowski napsal(a):
> Commit 4efca4ed ("kbuild: modversions for EXPORT_SYMBOL() for asm") adds
> modversion support for symbols exported from asm files. Architectures
> must include C-style declarations for those symbols in asm/asm-prototypes.h
> in order for them to be
Hi Linus,
On Tue, Dec 13, 2016 at 8:25 PM, Linus Torvalds
wrote:
> Yeah,. the TCP sequence number md5_transform() cases are likely the
> best example of something where siphash might be good. That tends to
> be really just a couple words of data (the address and port info) plus
> the net_secret[]
Hi Linus,
On Sun, 11 Dec 2016 18:52:29 -0700 Jens Axboe wrote:
>
> Note that this pull will throw 3 trivial merge conflicts, since we had
> patches that went into mainline after 4.9-rc1 (upon which this branch is
> based), and one that will not show up in block/blk-flush.c. The latter
> is due to
Dne 8.12.2016 v 05:24 Nicolas Pitre napsal(a):
> Rather than having an asm-prototypes.h file where C prototypes for exported
> asm symbols are centralized, let's have some macros that can be used
> directly in the code where those symbols are exported for genksyms
> consumption. Either the prototy
David Arendt posted on Tue, 13 Dec 2016 21:26:04 +0100 as excerpted:
> The crash is not an isolated one as I already had this crash multiple
> times with -rc7 and -rc8. It seems only to occur when copying from
> 7200rpm harddisks to 5600rpm ones, and never when copying between two
> 7200rpm or two
On 12/13, Andy Shevchenko wrote:
> On Fri, Dec 9, 2016 at 8:01 PM, Irina Tirdea wrote:
>
> > --- a/drivers/clk/x86/Makefile
> > +++ b/drivers/clk/x86/Makefile
> > @@ -1,2 +1,5 @@
> > clk-x86-lpss-objs := clk-lpt.o
> > obj-$(CONFIG_X86_INTEL_LPSS) += clk-x86-lpss.o
>
> > +ifeq ($
rproc_del() waits on firmware_loading_complete in order to
make sure rproc_add() completed successfully before calling
rproc_shutdown(). However since rproc_add() will always be
called before rproc_del(), we do not need to wait on
firmware_loading_complete. Drop this completion variable
altogether
Hi Linus,
On Tue, 13 Dec 2016 19:21:59 + Catalin Marinas
wrote:
>
> Please pull the arm64 updates for 4.10 below.
>
> The patches touch the generic include/linux/thread_info.h to factor out
> struct restart_block into a separate include/linux/restart_block.h file
> (needed for arm64 moving
On 12/13, Nikita Yushchenko wrote:
> >> diff --git a/drivers/clk/imx/clk-pllv3.c b/drivers/clk/imx/clk-pllv3.c
> >> index 19f9b622981a..24a9e914e0d5 100644
> >> --- a/drivers/clk/imx/clk-pllv3.c
> >> +++ b/drivers/clk/imx/clk-pllv3.c
>
> >> +
> >> + temp64 *= mfn;
> >> + do_div(temp64, mfd);
> >
101 - 200 of 907 matches
Mail list logo
