On Wed 2016-03-23 10:24:43, Sergey Senozhatsky wrote:
> On (03/22/16 17:36), Petr Mladek wrote:
> > > - /* cpu currently holding logbuf_lock in this function */
> > > - static unsigned int logbuf_cpu = UINT_MAX;
> > > + bool in_panic = console_loglevel == CONSOLE_LOGLEVEL_MOTORMOUTH;
> >
> > I am
Flags should be saved in the same format in which clri instruction saves
them since they are passed directly to seti instruction over
arch_local_save_flags/arch_local_irq_restore calls.
Trace of all clri/seti assembly calls is added to support locking
correctness validator properly.
With this
On 2016/3/23 17:16, Peter Zijlstra wrote:
On Mon, Mar 14, 2016 at 09:59:41AM +, Wang Nan wrote:
Add new ioctl() to pause/resume ring-buffer output.
In some situations we want to read from ring buffer only when we
ensure nothing can write to the ring buffer during reading. Without
this
Hanjun Guo has reported that a CMA stress test causes broken accounting of
CMA and free pages:
> Before the test, I got:
> -bash-4.3# cat /proc/meminfo | grep Cma
> CmaTotal: 204800 kB
> CmaFree: 195044 kB
>
>
> After running the test:
> -bash-4.3# cat /proc/meminfo | grep Cma
>
On Wednesday 23 March 2016 09:48:42, Alexander Stein wrote:
> I'm currently trying to get PCIe working on LS1021A (little-endian ARM). For
> link-detection I need access to a syscon perpheral (SCFG) which is attched to
> CPU as big-endian.
> The corresponding DT part is:
>
> scfg:
On Mon, Mar 14, 2016 at 09:59:43AM +, Wang Nan wrote:
> Convert perf_output_begin to __perf_output_begin and make the later
> function able to write records from the end of the ring buffer.
> Following commits will utilize the 'backward' flag.
>
> This patch doesn't introduce any extra
On Wed, Mar 23, 2016 at 05:33:53PM +0800, Wangnan (F) wrote:
> Glad to see you start to look at this patchset.
My brain is completely fried from staring at fuzzer output for weeks, I
just need to do _something_, _anything_ else for a while :-)
When the battery is dry and BATTERY_FULL_DISCHARGED is set,
we should check BATTERY_DISCHARGING to decide the power status.
If BATTERY_DISCHARGING is set, the power status is not charging.
Or the power status should be charging.
Signed-off-by: YH Huang
---
drivers/power/sbs-battery.c | 22
On 2016/03/23 at 16:23, Baoquan He wrote:
> On 03/23/16 at 11:32am, Xunlei Pang wrote:
>> On 2016/03/23 at 10:48, Baoquan He wrote:
>>> On 03/01/16 at 05:53pm, Xunlei Pang wrote:
This is a bug fix.
After this, I will try to do a cleanup for crash_unmap/map_reserved_pages()
As ping_v6_sendmsg is used only in this file,
making it static
The body of "pingv6_prot" and "pingv6_protosw" were
moved at the middle of the file, to avoid having to
declare some static prototypes.
Signed-off-by: Haishuang Yan
---
include/net/ping.h | 1 -
net/ipv6/ping.c| 59
On Wed 2016-03-23 09:37:25, Sergey Senozhatsky wrote:
> Hello Petr,
>
> On (03/22/16 14:11), Petr Mladek wrote:
> > > + * Set printing_func() sleep condition early, under the @logbuf_lock.
> > > + * So printing kthread (if RUNNING) will go to console_lock() and spin
> > > + * on @logbuf_lock.
On Mon, Mar 14, 2016 at 09:59:45AM +, Wang Nan wrote:
> By creating onward and backward specific overflow handlers and setting
> them according to event's backward setting, normal sampling events
> don't need checking backward setting of an event any more.
The normal antonym of backward is
On 2016/3/23 17:50, Peter Zijlstra wrote:
On Mon, Mar 14, 2016 at 09:59:43AM +, Wang Nan wrote:
Convert perf_output_begin to __perf_output_begin and make the later
function able to write records from the end of the ring buffer.
Following commits will utilize the 'backward' flag.
This
On Wed, Mar 23, 2016 at 12:22:23PM +0530, Aneesh Kumar K.V wrote:
> Jérôme Glisse writes:
>
> > [ text/plain ]
> > This patch add helper for device page fault. Thus helpers will fill
> > the mirror page table using the CPU page table and synchronizing
> > with any update to CPU page table.
> >
>
Hi Uwe,
On 03/22/2016 08:42 PM, Uwe Kleine-König wrote:
> Hello Sebastian,
>
> On Tue, Mar 22, 2016 at 03:34:23PM +0100, Sebastian Frias wrote:
>> I think we are in a deadlock :-)
>> I'm going to reply inline below, but I will also send a different email
>> to Daniel with a small recap.
>> I
Drivers that define PSEUDO_DMA also define NCR5380_dma_xfer_len.
The core driver must call NCR5380_dma_xfer_len which means
FLAG_NO_PSEUDO_DMA can be eradicated from the core driver.
dmx3191d doesn't define PSEUDO_DMA and has no use for FLAG_NO_PSEUDO_DMA,
so remove it there also.
Signed-off-by:
Only the atari_scsi and sun3_scsi drivers define DMA_MIN_SIZE.
Both drivers also define NCR5380_dma_xfer_len, which means
DMA_MIN_SIZE can be removed from the core driver.
This removes another discrepancy between the two core drivers.
Signed-off-by: Finn Thain
Tested-by: Michael Schmitz
The dmx3191d driver is not capable of DMA or PDMA so all transfers
use PIO. Now that large slow PIO transfers periodically stop and call
cond_resched(), the max_sectors limit can go away.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
drivers/scsi/dmx3191d.c |1 -
1 file
This setting does not need to be conditional on Atari ST or TT.
Signed-off-by: Finn Thain
Tested-by: Michael Schmitz
Reviewed-by: Hannes Reinecke
---
Changed since v1:
- Set the default cmd_per_lun to 4 based on test results.
Changed since v2:
- Revert the default cmd_per_lun to 2, like in
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
Tested-by: Michael Schmitz
Tested-by: Ondrej Zary
---
drivers/scsi/NCR5380.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Index: linux/drivers/scsi/NCR5380.c
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
Tested-by: Michael Schmitz
Tested-by: Ondrej Zary
---
drivers/scsi/NCR5380.c | 12 +---
drivers/scsi/NCR5380.h |4
drivers/scsi/arm/oak.c |2 --
drivers/scsi/dmx3191d.c |2 --
drivers/scsi/dtc.c |
Now that atari_scsi and sun3_scsi have been converted to use the NCR5380.c
core driver, remove atari_NCR5380.c. Also remove the last vestiges of its
Tagged Command Queueing implementation from the wrapper drivers.
The TCQ support in atari_NCR5380.c is abandoned by this patch. It is not
merged
Fix various issues: Comments about bus errors are incorrect. The
PDMA asm must return the size of the memory access that faulted so the
transfer count can be adjusted accordingly. A phase change may cause a
bus error but should not be treated as failure. A bus error does not
always imply a phase
On Wed, Mar 23, 2016 at 11:12:41AM +0800, Kefeng Wang wrote:
> If no pci, the PCI I/O space(16M) is mapped into an irrelevant mem
> space(right ?),
No. It is not mapped at all.
> not a right IO space,
> that is, no one call pci_remap_iospace() to remap the memory mapped I/O
> space, once
Decode all bits in the chip registers. They are all useful at times.
Fix printk severity so that this output can be suppressed along with
the other debugging output.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
Tested-by: Michael Schmitz
Tested-by: Ondrej Zary
---
Add support for the custom Sun 3 DMA logic to the NCR5380.c core driver.
This code is copied from atari_NCR5380.c.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
Tested-by: Michael Schmitz
Tested-by: Ondrej Zary
---
The Sun 3 DMA code is still configured by macros. I have simplified
The driver has a limit of eight LUs because of the byte-sized bitfield
that is used for busy flags. That means the maximum LUN is 7. The default
is 8.
Signed-off-by: Finn Thain
Tested-by: Michael Schmitz
Tested-by: Ondrej Zary
Reviewed-by: Hannes Reinecke
---
Changed since v1:
- Reduce
On 22/03/2016 20:42, Uwe Kleine-König wrote:
> Preconditions:
> - Some of the devices a given driver handles have a reset line and
>others don't.
> - A non-empty subset (maybe all) of the devices that have a reset line
>require that this reset line is used.
>
> Then the way to handle
This patch series has more macro elimination and some tweaks to the
DMA hooks so that all the wrapper drivers can share the same core
DMA algorithm. This resolves the major discrepancies between the two
core drivers, which relate to code conditional on the REAL_DMA and
PSEUDO_DMA macros.
After
I'm told that some targets are liable to disconnect a REQUEST SENSE
command. Theoretically this would cause a command undergoing autosense to
be moved onto the disconnected list. The bus reset handler must call
complete_cmd() for these commands, otherwise the hostdata->sensing pointer
will not get
Add support for the Atari ST DMA chip to the NCR5380.c core driver.
This code is copied from atari_NCR5380.c.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
Tested-by: Michael Schmitz
Tested-by: Ondrej Zary
---
drivers/scsi/NCR5380.c| 32
Update kernel parameter documentation for atari_scsi, mac_scsi and
g_NCR5380 drivers. Remove duplication.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
Documentation/scsi/g_NCR5380.txt | 17 ++-
Documentation/scsi/scsi-parameters.txt | 11 +++---
The benefit of limiting can_queue to 1 is that atari_scsi shares the
ST DMA chip more fairly with other drivers (e.g. falcon-ide).
Unfortunately, this can limit SCSI bus utilization. On systems without
IDE, atari_scsi should issue SCSI commands whenever it can arbitrate for
the bus. Make that
For the NCR5380.c core driver, these macros are never used.
If REAL_DMA were to be defined, compilation would fail.
For the atari_NCR5380.c core driver, REAL_DMA is always defined.
Hence these macros are pointless.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
Tested-by: Michael
Standardize the DMA setup hooks so that the DMA implementation in
atari_NCR5380.c can be reconciled with pseudo DMA implementation in
NCR5380.c.
Calls to NCR5380_dma_recv_setup() and NCR5380_dma_send_setup() return
a negative value on failure, zero on PDMA transfer success and a positive
byte
Those wrapper drivers which use DMA define the REAL_DMA macro and
those which use pseudo DMA define PSEUDO_DMA. These macros need to be
removed for a number of reasons, not least of which is to have drivers
share more code.
Redefine the PDMA send and receive hooks as DMA setup hooks, so that the
The io_recovery_delay macro is intended to insert a microsecond delay
between the chip register accesses that begin a DMA operation. This
is reportedly needed for some ISA boards.
Reverse the sense of the macro test so that in the common case,
where no delay is required, drivers need not define
Adopt the DMA implementation from atari_NCR5380.c. This means that
atari_scsi and sun3_scsi can make use of the NCR5380.c core driver
and the atari_NCR5380.c driver fork can be made redundant.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
Tested-by: Michael Schmitz
Tested-by: Ondrej
For those wrapper drivers which only implement Programmed IO, have
NCR5380_dma_xfer_len() evaluate to zero. That allows PDMA to be easily
disabled at run-time and so the PSEUDO_DMA macro is no longer needed.
Also remove the spin counters used for debugging pseudo DMA drivers.
Signed-off-by: Finn
The only chip that needs the workarounds enabled is an early NMOS
device. That means that the common case is to disable them.
Unfortunately the sense of the flag is such that it has to be set
for the common case.
Rename the flag so that zero can be used to mean "no errata workarounds
needed".
This change brings a number of improvements: fewer macros, better test
coverage, simpler code and sane Kconfig options. The downside is a small
chance of incompatibility (which seems unavoidable).
CONFIG_SCSI_GENERIC_NCR53C400 exists to enable or inhibit pseudo DMA
transfers when the driver is
Hi Jayachandran
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Jayachandran C
> Sent: 18 March 2016 17:48
> To: Bjorn Helgaas; Tomasz Nowicki; raf...@kernel.org
> Cc: Jayachandran C; Arnd Bergmann; Will Deacon;
On Tue, Mar 22, 2016 at 10:31:45PM +0800, Jisheng Zhang wrote:
> psci_power_state_loses_context() and psci_power_state_is_valid are only
> used internally now, so make them static.
>
> Signed-off-by: Jisheng Zhang
> ---
> drivers/firmware/psci.c | 4 ++--
> include/linux/psci.h| 2 --
> 2
Jerome Glisse writes:
> [ text/plain ]
> On Wed, Mar 23, 2016 at 12:22:23PM +0530, Aneesh Kumar K.V wrote:
>> Jérôme Glisse writes:
>>
>> > [ text/plain ]
>> > This patch add helper for device page fault. Thus helpers will fill
>> > the mirror page table using the CPU page table and
A couple of data structures in the dibusb-common file are only
accessed when CONFIG_DVB_DIB3000MC is enabled, otherwise we
get a harmless gcc warning:
usb/dvb-usb/dibusb-common.c:223:34: error: 'dib3000p_panasonic_agc_config'
defined but not used
usb/dvb-usb/dibusb-common.c:211:32: error:
On Wed, Mar 23, 2016 at 09:48:42AM +0100, Alexander Stein wrote:
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
> I'm currently trying to get PCIe working on LS1021A
gcc finds that the i40iw_make_cm_node() function in the recently added
i40iw driver uses an uninitilized variable as an index into an array
if CONFIG_IPV6 is disabled and the driver uses IPv6 mode:
drivers/infiniband/hw/i40iw/i40iw_cm.c: In function 'i40iw_make_cm_node':
The syscon header uses the ENOTSUPP error constant, but doesn't
include the header that defines it. This causes a build error
after the imx pinctrl driver started using syscon:
include/linux/mfd/syscon.h: In function 'syscon_node_to_regmap':
include/linux/mfd/syscon.h:32:18: error: 'ENOTSUPP'
On Wed, Mar 23, 2016 at 11:42:53AM +0300, Alexey Brodkin wrote:
> As a pair to already existing drm_connector_unplug_all()
> (which we'll rename in this series to drm_connector_unregister_all())
> we're adding generic implementation of what is already done in some drivers
> for registering all
On 22/03/16 20:23, Mathieu Poirier wrote:
In their current implementation the tmc_read_prepare/unprepare()
are a lump of if/else that is difficult to read. This patch is
alleviating that by using a switch statement. The latter also
allows for a better control on the error path.
Signed-off-by:
On 22/03/16 20:23, Mathieu Poirier wrote:
According to the TMC architectural state machine, the 'stopped'
state is reached when bit 2 (TMCReady) of the TMC Status register
turns to '1'. The code is correct but the naming convention isn't.
The 'Triggered' bit occupies position '1' of the TMC
The previous patch that added a couple of callback functions put
the declarations inside of an #ifdef CONFIG_INFINIBAND_ON_DEMAND_PAGING,
which causes the build to fail if that option is disabled:
drivers/infiniband/hw/mlx5/main.c: In function 'mlx5_ib_add':
Hello.
On 3/23/2016 1:17 PM, Mason wrote:
Preconditions:
- Some of the devices a given driver handles have a reset line and
others don't.
- A non-empty subset (maybe all) of the devices that have a reset line
require that this reset line is used.
Then the way to handle this in the
gcc-6.0 warns about comparisons between two identical expressions,
which is what we get in the floppy driver when writing to the FD_DOR
register:
drivers/block/floppy.c: In function 'set_dor':
drivers/block/floppy.c:810:44: error: self-comparison always evaluates to true
Am 06.03.2016 um 12:21 schrieb Andreas Färber:
> Split off the bulk of the existing meson_serial_console_write()
> implementation into meson_serial_port_write() for implementing
> meson_serial_early_console_write().
>
> Use "meson" as the earlycon driver name, courtesy of Nicolas.
>
>
On Tue 22-03-16 22:23:52, Peter Zijlstra wrote:
[...]
> Probably. However, with such semantics the schedule*() name is wrong
> too, you cannot use these functions to build actual wait loops etc.
>
> So maybe:
>
> static inline long sleep_in_state(long timeout, long state)
> {
>
This removes the dependency on GPIOLIB for non faulty PHYs.
Indeed, without this patch, if GPIOLIB is not selected
devm_gpiod_get_optional() will return -ENOSYS and the driver probe
call will fail, regardless of the actual PHY hardware.
Out of the 3 PHYs supported by this driver (AT8030, AT8031,
The zero-length file "ni_mio_c_common.c" was inadvertantly created by
commit e563637b5fef ("staging: comedi: Use ARRAY_SIZE for sizes of
arrays"). Remove it.
Signed-off-by: Ian Abbott
---
drivers/staging/comedi/drivers/ni_mio_c_common.c | 0
1 file changed, 0 insertions(+), 0 deletions(-)
Hi Sergei,
On 03/23/2016 11:39 AM, Sergei Shtylyov wrote:
>> gpiod_reset = devm_gpiod_get_optional(dev, "reset",
>> GPIOD_OUT_HIGH);
>
>We shouldn't call _optional() then, should we?
I could imagine the original intention was to be backward compatible.
Indeed, if this call is not
On Wed, Mar 23, 2016 at 11:37:45AM +0100, Arnd Bergmann wrote:
> The previous patch that added a couple of callback functions put
> the declarations inside of an #ifdef CONFIG_INFINIBAND_ON_DEMAND_PAGING,
> which causes the build to fail if that option is disabled:
>
>
On Wed, Mar 16, 2016 at 03:34:30PM +0100, Jiri Olsa wrote:
> We suppress events with attr::exclude_kernel set when
> the event is generated, so following capture will
> give no warning but won't produce any data:
>
> $ sudo perf record -e sched:sched_switch:u ls
> $ sudo /perf script | wc -l
Hi Alexander,
Thanks for your test.
Number 134742016 is calculated by the following code
/**
* pci_msi_domain_calc_hwirq - Generate a unique ID for an MSI source
* @dev:Pointer to the PCI device
* @desc: Pointer to the msi descriptor
*
* The ID number is only used within the
Fix following sparse warning:
warning: cast to restricted __be16
Signed-off-by: Ksenija Stanojevic
---
drivers/staging/iio/adc/ad7606_spi.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/iio/adc/ad7606_spi.c
b/drivers/staging/iio/adc/ad7606_spi.c
index
Commit-ID: dd17a3c40d46adea7215cad3f8fa0afb7c616290
Gitweb: http://git.kernel.org/tip/dd17a3c40d46adea7215cad3f8fa0afb7c616290
Author: MaJun
AuthorDate: Wed, 23 Mar 2016 17:06:32 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 23 Mar 2016 12:02:29 +0100
ARM64: Kconfig: Select mbigen
Commit-ID: 9a7c4abd41c0d553f4fb9845bdd4328155426ac7
Gitweb: http://git.kernel.org/tip/9a7c4abd41c0d553f4fb9845bdd4328155426ac7
Author: MaJun
AuthorDate: Wed, 23 Mar 2016 17:06:33 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 23 Mar 2016 12:02:29 +0100
irqchip/mbigen: Make
On 23/03/16 09:18, Alexander Stein wrote:
> On Monday 07 March 2016 11:36:22, Minghuan Lian wrote:
>> Some kind of NXP Layerscape SoC provides a MSI
>> implementation which uses two SCFG registers MSIIR and
>> MSIR to support 32 MSI interrupts for each PCIe controller.
>> The patch is to support
Document the devicetree bindings for the clock driver found on Microchip
PIC32 class devices.
Signed-off-by: Purna Chandra Mandal
Acked-by: Rob Herring
Acked-by: Michael Turquette
Note: Please pull this complete series through the MIPS tree.
---
Changes in v10: None
Changes in v9: None
This clock driver implements PIC32 specific clock-tree. clock-tree
entities can only be configured through device-tree file (OF).
Signed-off-by: Purna Chandra Mandal
Note: Please pull this complete series through the MIPS tree.
---
Changes in v10:
- drop early clock init of
Clock bindings got acked and then essentially unacked, while the clock
driver never made it upstream. In the meantime, the initial DTS file
made it upstream. This latest patch series includes a patch to go back
and correct the DTS files to reflect the new clock bindings in this
patch series.
- now clock nodes definition is merged with core .dtsi file
- only one rootclk is now part of DT
- clock clients also updated based on new binding doc
Signed-off-by: Purna Chandra Mandal
Note: Please pull this complete series through the MIPS tree.
---
Changes in v10: None
Changes in v9: None
From: Sylwester Nawrocki
There is no need to support access to the PMU through memory ioresource
as now access through PMU regmap should only be used.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Marek Szyprowski
---
drivers/phy/phy-exynos-mipi-video.c | 57
Hello,
This patch series adds upport for MIPI Video DPHY found in Exynos
5420/5422/5800 and 5433 SoCs.
Best regards
Marek Szyprowski
Samsung R Institute Poland
Patch summary:
Marek Szyprowski (2):
phy: exynos-mipi-video: rewrite handling of phy registers
phy: exynos-mipi-video: add
This patch adds support for MIPI DPHYs found in Exynos5420-compatible
(5420, 5422 and 5800) and Exynos5433 SoCs. Those SoCs differs from
earlier by different offset of MIPI DPHY registers in PMU controllers
(Exynos 5420-compatible case) or by moving MIPI DPHY reset registers to
separate system
Controlling Exynos MIPI DPHY is done by handling 2 registers: one for
phy reset and one for enabling it. This patch moves definitions of those
2 registers to speparate exynos_mipi_phy_desc structure, which can be
defined separately for each PHY for each supported hardware variant.
This code
On Mon, Mar 21, 2016 at 08:58:02AM -0700, Laura Abbott wrote:
> On 03/21/2016 03:08 AM, Mark Rutland wrote:
> >On Mon, Mar 21, 2016 at 04:07:47PM +0800, Chen Feng wrote:
> >>But if we use VA to flush cache to do cache-coherency with other
> >>master(eg:gpu)
> >>
> >>We must iterate over the
Hi
On Wed, Mar 23, 2016 at 9:42 AM, Alexey Brodkin
wrote:
> As a pair to already existing drm_connector_unregister_all() we're adding
> generic implementation of what is already done in some drivers.
>
> Once this helper is implemented we'll be ready to switch existing
> driver-specific
> Bandan Das wrote on 03/22/2016 09:00:50 PM:
> > "Michael Rapoport" writes:
> >
> > Well, Elvis is a _theoretical_ example that showed that I/O scheduling
in
> > the vhost improves performance.
> > I'm not saying we should take Evlis and try to squeeze it into the
vhost,
> > I just want to
On Tue, Mar 22, 2016 at 10:15:49AM +1100, Stephen Rothwell wrote:
> Today's linux-next merge of the arm64 tree got a conflict in:
>
> arch/arm64/mm/init.c
>
> between commit:
>
> dfd55ad85e4a ("arm64: vmemmap: use virtual projection of linear region")
>
> from Linus' tree and commit:
>
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: a24e3d414e59ac76566dedcad1ed1d319a93ec14
commit: d4883d5d6b146fd65f762c462b2c6d4a327c7d50 objtool: Enable stack metadata
validation on 64-bit x86
date: 3 weeks ago
config: x86_64-randconfig-x014-03231738
On Wednesday 23 March 2016 10:34:15, Mark Brown wrote:
> > I'm currently trying to get PCIe working on LS1021A (little-endian
> > ARM). For link-detection I need access to a syscon perpheral (SCFG)
> > which is attched to CPU as big-endian.
>
> Are you *sure* that this is actually big endian?
Le 16/03/2016 14:19, Nicolas Ferre a écrit :
> This is a series to add driver for a new Atmel Shutdown Controller. This new
> IP
> is extensible and some features will be added later (see the TODO section).
> Its extensible nature led to write a new binding so that wake-up sources can
> be
>
On Wednesday 23 March 2016 11:08:04, Marc Zyngier wrote:
> > Using an intel e1000e card which uses 3 MSIs. But the IRQ numbers are a bit
> > strange though:
> >> grep eth3 /proc/interrupts
> >>
> >> 63: 49 0 MSI 134742016 Edge eth3-rx-0
> >> 64: 3 0
Some Layerscape SoCs use a simple MSI controller implementation.
It contains only two SCFG register to trigger and describe a
group 32 MSI interrupts. The patch adds bindings to describe
the controller.
Signed-off-by: Minghuan Lian
---
change log:
v6-v4: no change
v4: add interrupt-parent
Some kind of Freescale Layerscape SoC provides a MSI
implementation which uses two SCFG registers MSIIR and
MSIR to support 32 MSI interrupts for each PCIe controller.
The patch is to support it.
Signed-off-by: Minghuan Lian
Tested-by: Alexander Stein
Acked-by: Marc Zyngier
---
Change log
v6:
Le 18/03/2016 11:34, Alexandre Belloni a écrit :
> On 18/03/2016 at 08:21:19 +0100, Ludovic Desroches wrote :
>> So far, the CIDR and EXID registers were in the DBGU interface. This device
>> has disappeared with the SAMA5D2 family. These registers are exposed
>> through a new device called
Hi,
I noticed this issues when running make htmldocs. It returns the following
warnings:
.//include/linux/regulator/machine.h:163: warning: No description found for
parameter 'over_current_protection'
.//include/linux/regulator/driver.h:205: warning: No description found for
parameter
Operation set_over_current_protection of regulator_ops is missing a
description for documentation.
Fixes: 3a003baeec24 ("regulator: Add over current protection (OCP) support")
Signed-off-by: Luis de Bethencourt
---
include/linux/regulator/driver.h | 3 +++
1 file changed, 3 insertions(+)
diff
Le 17/03/2016 17:04, Ludovic Desroches a écrit :
> From: Cyrille Pitchen
>
> This SFR node is looked up by the I2S controller driver to tune the
> SFR_I2SCLKSEL register.
>
> Signed-off-by: Cyrille Pitchen
> Signed-off-by: Ludovic Desroches
Acked-by: Nicolas Ferre
I'll queue it in our
Members csel_reg and csel_mask of the regulator_desc struct are missing
descriptions for documentation. Adding them.
Fixes: c0ea88b890d6 ("regulator: tps65218: add support for LS3 current
regulator")
Signed-off-by: Luis de Bethencourt
---
include/linux/regulator/driver.h | 2 ++
1 file
On Wed, Mar 23, 2016 at 03:59:32PM +0530, Aneesh Kumar K.V wrote:
> Jerome Glisse writes:
[...]
> >> +static int hmm_mirror_fault_hpmd(struct hmm_mirror *mirror,
> >> > + struct hmm_event *event,
> >> > + struct vm_area_struct
David Rientjes wrote:
> On Tue, 22 Mar 2016, Michal Hocko wrote:
>
> > Hi,
> > I am reposting the whole patchset on top of the current Linus tree which
> > should
> > already contain big pile of Andrew's mm patches. This should serve an easier
> > reviewability and I also hope that this core
On Wed, Mar 23, 2016 at 4:17 AM, Geert Uytterhoeven
wrote:
> On Tue, Mar 8, 2016 at 2:53 PM, Maciej S. Szmigiero
> wrote:
>> FAT has long supported its own default file name encoding
>> config setting, separate from CONFIG_NLS_DEFAULT.
>>
>> However, if UTF-8 encoded file names are desired FAT
On Mon, 21 Mar 2016, Alex Thorlton wrote:
First of all, please use proper patch prefixes.
x86/platform/uv:
And please fold the documentation change into the patch which changes the
parameter.
> static int timeout_us;
> -static int nobau;
> +static int nobau = 1;
> static int nobau_perm;
Commit-ID: b7c8b4aac6ea6746b1c49fda0a0563a07203dd26
Gitweb: http://git.kernel.org/tip/b7c8b4aac6ea6746b1c49fda0a0563a07203dd26
Author: Vladimir Zapolskiy
AuthorDate: Tue, 22 Mar 2016 01:42:07 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 23 Mar 2016 12:30:40 +0100
Hi!
> > But we have fixed regulator there, it does not have "reg" property.
>
> The fixed regulator doesn't even use I2C. So, you need to debug why it
> calls I2C. Your information given is not enough for me.
Thanks for the help. It seems to have been mismerge on my dts.
Best regards,
Over current protection is missing descriptions for documentation.
Fixes: 3a003baeec24 ("regulator: Add over current protection (OCP) support")
Signed-off-by: Luis de Bethencourt
---
Hi,
Sorry. I missed this second missing description related to over current
protection in
If asymmetric packing is used when target cpu is busy,
update_sd_pick_busiest(), can select a lightly loaded cpu.
find_busiest_group() has checks to ensure asym packing is only used
when target cpu is not busy. However it may not be able to avoid a
lightly loaded cpu selected by
On 23/03/16 11:19, Alexander Stein wrote:
> On Wednesday 23 March 2016 11:08:04, Marc Zyngier wrote:
>>> Using an intel e1000e card which uses 3 MSIs. But the IRQ numbers are a bit
>>> strange though:
grep eth3 /proc/interrupts
63: 49 0 MSI 134742016 Edge
On Wed, Mar 23, 2016 at 12:16:13PM +0100, Alexander Stein wrote:
> On Wednesday 23 March 2016 10:34:15, Mark Brown wrote:
> > Are you *sure* that this is actually big endian? Are you basing this on
> > documentation or on what happened to work for you in the past.
> Please refer to QorIQ
On 23 March 2016, Alexandre Belloni wrote:
> To: Opensource [Anthony Olech]; Opensource [Steve Twiss]
> Subject: Re: [NEW DRIVER V6 0/7] DA9058 PMIC - please comment on this new
> driver
>
> Hi Anthony, Steve,
>
> This driver has been submitted a while ago and reached v6 but still had
> a few
801 - 900 of 1478 matches
Mail list logo
