Hi Aaro,
On mer., août 10 2016, Aaro Koskinen wrote:
> Hi,
>
> When upgrading from v4.6 --> v4.7, I lost the display/framebuffer on
> OpenRD-Client (the only pcie device on the board).
>
> Bisection points to:
>
> eb13cf8345e94a02e9872ca3e909596a5ddb5f90 is the first bad commit
> commit eb13cf
On Thu, Aug 11, 2016 at 11:08:52AM +0800, Baolin Wang wrote:
> Hi Alan,
>
> On 10 August 2016 at 22:25, Alan Stern wrote:
> > On Wed, 10 Aug 2016, Baolin Wang wrote:
> >
> >> >> >> For example: No slave attached> usb interface runtime suspend
> >> >> >> > usb device runtime suspend ->
On Thu, Aug 11, 2016 at 12:35:40PM +0530, akash.g...@intel.com wrote:
> From: Akash Goel
>
> relay essentially needs to maintain the per CPU array of channel buffer
> pointers but it manually creates that array.
> Instead its better to avail the per CPU constructs, provided by the
> kernel, to al
On Wed, Aug 10, 2016 at 09:41:37PM +0200, SF Markus Elfring wrote:
> >> Please and and use pr_fmt
> >
> > Can't we use dev_* on the SDIO device?
>
> How should a connection be constructed from the data structure
> "sdio_device_id"
> to the corresponding device information for such an use case?
From: Eric Wong
Date: Thu, 11 Aug 2016 06:59:04 +
> Zhouyi Zhou wrote:
>> Hi,
>> Yesterday, I cced 5 patches to linux-kernel@vger.kernel.org using
>> send-email, but all of them were
>> rejected by mail server at vger.kernel.org as follows:
>> "Dear yizhouz...@ict.ac.cn, Your message t
Am Mittwoch, 10. August 2016, 15:14:06 schrieb Guenter Roeck:
> On Tue, Aug 9, 2016 at 11:02 AM, Chris Zhong wrote:
> > Fix incorrect rk3399 aclk_vio gating bit, it should be 0, not 10. With
> > this modification, the aclk_vio_noc should be put into critical list,
> > since it is required by VOP.
On Thu, Aug 11, 2016 at 09:52:55AM +0530, Maninder Singh wrote:
> Currently mmap_failed variable is 1 for every case, so make it 0
> if mmap is success.
>
> Signed-off-by: Maninder Singh
> Signed-off-by: Vaneet Narang
See section 11) of Documentation/SubmittingPatches on how the sign-off
chain
Hi, YT:
On Wed, 2016-08-10 at 15:24 +0800, YT Shen wrote:
> Hi CK,
>
> On Fri, 2016-08-05 at 18:08 +0800, CK Hu wrote:
> > Hi, YT:
> >
> > On Thu, 2016-08-04 at 19:07 +0800, YT Shen wrote:
> > > From: shaoming chen
> > >
> > > add dsi read/write commands for transfer function
> > >
> > > Sign
From: Fengtiantian
I find a issue in dentry cache used by sysctl proc.
If register sysctl proc file ,access the file and then unregister this file,
dentry in cache will keep increasing, and cause CPU softlockup。
I test in the kernel 3.10.0-327.
My testcase is :
#/bin/sh
while :
do
brc
On Wed, Aug 10, 2016 at 10:28:45PM +0200, Oliver Hartkopp wrote:
> Hi Andreas,
>
> On 08/09/2016 08:10 AM, Andreas Werner wrote:
> >On Mon, Aug 08, 2016 at 04:35:34PM +0200, Wolfgang Grandegger wrote:
>
> >>You specify here one echo_skb but it's not used anywhere. Local loopback
> >>seems
Am Donnerstag, den 04.08.2016, 10:38 +0800 schrieb Bibby Hsieh:
> From: Junzhi Zhao
>
> Pixel clock should be 297MHz when resolution is 4K.
>
> Signed-off-by: Junzhi Zhao
> Signed-off-by: Bibby Hsieh
> ---
> drivers/gpu/drm/mediatek/mtk_dpi.c |8 ++--
> 1 file changed, 6 insertions(+)
On Thu, Aug 11, 2016 at 11:11:08AM +0800, Baolin Wang wrote:
> On 10 August 2016 at 22:31, Alan Stern wrote:
> > On Wed, 10 Aug 2016, Baolin Wang wrote:
> >
> >> Considering strict power management for mobile device, we should also power
> >> off the usb controller if there are no slaves attached
The Image Sensor Controller driver includes two parts.
1) Driver code to implement the ISC function.
2) Device tree binding documentation, it describes how
to add the ISC in device tree.
Test result with v4l-utils.
# v4l2-compliance -f
v4l2-compliance SHA : not available
Driver Info:
DT binding documentation for ISC driver.
Acked-by: Rob Herring
Signed-off-by: Songjun Wu
---
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6:
- Add "iscck" and "gck" to clock-names.
Changes in v5:
- Add clock-output-names.
Changes in v4:
- Remove the isc clock nodes.
On Aug 10, 2016 5:16 PM, "Josh Poimboeuf" wrote:
>
> On Wed, Aug 10, 2016 at 12:25:11AM -0700, Andy Lutomirski wrote:
> > On Aug 10, 2016 2:27 AM, "Josh Poimboeuf" wrote:
> > >
> > > On Tue, Aug 09, 2016 at 06:17:41PM -0500, Nilay Vaish wrote:
> > > > On 4 August 2016 at 17:22, Josh Poimboeuf wr
Add driver for the Image Sensor Controller. It manages
incoming data from a parallel based CMOS/CCD sensor.
It has an internal image processor, also integrates a
triple channel direct memory access controller master
interface.
Signed-off-by: Songjun Wu
---
Changes in v9:
- Set the default format
On Aug 11, 2016 12:01 AM, "Mathieu Desnoyers"
wrote:
>
> - On Aug 10, 2016, at 4:09 PM, Andy Lutomirski l...@amacapital.net wrote:
>
> > On Wed, Aug 10, 2016 at 1:06 PM, Mathieu Desnoyers
> > wrote:
>
>
>
> >>> u64 is a perfectly valid, if odd, userspace pointer on all
> >>> architecures th
On Wed, Aug 10, 2016 at 10:16 PM, Al Viro wrote:
> On Wed, Aug 10, 2016 at 09:49:22PM -0700, Dan Williams wrote:
>
>> Where dax_dev_release() is the f_op->release() method, and is
>> implemented to simply drop the final references on our driver objects:
>>
>> struct dax_dev *dax_dev = filp
On Wed, Aug 10, 2016 at 4:37 PM, Kees Cook wrote:
> This fixes a ptrace vs fatal pending signals bug as manifested in seccomp
> now that ptrace was reordered to happen after ptrace. The short version is
> that seccomp should not attempt to call do_exit() while fatal signals are
> pending under a t
On 10/08/16 21:44, David Long wrote:
> From: "David A. Long"
>
> Because the arm64 calling standard allows stacked function arguments to be
> anywhere in the stack frame, do not attempt to duplicate the stack frame for
> jprobes handler functions.
>
> Documenation changes to describe this issue
On Wed, 10 Aug 2016, Suman Anna wrote:
> On 08/10/2016 04:19 PM, Bjorn Andersson wrote:
> > On Wed 10 Aug 14:04 PDT 2016, Suman Anna wrote:
> >
> >> On 08/10/2016 03:40 PM, Bjorn Andersson wrote:
> >>> On Wed 10 Aug 12:37 PDT 2016, Suman Anna wrote:
> >>>
> Hi Lee, Bjorn,
>
> On 08
Add constants and callback functions for the dwmac on rk3228/rk3229 socs.
As can be seen, the base structure is the same, only registers and the
bits in them moved slightly.
Signed-off-by: Roger Chen
---
.../devicetree/bindings/net/rockchip-dwmac.txt | 4 +-
drivers/net/ethernet/stmicro/st
This patch add ethernet GMAC dt nodes for RK3399 evaluation board.
Signed-off-by: Roger Chen
---
arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 23 +++
1 file changed, 23 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-evb.dts
b/arch/arm64/boot/dts/rockchip/rk
This patch adds ethernet GMAC dt notes for Rockchip RK3399 SoC.
Signed-off-by: Roger Chen
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 79
1 file changed, 79 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
b/arch/arm64/boot/dts/rockchip/rk
> Expose AVX512DQ, AVX512BW, AVX512VL feature to guest.
> Its spec can be found at:
> https://software.intel.com/sites/default/files/managed/b4/3a/319433-024.pdf
>
> Signed-off-by: Luwei Kang
> ---
> arch/x86/kvm/cpuid.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a
On Wed, 10 Aug 2016, Suman Anna wrote:
> On 08/09/2016 01:12 PM, Lee Jones wrote:
> > On Tue, 09 Aug 2016, Bjorn Andersson wrote:
> >
> >> On Thu 04 Aug 02:21 PDT 2016, Lee Jones wrote:
> >>
> >>> Before this patch, the dma_alloc_coherent() failure path printed out:
> >>>
> >>> "dma_alloc_coher
Hi, Yury
On 2016/6/18 7:54, Yury Norov wrote:
From: Andrew Pinski
In this patchset ILP32 ABI support is added. Additionally to AARCH32,
which is binary-compatible with ARM, ILP32 is (mostly) ABI-compatible.
From now, AARCH32_EL0 (former COMPAT) config option means the support of
AARCH32 use
This series adds registers description for RK3366 & RK3399 GMAC.
And also DT nodes for RK3399 SoC and EVB.
Roger Chen (3):
net: stmmac: dwmac-rk: add rk3366 & rk3399 specific data
arm64: dts: rockchip: add GMAC dt nodes for rk3399 SoC
arm64: dts: rockchip: add GMAC dt nodes for RK3399 evb
Hi Peter,
On 11 August 2016 at 14:52, Peter Chen wrote:
> On Thu, Aug 11, 2016 at 11:11:08AM +0800, Baolin Wang wrote:
>> On 10 August 2016 at 22:31, Alan Stern wrote:
>> > On Wed, 10 Aug 2016, Baolin Wang wrote:
>> >
>> >> Considering strict power management for mobile device, we should also
>
On 09/08/16 22:36, Mimi Zohar wrote:
> On Tue, 2016-08-09 at 15:19 +1000, Balbir Singh wrote:
>>
>> On 04/08/16 22:24, Mimi Zohar wrote:
>>> The TPM PCRs are only reset on a hard reboot. In order to validate a
>>> TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list
>>> of th
Since commit 52aec3308db8 ("x86/tlb: replace INVALIDATE_TLB_VECTOR by
CALL_FUNCTION_VECTOR"), the tlb remote shootdown is done through call
function vector. That commit didn't take care of irq_tlb_count so later
commit fd0f5869724f ("x86: Distinguish TLB shootdown interrupts from
other functions ca
On Thu, Aug 11, 2016 at 09:32:59AM +0200, Philipp Zabel wrote:
> Am Donnerstag, den 28.07.2016, 10:22 +0800 schrieb Bibby Hsieh:
> > Add gamma set function to correct brightness values.
> > It applies arbitrary mapping curve to compensate the
> > incorrect transfer function of the panel.
> >
> > S
On 2016年08月11日 00:40, Cornelia Huck wrote:
I'm hitting the following oops during shutdown (halt command in guest)
of a libvirt-managed qemu guest 100% of the time:
[ 108.920486] Unable to handle kernel pointer dereference in virtual kernel
address space
[ 108.920492] Failing address: 6b6b6b
Hi Lee,
I just tested your series and found issue with append mechanism.
There is no problem to add resources when working on Linux side, but the
resource table is growing and when copying it at loaded location (ie
overwriting existing prebuilt resource table of firmware), you have an
overflow
Am Donnerstag, den 28.07.2016, 10:22 +0800 schrieb Bibby Hsieh:
> Add gamma set function to correct brightness values.
> It applies arbitrary mapping curve to compensate the
> incorrect transfer function of the panel.
>
> Signed-off-by: Bibby Hsieh
> ---
> drivers/gpu/drm/mediatek/mtk_drm_crtc.c
Am Donnerstag, den 11.08.2016, 10:44 +0300 schrieb Ville Syrjälä:
> On Thu, Aug 11, 2016 at 09:32:59AM +0200, Philipp Zabel wrote:
> > Am Donnerstag, den 28.07.2016, 10:22 +0800 schrieb Bibby Hsieh:
> > > Add gamma set function to correct brightness values.
> > > It applies arbitrary mapping curve
Am Donnerstag, den 04.08.2016, 10:59 +0800 schrieb Bibby Hsieh:
> These patches based on 4.7-rc1 to clean up unused function
> & variable and use drm core function instead.
>
> The following patches are needed to cleanly apply on top of v4.7-rc1:
> - https://patchwork.kernel.org/patch/8044001/
>
On Wed 03-08-16 22:19:59, Geert Uytterhoeven wrote:
> mm/oom_kill.c: In function ‘task_will_free_mem’:
> mm/oom_kill.c:767: warning: ‘ret’ may be used uninitialized in this
> function
>
> If __task_will_free_mem() is never called inside the for_each_process()
> loop, ret will not be initi
hdmi->disabled maybe not match to the real hardware status.
->dw_hdmi_bridge_enable()
hdmi->disabled = false;
-->dw_hdmi_update_power()
if (hdmi->rxsense)
force = DRM_FORCE_ON;
else
force = DRM_FORCE_OFF;
hdmi->rxsense maybe false on bridge enable path, then hdmi->disabled
i
Since commit 3f8d6f2a0 ('ses: fix discovery of SATA devices in SAS
enclosures') ses_match_to_enclosure() is calling sas_get_address(),
which is coming from commit bcf508c13385 ('scsi_transport_sas: add
function to get SAS endpoint address'). sas_get_address() itself calls
sas_sdev_to_rdev() which B
On Thu, Aug 11, 2016 at 09:51:16AM +0200, Philipp Zabel wrote:
> Am Donnerstag, den 11.08.2016, 10:44 +0300 schrieb Ville Syrjälä:
> > On Thu, Aug 11, 2016 at 09:32:59AM +0200, Philipp Zabel wrote:
> > > Am Donnerstag, den 28.07.2016, 10:22 +0800 schrieb Bibby Hsieh:
> > > > Add gamma set function
On Mon, 2016-07-11 at 17:15 +0300, Maxim Altshul wrote:
> Mesh HWMP module will be able to rely on the HW
> RC algorithm if it exists, for path metric calculations.
>
> This allows the metric calculation mechanism to calculate
> a correct metric, based on PER and last TX rate both via
> HW RC algo
On 11 August 2016 at 02:29, Shaun Tancheff wrote:
>>
>> You are talking about an AF 4Kn drive I suppose? For a 512e drive it
>> should be only ~2G.
>
> I stand corrected. Since all the kernel math is 512 byte sectors you are
> absolutely correct and this isn't an issue at all.
>
> We should report
Hi Peter,
On 11 August 2016 at 14:54, Peter Chen wrote:
> On Thu, Aug 11, 2016 at 11:08:52AM +0800, Baolin Wang wrote:
>> Hi Alan,
>>
>> On 10 August 2016 at 22:25, Alan Stern wrote:
>> > On Wed, 10 Aug 2016, Baolin Wang wrote:
>> >
>> >> >> >> For example: No slave attached> usb interface r
From: Honghui Zhang
larb2 have 23 ports, the LARB3_PORT_OFFSET should be LARB2_PORT_OFFSET
plus larb2's port number, it should be 44 instead of 43.
Signed-off-by: Honghui Zhang
---
include/dt-bindings/memory/mt2701-larb-port.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
On Wed, Aug 10, 2016 at 04:29:22PM -0700, Davidlohr Bueso wrote:
> (1) As Manfred suggested, have a patch 1 that fixes the race against mainline
> with the redundant smp_rmb, then apply a second patch that gets rid of it
> for mainline, but only backport the original patch 1 down to 3.12.
I have
On Thu 04-08-16 14:46:49, Andrew Morton wrote:
> On Thu, 4 Aug 2016 21:28:13 +0900 Tetsuo Handa
> wrote:
>
> > >
> > > Fixes: 1af8bb43269563e4 ("mm, oom: fortify task_will_free_mem()")
> > > Signed-off-by: Geert Uytterhoeven
> > > ---
> > > Untested. I'm not familiar with the code, hence the d
Hi Roger,
Am Donnerstag, 11. August 2016, 15:24:46 schrieb Roger Chen:
> Add constants and callback functions for the dwmac on rk3228/rk3229 socs.
> As can be seen, the base structure is the same, only registers and the
> bits in them moved slightly.
>
> Signed-off-by: Roger Chen
> ---
> .../de
On Thu, 11 Aug 2016 15:49:12 +0800
Jason Wang wrote:
> This looks like a use-after-free. Could you pls try the following patch
> to see it if fixes your issue?
>
> diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
> index a38c0da..070e329 100644
> --- a/drivers/net/macvtap.c
> +++ b/dr
On Mon, Jul 11, 2016 at 9:01 PM, Stephen Boyd wrote:
> The drivers don't really need to know which PMIC they're for, so
> make a generic binding for them. This alleviates us from updating
> the drivers every time a new PMIC comes out. It's still
> recommended that we update the binding with new P
On Tue, Jul 19, 2016 at 1:27 PM, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Remove duplicated include.
>
> Signed-off-by: Wei Yongjun
Patch applied.
Yours,
Linus Walleij
On Fri, Jul 22, 2016 at 08:50:44AM -0400, Chris Metcalf wrote:
> On 7/21/2016 10:20 PM, Christoph Lameter wrote:
> >On Thu, 21 Jul 2016, Chris Metcalf wrote:
> >>On 7/20/2016 10:04 PM, Christoph Lameter wrote:
> >>unstable, and then scheduling work to safely remove that timer.
> >>I haven't looked
On Wed, Jul 20, 2016 at 4:11 PM, Maxime Ripard
wrote:
> The AXP209 PMIC has a bunch of GPIOs accessible, that are usually used to
> control LEDs or backlight.
>
> Add a driver for them
>
> Signed-off-by: Maxime Ripard
> Acked-by: Rob Herring
Patch applied, it's clean and simple. I would sugges
On Thu, Aug 11, 2016 at 04:07:21PM +0800, Baolin Wang wrote:
> Hi Peter,
>
> On 11 August 2016 at 14:54, Peter Chen wrote:
> > On Thu, Aug 11, 2016 at 11:08:52AM +0800, Baolin Wang wrote:
> >> Hi Alan,
> >>
> >> On 10 August 2016 at 22:25, Alan Stern wrote:
> >> > On Wed, 10 Aug 2016, Baolin Wan
On Thu, Aug 11, 2016 at 03:54:03PM +0800, Mark Yao wrote:
> hdmi->disabled maybe not match to the real hardware status.
>
> ->dw_hdmi_bridge_enable()
> hdmi->disabled = false;
> -->dw_hdmi_update_power()
>if (hdmi->rxsense)
>force = DRM_FORCE_ON;
>else
>force = DRM_FORCE_
Hi Balbi,
On 10/08/16 12:25, Felipe Balbi wrote:
>
> Hi,
>
> "Felipe F. Tonello" writes:
>> 512 is the value used by wMaxPacketSize, as specified by the USB Spec. This
>
> this is only true for HS :-) FS and SS use different sizes. Do you want
> to use 1024 (SS maxp) by default instead? Then a
Hi Frank,
On 08/10/2016 12:19 PM, Frank Wang wrote:
> Hi Neil,
>
> On 2016/8/9 18:29, Neil Armstrong wrote:
[...]
>>
>> Changes since RFC v2 at https://lkml.org/lkml/2016/6/21/324 :
>> - Moved MHU to a separate patchset posted at
>> http://lkml.kernel.org/r/1470732737-18391-1-git-send-email-n
On 08/10/2016 07:34 AM, Guenter Roeck wrote:
> Coverity reports:
>
> Passing argument 152UL /* sizeof (*wdd) */ to function __devres_alloc_node
> and then casting the return value to struct watchdog_device ** is
> suspicious.
>
> Allocation size needs to be sizeof(*rcwdd), not sizeof(*wdd).
>
>
* Baoquan He wrote:
> On 08/10/16 at 04:02pm, Ingo Molnar wrote:
> >
> > * Baoquan He wrote:
> >
> > > ACPI MADT has a 32-bit field providing lapic address at which
> > > each processor can access its lapic information. MADT also contains
> > > an optional entry to provide a 64-bit address to
On 08/08/16 22:48, Linus Walleij wrote:
> On Sat, Aug 6, 2016 at 1:45 AM, John Stultz wrote:
>
>> @@ -614,7 +615,11 @@ unsigned int irq_create_fwspec_mapping(struct
>> irq_fwspec *fwspec)
>> * it now and return the interrupt number.
>> */
>> if (i
Hi Balbi,
On 10/08/16 12:24, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> On 26 July 2016 at 07:15, Felipe F. Tonello wrote:
>>> USB spec specifies wMaxPacketSize to be little endian (as other properties),
>>> so when using this variable in the driver we should convert to the current
Hi,
I just wanted to kindly remind about this patch.
Best regards,
Grzegorz
2016-07-21 12:39 GMT+02:00 Grzegorz Jaszczyk :
> There is no need to implement subroutine for suspend since there is no
> data to store before suspending.
>
> Signed-off-by: Grzegorz Jaszczyk
> ---
> drivers/i2c/busses
Hi,
I just wanted to kindly remind about this patch.
Best regards,
Grzegorz
2016-07-21 12:43 GMT+02:00 Grzegorz Jaszczyk :
> There is no need to implement subroutine for suspend since there is no
> data to store before suspending.
>
> Signed-off-by: Grzegorz Jaszczyk
> ---
> drivers/thermal/ar
On Thu, Aug 11, 2016 at 12:16:58AM +0200, Frederic Weisbecker wrote:
> I had similar issues, this seems to happen when the tsc is considered not
> reliable
> (which doesn't necessarily mean unstable. I think it has to do with some x86
> CPU feature
> flag).
Right, as per the other email, in gene
On Wed, Jul 20, 2016 at 7:58 AM, Andrew Jeffery wrote:
> --- a/arch/arm/mach-aspeed/Kconfig
> +++ b/arch/arm/mach-aspeed/Kconfig
> @@ -5,6 +5,7 @@ menuconfig ARCH_ASPEED
> select WATCHDOG
> select ASPEED_WATCHDOG
> select MOXART_TIMER
> + select PINCTRL
> hel
Some PLLs can support dynamic reprogramming, which means just a L value
change is whats needed to change the PLL frequency without having to
explicitly enable/disable or bypass/re-lock the PLL.
Add support for such PLLs' initial configuration and the ops needed to
support the dynamic reprogramming
Some PLLs can have an additional early output (apart from
the main and aux outputs). Add support for the PLL driver
so it can be used to initialize/configure the early output
Signed-off-by: Rajendra Nayak
---
drivers/clk/qcom/clk-pll.c | 2 ++
drivers/clk/qcom/clk-pll.h | 1 +
2 files changed, 3
This would be useful in subsequent patches when the .set_rate operation
would need to identify if the PLL is actually enabled
Signed-off-by: Rajendra Nayak
---
drivers/clk/qcom/clk-alpha-pll.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/clk/qcom/clk-alpha-pll.
From: Taniya Das
Move all
'# define XYZ'
to
'#define XYZ'
Signed-off-by: Taniya Das
Signed-off-by: Rajendra Nayak
---
drivers/clk/qcom/clk-alpha-pll.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/clk/qcom/clk-alpha-pll.c b/driv
From: Taniya Das
Alpha PLLs which do not support dynamic update feature
need to be explicitly disabled before a rate change. The ones which do
support dynamic update don't have to be disabled but need to follow a update
sequence (as implemented by clk_alpha_pll_dynamic_update() in the patch).
The
The votable alpha PLLs need to have the fsm mode enabled as part
of the initialization. The sequence seems to be the same as used
by clk-pll, so move the function which does this into a common
place and reuse it for the clk-alpha-pll
Signed-off-by: Rajendra Nayak
Signed-off-by: Taniya Das
---
d
2016-08-11 6:54 GMT+09:00 Arnd Bergmann :
> Using "make tinyconfig" produces a couple of annoying warnings that show up
> for build test machines all the time:
>
> .config:966:warning: override: NOHIGHMEM changes choice state
> .config:965:warning: override: SLOB changes choice state
>
index is of type u8 in all places except in clk_hw_get_parent_by_index()
and return value of all round_rate functions is long except for
clk_hw_round_rate(). Make them consistent with the rest of the places
Signed-off-by: Rajendra Nayak
---
drivers/clk/clk.c| 4 ++--
include/linux/cl
On 11 August 2016 at 16:19, Peter Chen wrote:
> On Thu, Aug 11, 2016 at 04:07:21PM +0800, Baolin Wang wrote:
>> Hi Peter,
>>
>> On 11 August 2016 at 14:54, Peter Chen wrote:
>> > On Thu, Aug 11, 2016 at 11:08:52AM +0800, Baolin Wang wrote:
>> >> Hi Alan,
>> >>
>> >> On 10 August 2016 at 22:25, Al
Hi,
This series adds some additional support to the clk-alpha-pll and the
clk-pll drivers in preperation to add the CPU clock driver support
on msm8996
Changes in v2:
* Patch 1 to 6 are same as v1 post, added patches 7 to 10
Rajendra Nayak (8):
clk: Fix inconsistencies in usage of data types
On Wed, Aug 03, 2016 at 10:19:43AM -0400, nwatt...@codeaurora.org wrote:
[...]
> >+const struct iommu_ops *iort_iommu_configure(struct device *dev)
> >+{
> >+struct acpi_iort_node *node, *parent;
> >+struct fwnode_handle *iort_fwnode;
> >+u32 rid = 0, devid = 0;
>
> Since this routin
On 08/11/2016 09:14 AM, Andreas Werner wrote:
On Wed, Aug 10, 2016 at 10:28:45PM +0200, Oliver Hartkopp wrote:
Just check 'git grep IFF_ECHO'. Even grcan.c and janz-ican3.c have IFF_ECHO
set - but implement it in a different way without using the provided
machanism from dev.c .
Ok I am with
On 11 August 2016 at 09:47, Martin K. Petersen
wrote:
>
> Tom> so we can at most allow only a 2-block (well, or 3-block) payload.
>
> We tried turning on multi block payloads and it was a massive disaster.
> Many drives reported that they supported 8 block payloads but actually
> didn't. Instead o
Add a function to do initial configuration of the alpha plls
Signed-off-by: Rajendra Nayak
---
drivers/clk/qcom/clk-alpha-pll.c | 23 +++
drivers/clk/qcom/clk-alpha-pll.h | 13 +
2 files changed, 36 insertions(+)
diff --git a/drivers/clk/qcom/clk-alpha-pll.c b/dr
Some PLLs can support an alpha mode, and a single alpha
register (instead of registers to program the M/N values),
the contents of which depend on the alpha mode selected.
(They are either treated as two's complement or M/N value)
Add support for this in the clk PLL driver.
Signed-off-by: Rajendra
Add support to enable/disable the alpha pll using hwfsm
Signed-off-by: Rajendra Nayak
---
drivers/clk/qcom/clk-alpha-pll.c | 109 ++-
drivers/clk/qcom/clk-alpha-pll.h | 1 +
2 files changed, 98 insertions(+), 12 deletions(-)
diff --git a/drivers/clk/qcom/cl
* Baoquan He wrote:
> On 08/10/16 at 02:53pm, Ingo Molnar wrote:
> >
> > * Baoquan He wrote:
> >
> > > It won't impact the result, we still should fix the code bug.
> > >
> > > Signed-off-by: Baoquan He
> > > Cc: "Rafael J. Wysocki"
> > > Cc: Len Brown
> > > Cc: Pavel Machek
> > > Cc: Th
Hi
I noticed some changes in the mmc block driver that did not go
through the mmc tree and they looked wrong so I gave them a test.
And it does seem like secure discard is broken, not just for mmc
but in general too. The commit was:
288dab8a35a0 ("block: add a separate operation type for secure e
On Tue, 9 Aug 2016, Steven Rostedt wrote:
> On Tue, 9 Aug 2016 10:16:00 +0200 (CEST)
> Miroslav Benes wrote:
>
>
> > I agree it is kind of shooting oneself in the foot bug, because explicit
> > call to a sleeping function may not be the brightest thing to do. However
> > I see two (closely re
Michael reported 'perf mem -t store record' being broken.
The reason is latest rework of this area:
commit acbe613e0c03 ("perf tools: Add monitored events array")
We don't mark perf_mem_events store record when -t store
option is specified.
Fixes: commit acbe613e0c03 ("perf tools: Add monitored
of_mm_gpiochip_add_data() calls mm_gc->save_regs() before
setting the data. Therefore ->save_regs() cannot use
gpiochip_get_data()
[0.275940] Unable to handle kernel paging request for data at address
0x0130
[0.283120] Faulting instruction address: 0xc01b44cc
[0.288175] Oops: Kern
On Thu, Aug 11, 2016 at 04:41:27PM +0800, Baolin Wang wrote:
> >> >>
> >> >> OK. But that is a real problem. It will pm_runtime_resume() falied
> >> >> (issued in choose_wakeup()), cause usb controller has powered-off and
> >> >> xHCI controller has suspended and we have no method to notify the use
* Andy Lutomirski wrote:
> On Aug 10, 2016 3:31 PM, "Ingo Molnar" wrote:
> >
> >
> > One side note:
> >
> > * Andy Lutomirski wrote:
> >
> > > This series fixes it the other way: it allow the trampoline to live
> > > in boot services memory. It achieves this by deferring the panic
> > > due t
On 10 August 2016 at 20:21, Jon Mason wrote:
> On Wed, Aug 10, 2016 at 1:44 PM, Ray Jui wrote:
>> On 8/10/2016 10:28 AM, Rafał Miłecki wrote:
>>>
>>> On 10 August 2016 at 19:22, Jon Mason wrote:
On Wed, Aug 10, 2016 at 8:05 AM, Rafał Miłecki wrote:
>
> diff --git a/Documentati
Hi All.
Have posted the question on Sierra-forums
https://forum.sierrawireless.com/viewtopic.php?f=117&t=9898
Posting it here as well, as the activity there is relatively low, and
this is where all the kernel-guys hand :)
I am using a Ubuntu interfaced with a Sierra-MC8090 module.
Right now MC8
On Thu, Aug 11, 2016 at 11:02:27AM +0300, Ville Syrjälä wrote:
> On Thu, Aug 11, 2016 at 09:51:16AM +0200, Philipp Zabel wrote:
> > Am Donnerstag, den 11.08.2016, 10:44 +0300 schrieb Ville Syrjälä:
> > > On Thu, Aug 11, 2016 at 09:32:59AM +0200, Philipp Zabel wrote:
> > > > Am Donnerstag, den 28.07
On Thu, Aug 11, 2016 at 09:33:26AM +0200, Philipp Zabel wrote:
> Am Donnerstag, den 04.08.2016, 10:59 +0800 schrieb Bibby Hsieh:
> > These patches based on 4.7-rc1 to clean up unused function
> > & variable and use drm core function instead.
> >
> > The following patches are needed to cleanly appl
* Icenowy Zheng wrote:
>
>
> 10.08.2016, 20:52, "Ingo Molnar" :
> > * Icenowy Zheng wrote:
> >
> >> Some broken firmwares have a wrongly filled version field in BGRT table.
> >> (See http://wiki.osdev.org/Broken_UEFI_implementations )
> >>
> >> As we know, these firmwares can also provide
On Thursday, August 11, 2016 3:35:01 PM CEST Zhangjian (Bamvor) wrote:
> On 2016/6/18 7:54, Yury Norov wrote:
> > From: Andrew Pinski
> >
> > In this patchset ILP32 ABI support is added. Additionally to AARCH32,
> > which is binary-compatible with ARM, ILP32 is (mostly) ABI-compatible.
> >
> > F
On 2016年08月11日 16:13, Cornelia Huck wrote:
On Thu, 11 Aug 2016 15:49:12 +0800
Jason Wang wrote:
This looks like a use-after-free. Could you pls try the following patch
to see it if fixes your issue?
diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
index a38c0da..070e329 100644
---
On Thu, Aug 11, 2016 at 10:45:00AM +0200, Oliver Hartkopp wrote:
> On 08/11/2016 09:14 AM, Andreas Werner wrote:
> >On Wed, Aug 10, 2016 at 10:28:45PM +0200, Oliver Hartkopp wrote:
>
> >>Just check 'git grep IFF_ECHO'. Even grcan.c and janz-ican3.c have IFF_ECHO
> >>set - but implement it in a dif
* Arnd Bergmann wrote:
> Using "make tinyconfig" produces a couple of annoying warnings that show up
> for build test machines all the time:
>
> .config:966:warning: override: NOHIGHMEM changes choice state
> .config:965:warning: override: SLOB changes choice state
> .config:963:war
The "hix5hd2" is SoC name, add the generic ethernet driver name.
The "hisi-gemac-v1" is the basic version and "hisi-gemac-v2" adds
the SG/TXCSUM/TSO/UFO features.
This patch set only adds the SG(scatter-gather) driver for transmitting,
the drivers of other features will be submitted later.
Add the
From: Li Dongpo
Add three reset control signals, "mac_core_rst", "mac_ifc_rst" and
"phy_rst".
The following diagram explained how the reset signals work.
SoC
|-
| --|
|
Because the clock and reset signals share the same register,
we initialize reset controller when initializing clock controller.
So the ethernet driver will control the reset signal instead of
the clock driver.
All the ethernet clock is changed from complex clock to gate clock.
The original ethernet
1 - 100 of 803 matches
Mail list logo
