On Tue, Jan 20, 2015 at 5:48 AM, Thierry Reding
wrote:
> From: Thierry Reding
>
> There is no use-case where it would be useful for drivers not to
> implement this function and the transitional plane helpers already
> require drivers to provide an implementation.
>
> Signed-off-by: Thierry
On Thu, 11 Dec 2014, Andy Shevchenko wrote:
> This patchset creates a new folder under drivers/mfd and moves there Intel
> related drivers.
>
> There is no functional change. The names of the kernel configuration variables
> are kept the same.
Can you explain to me why you think the Intel
On Tue, 2015-01-20 at 13:29 +0100, Olivier Sobrie wrote:
> When usb_queue_reset() is called it schedules a work in view of
> resetting the usb interface. When the reset work is running, it
> can be scheduled again (e.g. by the usb disconnect method of
> the driver).
>
> Consider that the reset
On Sun, 04 Jan 2015, Rickard Strandqvist wrote:
> Removes some functions that are not used anywhere:
> usbhs_readb() usbhs_writeb()
>
> This was partially found by using a static code analysis program called
> cppcheck.
>
> Signed-off-by: Rickard Strandqvist
> ---
>
On Tue, 2015-01-20 at 12:47 +, Lee Jones wrote:
> On Thu, 11 Dec 2014, Raymond Tan wrote:
[]
> > +static const struct i2c_mode_info platform_i2c_mode_info[] = {
> > + {
> > + .name = "Galileo",
> > + .i2c_scl_freq = 10,
> > + },
> > + {
> > + .name =
On Mon, 05 Jan 2015, Krzysztof Kozlowski wrote:
> Document usage of maxim,ena-gpios properties which turn on external/GPIO
> control over regulator.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> Documentation/devicetree/bindings/mfd/max77686.txt | 14 ++
> 1 file changed, 14
Commit-ID: 32c6590d126836a062b3140ed52d898507987017
Gitweb: http://git.kernel.org/tip/32c6590d126836a062b3140ed52d898507987017
Author: K. Y. Srinivasan
AuthorDate: Mon, 12 Jan 2015 16:26:02 -0800
Committer: Thomas Gleixner
CommitDate: Tue, 20 Jan 2015 14:36:25 +0100
x86, hyperv: Mark
On Mon, Jan 19, 2015 at 05:40:09PM +, Mark Rutland wrote:
> On Mon, Jan 19, 2015 at 02:40:28PM +, Mark Rutland wrote:
> > On Fri, Jan 16, 2015 at 02:11:04PM +, Peter Zijlstra wrote:
> > > On Fri, Jan 16, 2015 at 11:46:44AM +0100, Peter Zijlstra wrote:
> > > > Its a bandaid at best :/
Previous, jiffy-based, implementation had three issues:
1. For low HZ values (<100 and >=50) the timeout would be 1 jiffy,
which can cause premature timeouts if a timer interrupt happens
right after the "timeo" value is assigned.
2. For very low HZ values the timeout is 0 jiffies, which
On 01/20/2015 07:11 AM, Orson Zhai wrote:
> Hi, Peter,
>
> Thank you for reviewing our code!
> Some discussion below.
>
> On 2015年01月16日 23:20, Peter Hurley wrote:
>> On 01/16/2015 05:00 AM, Chunyan Zhang wrote:
>>> Add a full sc9836-uart driver for SC9836 SoC which is based on the
>>>
On Sat 17-01-15 10:21:47, Johannes Weiner wrote:
> The "none" name for the low-boundary 0 and the high-boundary maximum
> value can be confusing.
>
> Just leave the low boundary at 0, and give the highest-possible
> boundary value the name "max" that means the same for controls.
max might be
On Mon, 05 Jan 2015, Krzysztof Kozlowski wrote:
> Replace direct calls to power supply function attributes with wrappers.
> Wrappers provide safe access in case of unregistering the power
> supply (e.g. by removing the driver). Replace:
> - get_property -> power_supply_get_property
>
>
On Mon, 05 Jan 2015, Krzysztof Kozlowski wrote:
> Use power_supply_put() to decrement the power supply's device reference
> counter.
>
> Signed-off-by: Krzysztof Kozlowski
> Acked-by: Pavel Machek
> Acked-by: Linus Walleij
> Acked-by: Lee Jones
You've sent this to me already Acked. I don't
Commit-ID: 9d34cfdf47963905d792ae9c000efa522739abe4
Gitweb: http://git.kernel.org/tip/9d34cfdf47963905d792ae9c000efa522739abe4
Author: Juergen Gross
AuthorDate: Mon, 12 Jan 2015 06:15:45 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 20 Jan 2015 14:33:45 +0100
x86: Don't rely on
On Tue, Jan 20, 2015 at 2:28 PM, Cyril Hrubis wrote:
> Hi!
>> > Most of the failures comes from EBUSY while trying to umount
>> > filesystems. Do you have gvfsd-trash running? That thing is known to
>> > probe newly mounted filesystems preventing them from being unmounted for
>> > a certain
On 01/20/2015 02:27 PM, Zhang Yanfei wrote:
> Hello,
>
> 在 2015/1/19 18:05, Vlastimil Babka 写道:
>> @@ -883,6 +883,8 @@ static void isolate_freepages(struct compact_control *cc)
>> nr_freepages += isolated;
>>
>> /*
>> + * If we isolated enough freepages, or
在 2015/1/19 18:05, Vlastimil Babka 写道:
> Reseting the cached compaction scanner positions is now done implicitly in
> __reset_isolation_suitable() and compact_finished(). Encapsulate the
> functionality in a new function reset_cached_positions() and call it
> explicitly where needed.
>
>
Hi!
> > Most of the failures comes from EBUSY while trying to umount
> > filesystems. Do you have gvfsd-trash running? That thing is known to
> > probe newly mounted filesystems preventing them from being unmounted for
> > a certain amount of time.
> >
>
> Yupp, that popped up.
> How can I
Hi Joe,
On Tue, Jan 20, 2015 at 09:18:30PM +0800, Yingjoe Chen wrote:
> On Tue, 2015-01-20 at 10:47 +0100, Sascha Hauer wrote:
> <...>
> > diff --git a/drivers/soc/mediatek/mtk-pericfg.c
> > b/drivers/soc/mediatek/mtk-pericfg.c
> > index b7ee902..aa9a7eb 100644
> > ---
Hello,
在 2015/1/19 18:05, Vlastimil Babka 写道:
> Handling the position where compaction free scanner should restart (stored in
> cc->free_pfn) got more complex with commit e14c720efdd7 ("mm, compaction:
> remember position within pageblock in free pages scanner"). Currently the
> position is
As clk_unprepare_unused_subtree and clk_disable_unused_subtree are
always called with a valid struct clk.
Signed-off-by: Tomeu Vizoso
Reviewed-by: Stephen Boyd
---
drivers/clk/clk.c | 9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index
Adds a way for clock consumers to set maximum and minimum rates. This
can be used for thermal drivers to set minimum rates, or by misc.
drivers to set maximum rates to assure a minimum performance level.
Changes the signature of the determine_rate callback by adding the
parameters min_rate and
在 2015/1/19 18:05, Vlastimil Babka 写道:
> Compaction should finish when the migration and free scanner meet, i.e. they
> reach the same pageblock. Currently however, the test in compact_finished()
> simply just compares the exact pfns, which may yield a false negative when the
> free scanner
On Sat 17-01-15 10:21:19, Johannes Weiner wrote:
> High limit reclaim can currently overscan in proportion to how many
> charges are happening concurrently. Tone it down such that charges
> don't target the entire high-boundary excess, but instead only the
> pages they charged themselves when
Moves clock state to struct clk_core, but takes care to change as little API as
possible.
struct clk_hw still has a pointer to a struct clk, which is the
implementation's per-user clk instance, for backwards compatibility.
The struct clk that clk_get_parent() returns isn't owned by the caller,
On Tue, Jan 20, 2015 at 07:26:09PM +0800, Greg Kroah-Hartman wrote:
> On Tue, Jan 20, 2015 at 11:57:12AM +0100, Johannes Stezenbach wrote:
> >
> > So I did some googling and found in QNX servers create a channel
> > to receive messages, and clients connect to this channel.
> > Multiple clients
Hi,
I have addressed here the last comments from Stephen, most notably:
* Add more missing NULL checks
* Remove a few unused functions
* Call nolock variants from __clk_mux_determine_rate
* Refactor __clk_determine_rate to share code with clk_round_rate.
The second patch actually moves the
On 20 January 2015 10:46 Lee Jones wrote:
[...]
> > static const struct regmap_range da9063_ad_readable_ranges[] = {
> > {
> > .range_min = DA9063_REG_PAGE_CON,
> > @@ -203,6 +206,13 @@ static struct regmap_config da9063_regmap_config
> = {
> > .cache_type =
On Tue, 13 Jan 2015, Calvin Owens wrote:
> While debugging an issue with excessive softirq usage, I encountered the
> following note in commit 3e339b5dae24a706 ("softirq: Use hotplug thread
> infrastructure"):
>
> [ paulmck: Call rcu_note_context_switch() with interrupts enabled. ]
>
>
Richard Guy Briggs wrote:
> It also occurs to me that the pid_t of that process in init PID
> namespace would be useful for each entry.
Me too. I added it.
Steve Grubb wrote:
> > > As for the date-stamping bits, they seem to be the majority of the code
> > > in audit_update_history(). I'd just
On Tue, Jan 20, 2015 at 12:20:05PM +, Lee Jones wrote:
> On Fri, 02 Jan 2015, Inha Song wrote:
> > This patch update DT binding to support OUTn_MONO init_data. Each
> > output signal can be configurated as a mono differential output.
> > The mono differential configuration is selected using
Alexander Shishkin writes:
> Peter Zijlstra writes:
>
>> On Wed, Jan 14, 2015 at 02:18:21PM +0200, Alexander Shishkin wrote:
>>> +static __init int pt_init(void)
>>> +{
>>
>>> + pt_pmu.pmu.attr_groups = pt_attr_groups;
>>> + pt_pmu.pmu.task_ctx_nr = perf_hw_context;
>>
>> I just noticed
On Tue, 2015-01-20 at 10:47 +0100, Sascha Hauer wrote:
<...>
> diff --git a/drivers/soc/mediatek/mtk-pericfg.c
> b/drivers/soc/mediatek/mtk-pericfg.c
> index b7ee902..aa9a7eb 100644
> --- a/drivers/soc/mediatek/mtk-pericfg.c
> +++ b/drivers/soc/mediatek/mtk-pericfg.c
> @@ -1,6 +1,5 @@
> /*
> *
On Tue, 2015-01-20 at 13:29 +0100, Olivier Sobrie wrote:
> When the rfkill interface was created, a buffer containing the name
> of the rfkill node was allocated. This buffer was never freed when the
> device disappears.
>
> To fix the problem, we put the name given to rfkill_alloc() in
> the
Hi Lorenzo,
Sorry for the late reply, I was updating this patch according
to your comments and see if it works, inline reply below.
On 2015年01月17日 02:18, Lorenzo Pieralisi wrote:
Hi Hanjun,
On Wed, Jan 14, 2015 at 03:04:58PM +, Hanjun Guo wrote:
[...]
diff --git
On Thu, 15 Jan 2015, Rob Herring wrote:
> On Thu, Jan 15, 2015 at 3:11 AM, Thomas Gleixner wrote:
> > On Wed, 14 Jan 2015, Rob Herring wrote:
>
> > We do not change shared interrupts in any way. We provide an
> > alternative mechanism for braindead hardware. And if the at91 folks
> > are fine
On Tue, Jan 20, 2015 at 07:07:07PM +0800, Wang Nan wrote:
> This 2 patches are based on Jiri Olsa's perf repository:
>
> https://git.kernel.org/cgit/linux/kernel/git/jolsa/perf.git/log/?h=perf/core_ctf_convert
>
> Perf data convert to failes when converting perf.data recorded with
>
> # perf
On 01/20/2015 05:40 AM, Tomasz Nowicki wrote:
> Hi Marc,
>
> On 16.01.2015 12:15, Marc Zyngier wrote:
>> On 14/01/15 15:05, Hanjun Guo wrote:
>>> From: Tomasz Nowicki
>>>
>>> ACPI kernel uses MADT table for proper GIC initialization. It needs to
>>> parse GIC related subtables, collect CPU
On 01/15/15 at 04:51pm, Kees Cook wrote:
> On 64-bit, relocation is not required unless the load address gets
> changed. Without this, relocations do unexpected things when the kernel
> is above 4G.
This patch works for me. And good to see it's being merged. About the
patch log, I would say
On Tue, Jan 20, 2015 at 07:07:08PM +0800, Wang Nan wrote:
SNIP
> + *
> + * So instead of checking duplication, simply tries 10 times.
> + */
> + for (dup = 0; dup < 10; dup ++) {
> + struct bt_ctf_field_type *f;
> +
On Sat, 3 Jan 2015, Rickard Strandqvist wrote:
> Remove the function bfin_sec_resume() that is not used anywhere.
>
> This was partially found by using a static code analysis program called
> cppcheck.
>
> Signed-off-by: Rickard Strandqvist
This doesn't seem to be present in linux-next as of
On 20 January 2015 at 01:00, Stephen Boyd wrote:
> On 01/19, Tomeu Vizoso wrote:
>> Adds a way for clock consumers to set maximum and minimum rates. This can be
>> used for thermal drivers to set ceiling rates, or by misc. drivers to set
>> floor rates to assure a minimum performance level.
>>
>>
Hi Linus,
The following changes since commit b7392d2247cfe6771f95d256374f1a8e6a6f48d6:
Linux 3.19-rc2 (2014-12-28 16:49:37 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-fixes-3.19
for you to fetch changes up to
On 01/20/2015 12:17 PM, Lee Jones wrote:
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
Modify FLASH_EN_SHIFT and TORCH_EN_SHIFT macros to work properly
when passed enum max77693_fled values (0 for FLED1 and 1 for FLED2)
from leds-max77693 driver.
Off-by-one ay? Wasn't the original code
The conditional in local_irq_restore() otherwise can cause code bloat
(the if and else blocks may get translated into separate code paths
despite the generated code being identical, dependent on compiler
internal heuristics). Note that this adjustment gets the code in sync
with the comment
When requesting clock in the platform driver, leaving
chip->clk value as NULL if -ENOENT is returned, and
continue. With other errors returning failure. It makes the
driver usable on platforms that do not provide the clock.
Signed-off-by: Heikki Krogerus
---
drivers/dma/dw/platform.c | 8
On Tue 20-01-15 11:23:40, long.wanglong wrote:
[...]
> hi, Michal Hocko
>
> sorry for the wrong description in the email. i run the two testcase in
> kernel v3.10.63, not
> the latest kernel.
>
> in kernel v3.18, the two testcases can not invoke OOM killer.
>
> The problem comes from the LTP
On 01/20/2015 12:13 PM, Lee Jones wrote:
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
Change flash cell identifiers from max77693-flash to max77693-led
to avoid confusion with NOR/NAND Flash.
This is okay by me, but aren't these ABI yet?
No, the led driver using it hasn't been merged yet.
Hello Fam Zheng,
On 01/20/2015 10:57 AM, Fam Zheng wrote:
> This syscall is a sequence of
>
> 1) a number of epoll_ctl calls
> 2) a epoll_pwait, with timeout enhancement.
>
> The epoll_ctl operations are embeded so that application doesn't have to use
> separate syscalls to insert/delete/update
On Mon, 15 Dec 2014, Alan Cox wrote:
> The code bothers to probe for the device, but on failing to find it proceeds
> to try and release a NULL resource, thereby ruining it's prior good
> behaviour
>
> Resolves-Bug: https://bugzilla.kernel.org/show_bug.cgi?id=88581
> Signed-off-by: Alan Cox
Commit-ID: 7575637ab293861a799f3bbafe0d8c597389f4e9
Gitweb: http://git.kernel.org/tip/7575637ab293861a799f3bbafe0d8c597389f4e9
Author: Oleg Nesterov
AuthorDate: Thu, 15 Jan 2015 20:20:28 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 20 Jan 2015 13:53:07 +0100
x86, fpu: Fix
A small number of systems respond to PnP dock queries with bogus values.
This causes us to keep logging an error every 2 seconds. Instead of trying
again just assume the BIOS is crapware and doesn't actually have dock
functionality.
Signed-off-by: Alan Cox
---
drivers/pnp/pnpbios/core.c |3
Commit-ID: 14e153ef75eecae8fd0738ffb42120f4962a00cd
Gitweb: http://git.kernel.org/tip/14e153ef75eecae8fd0738ffb42120f4962a00cd
Author: Oleg Nesterov
AuthorDate: Thu, 15 Jan 2015 20:19:43 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 20 Jan 2015 13:53:07 +0100
x86, fpu: Introduce
Commit-ID: 33a3ebdc077fd85f1bf4d4586eea579b297461ae
Gitweb: http://git.kernel.org/tip/33a3ebdc077fd85f1bf4d4586eea579b297461ae
Author: Oleg Nesterov
AuthorDate: Thu, 15 Jan 2015 20:20:05 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 20 Jan 2015 13:53:07 +0100
x86, fpu: Don't abuse
--
www.facebook.com
Congratulations,
As we Celebrate our 10years of internet Journey and Global Communication
we are glad to Announce to you that your facebook account have been
randomly selected as a beneficiary of $1,000,000.00usd in the 2014
Facebook Account of the Year {Grand Rewards
On 01/20/2015 09:25 AM, Daniel Mack wrote:
> Hi Michael,
>
> On 01/20/2015 09:09 AM, Michael Kerrisk (man-pages) wrote:
>> On 11/30/2014 06:23 PM, Florian Weimer wrote:
>>> * David Herrmann:
>>>
On Sun, Nov 30, 2014 at 10:02 AM, Florian Weimer
wrote:
> * Greg Kroah-Hartman:
>
On 01/20/2015 12:12 PM, Lee Jones wrote:
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
Add macros for max77693 led part related binding.
Signed-off-by: Jacek Anaszewski
Acked-by: Kyungmin Park
Cc: Lee Jones
Cc: Chanwoo Choi
---
include/dt-bindings/mfd/max77693.h | 21
On Tue, Jan 20, 2015 at 10:56:33AM +0100, Miroslav Benes wrote:
> On Fri, 9 Jan 2015, Josh Poimboeuf wrote:
> > +struct klp_ops {
> > + struct list_head node;
> > + struct list_head func_stack;
> > + struct ftrace_ops fops;
> > +};
>
> I think it would be useful to add some comments for
On Tue, Jan 20, 2015 at 03:40:50PM +0900, Namhyung Kim wrote:
> When perf exits with some error it shows the error message with
> ui__error() or ui__warning() and then calls ui__exit() during
> exit_browser().
>
> On TUI, it then shows a window titled "Fatal Error" to inform user a
> last message
On Tue, Jan 20, 2015 at 12:49:35PM +0100, Miroslav Benes wrote:
> Change ARCH_HAVE_LIVE_PATCHING to HAVE_LIVE_PATCHING in Kconfigs. HAVE_
> bools are prevalent there and we should go with the flow.
>
> Suggested-by: Andrew Morton
> Signed-off-by: Miroslav Benes
Acked-by: Josh Poimboeuf
> ---
Hello Fam Zheng,
I know this API has been through a number of iterations, and there were
discussions about the design that led to it becoming more complex.
But, let us assume that someone has not seen those discussions,
or forgotten them, or is too lazy to go hunting list archives.
Then: this
On Thu, 11 Dec 2014, Raymond Tan wrote:
> In Quark X1000, there's a single PCI device that provides both
> an I2C controller and a GPIO controller. This MFD driver will
> split the 2 devices for their respective drivers.
>
> This patch is based on Josef Ahmad's initial work for Quark enabling.
>
Hi Thomas,
There was a problem awhile ago regarding hrtimer interrupt missing tick
reprogramming: https://lkml.org/lkml/2014/3/17/323
This is the last version of the patch rebased on top of 3.19-rc5 and
lightly tested. Could you please apply it?
---
I think I'm hitting particularly subtle
On Tue, 13 Jan 2015, Borislav Petkov wrote:
> Hi guys,
>
> here just a bunch of minor cleanups for 3.20.
>
> Please pull,
> thanks.
>
> ---
> The following changes since commit b1940cd21c0f4abdce101253e860feff547291b0:
>
> Linux 3.19-rc3 (2015-01-05 17:05:20 -0800)
>
> are available in the
On 1/20/2015 5:23 PM, Lee Jones wrote:
> On Wed, 07 Jan 2015, Vignesh R wrote:
>
>> In one shot mode, sequencer automatically disables all enabled steps at
>> the end of each cycle. (both ADC steps and TSC steps) Hence these steps
>> need not be saved in reg_se_cache for clearing these steps at
2015-01-08 3:55 GMT+01:00 James Liao :
> Hi Matthias,
>
> On Wed, 2015-01-07 at 18:22 +0100, Matthias Brugger wrote:
>> 2015-01-07 4:25 GMT+01:00 James Liao :
[...]
>> > +
>> > +extern spinlock_t *get_mtk_clk_lock(void);
>> > +
>> > +#define mtk_clk_lock(flags)
In big endian CPU mode l2x0_saved_regs structure stores registers values in BE
format. In order to maintain BE CPU mode, these values and immediate constants
must be converted back to LE format before writing them to cache controller.
Signed-off-by: Dmitry Osipenko
---
Hello Thomas,
2015-01-20 16:29 GMT+06:00 Thomas Gleixner :
> On Mon, 19 Jan 2015, Alexander Kuleshov wrote:
>
>> The following two patches remove unused macro definitions from
>> early_serial_console and early_printk x86 code.
>
> Sigh. These mechanical 'follow the output of some code analyzer'
>
When the device disappear, the function hso_disconnect() is called to
perform cleanup. In the cleanup function, hso_free_interface() calls
tty_port_tty_hangup() in view of scheduling a work to hang up the tty if
needed. If the port was not open then hso_serial_ref_free() is called
directly to
Add Right-J mode and set TCR5 FBT bit to let data right justify.
Signed-off-by: Zidan Wang
---
sound/soc/fsl/fsl_sai.c | 14 +++---
sound/soc/fsl/fsl_sai.h | 1 +
2 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/sound/soc/fsl/fsl_sai.c b/sound/soc/fsl/fsl_sai.c
index
Add sai master mode support.
Add tdm slots support.
Add Right-J mode support.
Zidan Wang (3):
SoC: fsl_sai: add sai master mode support
ASoC: fsl_sai: Add support for tdm slots operation
ASoC: fsl_sai: Add support for Right-J mode
sound/soc/fsl/fsl_sai.c | 164
On Tue, Jan 20, 2015 at 12:56 PM, Cyril Hrubis wrote:
> Hi!
>> > I will check my "iniza" setup of Linux v3.19-rc5 the "(runltp-)lite" way.
>> >
>>
>> Attached are the runltp-lite result and my kernel-config.
>>
>> I see a lot of "unexpected" failures, can you comment on them?
>
> Most of the
slots and slot width is set from set_dai_tdm_slot in machine driver.
We should calculate the actual slots per channel using slots/channels.
When using tdm slots, we should generate bclk depends channels, slots
and slot width. And there may be unused BCLK cycles before each LRCLK
transition.
Set
When the rfkill interface was created, a buffer containing the name
of the rfkill node was allocated. This buffer was never freed when the
device disappears.
To fix the problem, we put the name given to rfkill_alloc() in
the hso_net structure.
Signed-off-by: Olivier Sobrie
---
In the disconnect path, tx_buffer should freed like tx_data to avoid
a memory leak when the device disconnects.
Signed-off-by: Olivier Sobrie
---
drivers/net/usb/hso.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/usb/hso.c b/drivers/net/usb/hso.c
index 3a6c630..470ef9e 100644
These patches attempt to fix some problems I observed when the hso
device is disconnected or when a usb reset is queued by the hso driver
Several patches of this serie are fixing crashes or memleaks in hso.
The last patch of this serie fix a race condition occurring when multiple
usb resets are
I just realised I had an old USB BT-dongle so I tried it, and the
trackpad was working fine with `auto` in `power/control`, so, yes,
sounds like the builtin BT adapter is faulty.
But here is a strange thing again: as with the keyboard I had to set
`power/control` of the hub to `on` in order for
makes code look a bit prettier.
Cc: linux-cry...@vger.kernel.org.
Signed-off-by: Michael S. Tsirkin
---
drivers/char/hw_random/virtio-rng.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/char/hw_random/virtio-rng.c
b/drivers/char/hw_random/virtio-rng.c
index 72295ea..3fa2f8a 100644
No timer related function is used in this driver.
Signed-off-by: Olivier Sobrie
---
drivers/net/usb/hso.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/usb/hso.c b/drivers/net/usb/hso.c
index babda7d..cb0bcc1 100644
--- a/drivers/net/usb/hso.c
+++ b/drivers/net/usb/hso.c
@@
There is no need for a dedicated reset work in the hso driver since
there is already a reset work foreseen in usb_interface that does
the same.
Signed-off-by: Olivier Sobrie
---
drivers/net/usb/hso.c | 25 +
1 file changed, 1 insertion(+), 24 deletions(-)
diff --git
The function hso_serial_common_free() is called either by the cleanup
method of the tty or by the usb disconnect method.
In the former case, the usb_disconnect() has been already called
and the sysfs group associated to the device has been removed.
By calling tty_unregister directly from the
In other functions of the driver, variables of type "struct hso_serial"
are denoted by "serial" and variables of type "struct hso_device" are
denoted by "hso_dev". This patch makes the hso_free_interface()
consistent with these notations.
Signed-off-by: Olivier Sobrie
---
drivers/net/usb/hso.c
On Thu, 2014-12-11 at 17:53 +0200, Andy Shevchenko wrote:
> Instead of keeping everything in one folder with long prefixes let us to
> reoder
> files in the tree by moving them in the dedicated folder. Currently we have
> drivers for Intel MID platforms, LPC, and few more are coming.
>
> This
When usb_queue_reset() is called it schedules a work in view of
resetting the usb interface. When the reset work is running, it
can be scheduled again (e.g. by the usb disconnect method of
the driver).
Consider that the reset work is queued again while the reset work
is running and that this work
Thanks for reviewing. I propose the following additions instead.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
Add sign_extend64() for sign extending any (hardware-)given signed value
greater than 32 bits to s64.
Suggested-by: Christoph Muellner
Suggested-by: Peter Zijlstra
Signed-off-by: Martin Kepplinger
---
include/linux/bitops.h | 11 +++
1 file changed, 11 insertions(+)
diff --git
Signed-off-by: Martin Kepplinger
---
include/linux/bitops.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/bitops.h b/include/linux/bitops.h
index 5d858e0..336f22b 100644
--- a/include/linux/bitops.h
+++ b/include/linux/bitops.h
@@ -164,6 +164,8 @@ static inline __u8
For hso serial devices, two cancel_work_sync were missing in the
disconnect method.
Signed-off-by: Olivier Sobrie
---
drivers/net/usb/hso.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/usb/hso.c b/drivers/net/usb/hso.c
index c916ab5..c14fc80 100644
---
The serial_table is used to map the minor number of the usb serial device
to its associated context. The table is updated in the probe method and
in hso_serial_ref_free() which is called either from the tty cleanup
method or from the usb disconnect method.
This patch ensures that the serial_table
On Tue, Jan 20, 2015 at 11:10:32AM +, Mark Rutland wrote:
> > diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
> > index 54e39e3..8268c7b 100644
> > --- a/arch/arm64/kernel/setup.c
> > +++ b/arch/arm64/kernel/setup.c
> > @@ -371,6 +371,31 @@ static void __init
Simply remove the useless extra tab.
Signed-off-by: Olivier Sobrie
---
drivers/net/usb/hso.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/usb/hso.c b/drivers/net/usb/hso.c
index a49ac2e..2f2343d 100644
--- a/drivers/net/usb/hso.c
+++
> Happy New Year.
And to you.
> Regarding Andriy's suggestion to split and reorganize the MFD drivers for IA
> platform in the previous email, any thoughts from you? Should I proceed to
> work in splitting it or keep the structure as-is for now? Thanks.
I will review it as it is for now. I
On 20.01.2015 12:00, Catalin Marinas wrote:
On Tue, Jan 20, 2015 at 02:39:16AM +, Hanjun Guo wrote:
On 2015年01月19日 18:42, Catalin Marinas wrote:
On Sun, Jan 18, 2015 at 06:25:53AM +, Hanjun Guo wrote:
On 2015年01月16日 17:49, Catalin Marinas wrote:
On Wed, Jan 14, 2015 at 03:04:54PM
On 2015年01月20日 19:17, Catalin Marinas wrote:
On Wed, Jan 14, 2015 at 03:04:59PM +, Hanjun Guo wrote:
--- a/drivers/acpi/processor_core.c
+++ b/drivers/acpi/processor_core.c
@@ -64,6 +64,38 @@ static int map_lsapic_id(struct acpi_subtable_header *entry,
return 0;
}
+/*
+ * On ARM
Some ARM platforms mux the PMU interrupt of every core into a single
SPI. On such platforms if the PMU of any core except 0 raises an interrupt
then it cannot be serviced and eventually, if you are lucky, the spurious
irq detection might forcefully disable the interrupt.
On these SoCs it is not
Support CPU BE mode by adding endianness conversion for memcpy interactions.
Signed-off-by: Dmitry Osipenko
---
drivers/i2c/busses/i2c-tegra.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
index 28b87e6..e0d3ef1 100644
---
On Tue, Jan 20, 2015 at 1:11 PM, Alan wrote:
> I can't prove the case pointed out in
> https://bugzilla.kernel.org/show_bug.cgi?id=82341
> is correct so let us play safe.
>
> Signed-off-by: Alan Cox
> ---
> arch/um/os-Linux/drivers/ethertap_user.c |2 +-
> 1 file changed, 1 insertion(+), 1
When sai works on master mode, set its bit clock and frame clock.
SAI has 4 MCLK source, bus clock, MCLK1, MCLK2 and MCLK3. fsl_sai_set_bclk
will select proper MCLK source, then calculate and set the bit clock divider.
After fsl_sai_set_bclk, enable the selected mclk in hw_params(), and add
On Fri, 02 Jan 2015, Inha Song wrote:
> This patch update DT binding to support OUTn_MONO init_data. Each
> output signal can be configurated as a mono differential output.
> The mono differential configuration is selected using the OUTn_MONO
> registers.
This requires a DT Ack and an entry in
DT Ack (for this and the doc) required.
> Some boards need to set the OUTn_MONO register to configurates
> the output signal path as a mono differential output. This
> wlf,out-mono property is optional. If present, values must be
> specified less than or equal to the number of output signals.
>
701 - 800 of 2172 matches
Mail list logo
