Since there is no call to dev_get_drvdata() or input_get_drvdata(),
the call to input_set_drvdata() is unnecessary and can be dropped.
The conversion was done automatically using the following coccinelle
script.
@used@
@@
(
input_get_drvdata(...)
|
dev_get_drvdata(...)
)
@depends on !used@
@@
Reviewed-by: Chris Zhong
On 01/22/2017 12:31 AM, John Keeping wrote:
As the documentation for readx_poll_timeout says, we want to use the
specialized macro for readl rather than using the generic version
directly.
Signed-off-by: John Keeping
---
Unchanged in v2
---
drivers/gpu/drm/rockchip
Since there is no call to dev_get_drvdata() or input_get_drvdata(),
the call to input_set_drvdata() is unnecessary and can be dropped.
The conversion was done automatically using the following coccinelle
script.
@used@
@@
(
input_get_drvdata(...)
|
dev_get_drvdata(...)
)
@depends on !used@
@@
Dear All,
> Dear All,
>
> > Thierry, Jingoo,
> >
> > Please respond to Lukasz.
>
> Yes, your response is more than welcome... :-)
More, more than welcome.
Ping for this patch. I do understand that kernel developers are busy
people, but this patch is not reviewed since Nov last year :-)
>
Ping. Hi Myungjoo,
Could you apply these patches if there is no any comment?
On 2017년 01월 16일 21:26, Chanwoo Choi wrote:
> This patches update the devfreq and devfreq-event device. I add the summary
> of each patch as following.
> - Patch1 fixes the wrong description of governor_userspace.c.
> -
Hello Dear.
My name is Miss Naya M Makhlouf I am 19yrs Old girl from Syrian, I am the only
child of Hassan Mohammed Makhlouf, who was a business man and deals in Crude
oil and gold and who was killed in 2012 and by all investigation it was
planned by my uncle ( Mr Rami Makhlouf) who took over
Hi Martin,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 7a308bb3016f57e5be11a677d15b821536419d36
commit: 8d021d71b3247937a26ffdf313fd53a9d58778b7 drm/nouveau/drm/nouveau: add a
LED driver for the NVIDIA logo
date
Patch 1 fixes an issue when using drastically different BPF map definitions
inside ELFs from a client using libbpf, vs the map definition libbpf uses.
Patches 2-4 add some simple, useful helper functions for setting prog type
and retrieving libbpf errors without depending on kernel headers from
us
These bpf_prog_types were exposed in the uapi but there were no
corresponding functions to set these types for programs in libbpf.
Signed-off-by: Joe Stringer
Acked-by: Wang Nan
---
v2: Add ack.
---
tools/lib/bpf/libbpf.c | 5 +
tools/lib/bpf/libbpf.h | 10 ++
2 files changed, 15 i
This function will turn a libbpf pointer into a standard error code (or
0 if the pointer is valid). This also allows removal of the dependency
on linux/err.h in the public header file, which causes problems in
userspace programs built against libbpf.
Signed-off-by: Joe Stringer
Acked-by: Wang Nan
Commit 4708bbda5cb2 ("tools lib bpf: Fix maps resolution") attempted to
fix map resolution by identifying the number of symbols that point to
maps, and using this number to resolve each of the maps.
However, during relocation the original definition of the map size was
still in use. For up to two
Add a new API to pin a BPF object to the filesystem. The user can
specify the path full path within a BPF filesystem to pin the object.
Programs will be pinned under a subdirectory 'progs', and maps will be
pinned under a subdirectory 'maps'.
For example, with the directory '/sys/fs/bpf/foo':
/sys
Add a new API to pin a BPF map to the filesystem. The user can
specify the path full path within a BPF filesystem to pin the map.
Signed-off-by: Joe Stringer
---
v2: Don't automount BPF filesystem
Split program, map, object pinning into separate APIs and separate
patches.
---
tools/lib/b
Add a new API to pin a BPF program to the filesystem. The user can
specify the path full path within a BPF filesystem to pin the program.
Programs with multiple instances are pinned as 'foo', 'foo_1', 'foo_2',
and so on.
Signed-off-by: Joe Stringer
---
v2: Don't automount BPF filesystem
Split
On 19 January 2017 at 02:24, Wangnan (F) wrote:
>
>
> On 2017/1/19 7:57, Joe Stringer wrote:
>>
>> Patch 1 fixes an issue when using drastically different BPF map
>> definitions
>> inside ELFs from a client using libbpf, vs the map definition libbpf uses.
>>
>> Patch 2 is a trivial typo fix.
>>
>>
Turning this into a macro allows future prog types to be added with a
single line per type.
Signed-off-by: Joe Stringer
Acked-by: Wang Nan
---
v2: Add ack.
---
tools/lib/bpf/libbpf.c | 41 -
1 file changed, 16 insertions(+), 25 deletions(-)
diff --git a/
On 2017/1/22 20:58, zhongjiang wrote:
> From: zhong jiang
>
> Recently, I find the ioremap_page_range had been abusing. The improper
> address mapping is a issue. it will result in the crash. so, remove
> the symbol. It can be replaced by the ioremap_cache or others symbol.
>
> Signed-off-by: zhon
FYI, we noticed the following commit:
commit: a1a22c12060e4b9c52f45d4b3460f614e00162a2 ("net: ipv6: Keep nexthop of
multipath route on admin down")
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
in testcase: trinity
with following parameters:
runtime: 300s
t
On Fri, 20 Jan 2017 22:34:57 +0800, Geliang Tang wrote:
> Since i_blocksize() helper has been defined in fs.h, use it instead
> of open-coding.
>
> Signed-off-by: Geliang Tang
i_blocksize() doesn't exist in the mainline kernel.
This needs another patch titled "fs: add i_blocksize()" which I fou
On Sun, Jan 22, 2017 at 04:48:19PM -0800, Guenter Roeck wrote:
> If there is not call to dev_get_drvdata() or input_get_drvdata(),
> the call to input_set_drvdata() is unnecessary and can be dropped.
>
> The series was build tested on kerneltests.org and by the 0day build system.
>
> The patch se
On 01/22/2017 05:14 PM, zhong jiang wrote:
On 2017/1/22 20:58, zhongjiang wrote:
From: zhong jiang
Recently, I find the ioremap_page_range had been abusing. The improper
address mapping is a issue. it will result in the crash. so, remove
the symbol. It can be replaced by the ioremap_cache or
Hi John
On 01/22/2017 12:31 AM, John Keeping wrote:
The multiplication ratio for the PLL is required to be even due to the
use of a "by 2 pre-scaler". Currently we are likely to end up with an
odd multiplier even though there is an equivalent set of parameters with
an even multiplier.
For exam
From: zhouxianrong
the idea is that without doing more calculations we extend zero pages
to same element pages for zram. zero page is special case of
same element page with zero element.
1. the test is done under android 7.0
2. startup too many applications circularly
3. sample the zero pages, s
On 01/22/2017 06:44 PM, Jarkko Sakkinen wrote:
@@ -1025,8 +1029,60 @@ int tpm2_auto_startup(struct tpm_chip *chip)
}
}
+ rc = tpm2_get_tpm_pt(chip, TPM_PT_TOTAL_COMMANDS, &nr_commands, NULL);
+ if (rc)
+ goto out;
+
+ /* sanity check */
+
> if (!dev || !profile || !governor_name) {
> @@ -568,7 +569,8 @@ struct devfreq *devfreq_add_device(struct device *dev,
> mutex_lock(&devfreq->lock);
> }
>
> - dev_set_name(&devfreq->dev, "%s", dev_name(dev));
> + dev_set_name(&devfreq->dev, "devfreq%lu",
> +
On 01/16/2017 05:47 AM, Philipp Zabel wrote:
On Sat, 2017-01-14 at 14:46 -0800, Steve Longerbeam wrote:
[...]
+Unprocessed Video Capture:
+--
+
+Send frames directly from sensor to camera interface, with no
+conversions:
+
+-> ipu_smfc -> camif
I'd call this capture in
On Fri, Jan 20, 2017 at 04:43:47PM +0800, Baoyou Xie wrote:
> +static int zx2967_i2c_probe(struct platform_device *pdev)
> +{
> + struct resource *res;
> + struct zx2967_i2c_info *zx_i2c = NULL;
> + struct clk *clk;
> + void __iomem *reg_base;
> + int ret = 0;
> +
> + zx_i2c
Hello,
On Sun, Jan 22, 2017 at 10:58:38AM +0800, zhouxianrong wrote:
> 1. memset is just set a int value but i want to set a long value.
Sorry for late review.
Do we really need to set a long value? I cannot believe that
long value is repeated in the page. Value repeatition is
usually done by va
On Mon, Jan 23, 2017 at 10:55:23AM +0900, Minchan Kim wrote:
> From: zhouxianrong
>
> the idea is that without doing more calculations we extend zero pages
> to same element pages for zram. zero page is special case of
> same element page with zero element.
>
> 1. the test is done under android
On Wed, 01/18 15:28, Cathy Avery wrote:
> Enable FC lightweight host option so that the luns exposed by
> the driver may be manually scanned.
Hi Cathy, out of curiosity: how does this relate to issue_lip operation? And how
to trigger manual scan with this patch?
Fam
This patch just removes '.' character from the sysfs name of devfreq-event
device as following. Usually, the subsystem uses the similiar naming style
such as {framework name}{Number}.
- old : /sys/class/devfreq-event/event.[X]
- new : /sys/class/devfreq-event/event[X]
And this patch initializes th
This patch fixes the wrong description of governor_userspace.c
and removes the unneeded blank line.
Signed-off-by: Chanwoo Choi
---
drivers/devfreq/governor_userspace.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/devfreq/governor_userspace.c
b/drivers/devfreq/g
This patches update the devfreq and devfreq-event device. I add the summary
of each patch as following.
- Patch1 fixes the wrong description of governor_userspace.c.
- Patch2 show the information of registered PPMU devices.
- Patch3/4 modify the name of sysfs entry for devfreq/devfreq-event device
This patch modifies the device name as devfreq[X] for sysfs by using the
'devfreq'
prefix word instead of separate device name. On user-space aspect, user would
find the some devfreq drvier with 'devfreq[X]' pattern. So, this patch modify
the
device name as following:
- /sys/class/devfreq/[non-st
This patch just adds the simple log to show the PPMU device's registration
during the kernel booting.
Signed-off-by: Chanwoo Choi
---
drivers/devfreq/event/exynos-ppmu.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/devfreq/event/exynos-ppmu.c
b/drivers/devfreq/event/exynos-ppm
hey Joonsoo:
i would test and give the same element type later.
On 2017/1/23 10:58, Joonsoo Kim wrote:
Hello,
On Sun, Jan 22, 2017 at 10:58:38AM +0800, zhouxianrong wrote:
1. memset is just set a int value but i want to set a long value.
Sorry for late review.
Do we really need to s
On 2017년 01월 23일 11:19, MyungJoo Ham wrote:
>> if (!dev || !profile || !governor_name) {
>> @@ -568,7 +569,8 @@ struct devfreq *devfreq_add_device(struct device *dev,
>> mutex_lock(&devfreq->lock);
>> }
>>
>> -dev_set_name(&devfreq->dev, "%s", dev_name(dev));
>> +de
the purpose for reverse iteration is that i want compiler
compose decreasing instruction and compared instruction with zero
into one instruction which change cpu condition state.
yes, this maybe cause cache problem so need to be reviewed. thanks
On 2017/1/23 11:02, Joonsoo Kim wrote:
On Mon, Ja
From: Sean Wang
MT6323 PMIC is a multi-function device that includes
LED function. It allows attaching upto 4 LEDs which can
either be on, off or dimmed and/or blinked with the the
controller.
Signed-off-by: Sean Wang
---
drivers/leds/Kconfig | 8 +
drivers/leds/Makefile | 1 +
From: Sean Wang
Add compatible string as "mt6323-led" that will make
the OF core spawn child devices for the LED subnode
of that MT6323 MFD device.
Signed-off-by: Sean Wang
---
drivers/mfd/mt6397-core.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/mfd/mt6397-core.c b/drivers
From: Sean Wang
This patch adds documentation for devicetree bindings
for LED support on MT6323 PMIC
Signed-off-by: Sean Wang
---
.../devicetree/bindings/leds/leds-mt6323.txt | 60 ++
1 file changed, 60 insertions(+)
create mode 100644 Documentation/devicetree/bindin
From: Sean Wang
This patch adds documentation for devicetree bindings
for LED support as the subnode of MT6323 PMIC
Signed-off-by: Sean Wang
---
Documentation/devicetree/bindings/mfd/mt6397.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/mt6397
From: Sean Wang
MT7623 SoC uses MT6323 PMIC as the default power supply
which has LED function insides. The patchset introduces
the LED support for MT6323 with on, off and hardware
dimmed and blinked and it should work on other similar
SoCs if also using MT6323.
Sean Wang (4):
Documentation: d
On 01/21/2017 04:50 AM, Stephen Boyd wrote:
> On 01/10, Stanimir Varbanov wrote:
>>
>>> + udelay(1);
>>> +
>>> + reg = sc->gds_hw_ctrl ? sc->gds_hw_ctrl : sc->gdscr;
>>> + ret = gdsc_poll_status(sc, reg, 0);
>>
>> This should be gdsc_poll_status(sc, reg, true) becaus
On (01/23/17 11:58), Joonsoo Kim wrote:
> Hello,
>
> On Sun, Jan 22, 2017 at 10:58:38AM +0800, zhouxianrong wrote:
> > 1. memset is just set a int value but i want to set a long value.
>
> Sorry for late review.
>
> Do we really need to set a long value? I cannot believe that
> long value is rep
[]..
>> ---
>>
>> Stan,
>> If there was a specific issue you saw with venus because of the missing
>> delay and poll, can you check if this fixes any of that.
>>
>> drivers/clk/qcom/gdsc.c | 58
>> ++---
>> 1 file changed, 45 insertions(+), 13 deletio
[Re: [PATCH 20/20] module.h: remove extable.h include now users have migrated]
On 23/01/2017 (Mon 06:52) kbuild test robot wrote:
> Hi Paul,
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.10-rc5 next-20170120]
> [if your patch is applied to the wrong git tree, please
zram_reset_device waits ongoing writepage pages completed by
zram->refcount logic. However, it's pointless because before
the reset, we prevent further opening of zram by zram->claim
and flush all of pending IO by fsync_bdev so there should be
no pending IO at the zram_reset_device.
So let's remov
It's much the same as what we did for mwifiex in:
b9da4d2 mwifiex: avoid double-disable_irq() race
"We have a race where the wakeup IRQ might be in flight while we're
calling mwifiex_disable_wake() from resume(). This can leave us
disabling the IRQ twice.
Let's disable the IRQ and enable it in ca
The irq_of_parse_and_map will return 0 as a invalid irq.
Set irq_bt to -1 in this case, so that the btmrvl resume/suspend code
would not try to enable/disable it.
Signed-off-by: Jeffy Chen
Reviewed-by: Brian Norris
---
Changes in v2:
Update commit message.
drivers/bluetooth/btmrvl_sdio.c | 1
Use irqflags parsed from dt.
Signed-off-by: Jeffy Chen
Reviewed-by: Brian Norris
---
Changes in v2: None
drivers/bluetooth/btmrvl_sdio.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/bluetooth/btmrvl_sdio.c b/drivers/bluetooth/btmrvl_sdio.c
index 796f719..23711
Once a gdsc is brought in and out of HW control, there is a
power down and up cycle which can take upto 1us. Polling on
the gdsc status immediately after the hw control enable/disable
can mislead software/firmware to belive the gdsc is already either on
or off, while its yet to complete the power c
On Thu, Jan 19, 2017 at 08:04:59PM -0800, Andy Lutomirski wrote:
> On Thu, Jan 19, 2017 at 6:39 PM, Alexei Starovoitov
> wrote:
> > On Wed, Jan 18, 2017 at 06:29:22PM -0800, Andy Lutomirski wrote:
> >> I think it could work by making a single socket cgroup controller that
> >> handles all cgroup t
Now that we have proper kernel reference infrastructure in place for OPP
tables, use it to guarantee that the OPP table isn't freed while being
used by the callers of dev_pm_opp_set_*() APIs.
Make them all return the pointer to the OPP table after taking its
reference and put the reference back wi
Hi Rafael,
This series is based over the other OPP series [1] which is ready to be
merged and is fully reviewed.
In this series, 11 out of 12 patches have Reviewed-by from Stephen. Only
the 7th patch hasn't got any of those.
@Stephen: Can you see if you can do a generic review of it as well?
Tha
Take reference of the OPP table while adding and removing OPPs, that
helps us remove special checks in _remove_opp_table().
Signed-off-by: Viresh Kumar
Reviewed-by: Stephen Boyd
---
drivers/base/power/opp/core.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/driver
Migrate all users of _add_opp_table() to use dev_pm_opp_get_opp_table()
to guarantee that the OPP table doesn't get freed while being used.
Also update _managed_opp() to get the reference to the OPP table.
Now that the OPP table wouldn't get freed while these routines are
executing after dev_pm_o
Take reference of the OPP table from within _find_opp_table(). Also
update the callers of _find_opp_table() to call
dev_pm_opp_put_opp_table() after they have used the OPP table.
Note that _find_opp_table() increments the reference under the
opp_table_lock.
Now that the OPP table wouldn't get fre
The RCU locking isn't well suited for the OPP core. The RCU locking fits
better for reader heavy stuff, while the OPP core have at max one or two
readers only at a time.
Over that, it was getting very confusing the way RCU locking was used
with the OPP core. The individual OPPs are mostly well han
Add kref to struct dev_pm_opp for easier accounting of the OPPs.
Note that the OPPs are freed under the opp_table->lock mutex only.
Signed-off-by: Viresh Kumar
Reviewed-by: Stephen Boyd
---
drivers/base/power/opp/core.c | 27 ---
drivers/base/power/opp/opp.h | 3 +++
Add kref to struct opp_table for easier accounting of the OPP table.
Note that the new routine dev_pm_opp_get_opp_table() takes the reference
from under the opp_table_lock, which guarantees that the OPP table
doesn't get freed unless dev_pm_opp_put_opp_table() is called for the
OPP table.
Two sep
Update OPP documentation to remove the RCU specific bits.
Signed-off-by: Viresh Kumar
Reviewed-by: Stephen Boyd
---
Documentation/power/opp.txt | 52 ++---
1 file changed, 16 insertions(+), 36 deletions(-)
diff --git a/Documentation/power/opp.txt b/Docum
dev_pm_opp_get_max_volt_latency() calls _find_opp_table() two times
effectively.
Merge _get_regulator_count() into dev_pm_opp_get_max_volt_latency() to
avoid that.
Signed-off-by: Viresh Kumar
Reviewed-by: Stephen Boyd
---
drivers/base/power/opp/core.c | 34 +-
1
This patch updates dev_pm_opp_find_freq_*() routines to get a reference
to the OPPs returned by them.
Also updates the users of dev_pm_opp_find_freq_*() routines to call
dev_pm_opp_put() after they are done using the OPPs.
As it is guaranteed the that OPPs wouldn't get freed while being used,
the
As we don't use RCU locking anymore, there is no need to replace an
earlier OPP node with a new one. Just update the existing one.
Signed-off-by: Viresh Kumar
Reviewed-by: Stephen Boyd
---
drivers/base/power/opp/core.c | 27 +--
1 file changed, 5 insertions(+), 22 deleti
Add per OPP table lock to protect opp_table->opp_list.
Note that at few places opp_list is used under the rcu_read_lock() and
so a mutex can't be added there for now. This will be fixed by a later
patch.
Signed-off-by: Viresh Kumar
Reviewed-by: Stephen Boyd
---
drivers/base/power/opp/core.c |
On Fri, Jan 20, 2017 at 05:52:13PM +0800, Yisheng Xie wrote:
> Hi Naoya,
>
> On 2017/1/18 17:45, Naoya Horiguchi wrote:
> > On Wed, Jan 18, 2017 at 12:00:54PM +0800, Yisheng Xie wrote:
> >> This patch is to extends soft offlining framework to support
> >> non-lru page, which already support migrat
On Thu, Jan 19, 2017 at 10:59:03PM +0800, ys...@foxmail.com wrote:
> From: Yisheng Xie
>
> This patch is to extends soft offlining framework to support
> non-lru page, which already support migration after
> commit bda807d44454 ("mm: migrate: support non-lru movable page
> migration")
>
> When m
Hello,
When I look at first patch, I wanted to use increment loop but didn't
tell to you because that small piece of code is no harmful for readbility
to me so I want to keep author's code rather than pointing the trivial
which is just matter of preference out.
Rather than readiblity, I suspect i
This patch adds dt-binding documentation for zx2967 family
i2c controller.
Signed-off-by: Baoyou Xie
---
.../devicetree/bindings/i2c/i2c-zx2967.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-zx2967.txt
diff
Add the zx2967 i2c controller driver as maintained by ARM ZTE
architecture maintainers, as they're parts of the core IP.
Signed-off-by: Baoyou Xie
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 275c434..757c098 100644
--- a/MAINTAINERS
+++ b
This patch adds i2c controller driver for ZTE's zx2967 family.
Signed-off-by: Baoyou Xie
---
drivers/i2c/busses/Kconfig | 9 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-zx2967.c | 690
3 files changed, 700 insertions(+)
creat
Hi all,
Changes since 20170120:
The vfs tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 4596
5281 files changed, 169240 insertions(+), 99700 deletions(-)
I have created today'
Hello,
On Thu, Jan 19, 2017 at 10:59:03PM +0800, ys...@foxmail.com wrote:
> From: Yisheng Xie
>
> This patch is to extends soft offlining framework to support
> non-lru page, which already support migration after
> commit bda807d44454 ("mm: migrate: support non-lru movable page
> migration")
>
When regulator_get() tries to resolve a regulator supply but fail to
find a matching property in DeviceTree it returns a dummy regulator, if
a matching supply is specified but unavailable the regulator core will
return an error.
Based on this we should not ignore errors upon failing to acquire the
The error paths of the common qcom-ufs functions for registering the
phy, acquiring clocks and acquiring regulators all print specific error
messages before returning an error, so there is no value in printing yet
another - more generic - message when this occur.
Reviewed-by: Vivek Gautam
Reviewe
Upon failing to acquire regulator supplies the qcom-ufs driver calls
kfree() on the devm allocated memory used to store the name of the
regulator, leading to devres corruption.
Rather than switching to using the appropriate free function the patch
acknowledge the fact that "name" is always a const
The fact that a regulator is always-on is a property of the regulator,
not a specific consumer. Implementing this in the driver leads to a
system behaviour that is dependent on if the Qualcomm UFS PHY was ever
(partially) probed.
If the specific regulator should be always on in a particular device
On 23-01-17, 04:20, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: c497f8d17246720afe680ea1a8fa6e48e75af852
> commit: 33692dc381f9b89ddfc408631bf670ac2fd08ffc PM / OPP: Move opp core to
> its own directory
> date: 1 year,
On Sun, 2017-01-22 at 18:45 +0100, Mike Galbraith wrote:
> On Sun, 2017-01-22 at 09:46 +0100, Mike Galbraith wrote:
> > Greetings btrfs/lockdep wizards,
> >
> > RT trees have trouble with the BTRFS lockdep positive avoidance lock
> > class dance (see disk-io.c). Seems the trouble is due to RT not
From: Joel Stanley
The Aspeed SoCs have more GPIOs than can be represented with A-Z. The
documentation uses two letter names such as AA and AB, so make the names
a three-character array in the bank struct to accommodate this.
Signed-off-by: Joel Stanley
Signed-off-by: Andrew Jeffery
---
drive
Hi Linus,
This short series resolves a TODO comment in the Aspeed GPIO driver regarding
banks Y, Z, AA, AB and AC by implementing their support. It's a little involved
given some of the characteristics of these banks, but hopefully nothing too
controversial.
Cheers,
Andrew
Andrew Jeffery (1):
This is less straight-forward than one would hope, as some banks only
have 4 pins rather than 8, others are output only, yet more (W and
X, already supported) are input-only, and in the case of the g4 SoC bank
AC doesn't exist.
Add some structs to describe the varying properties of different banks
Incorrect video output configuration bits were being tested on pins in
GPIO banks AA and AB for the ROM{8,16} mux functions. The ROM{8,16}
functions are the highest priority for the relevant pins and also the
default function, so we require the relevant video output configuration
be disabled to mux
The Aspeed GPIO driver recently gained support for banks Y, Z, AA, AB and AC.
Update the devicetree so GPIO requests for these pins are routed via pinmux,
else the export succeeds but the GPIOs are non-functional.
Signed-off-by: Andrew Jeffery
---
arch/arm/boot/dts/aspeed-g5.dtsi | 2 +-
1 file
Peter Zijlstra writes:
> On Tue, Jan 17, 2017 at 02:07:36PM +0100, Vlastimil Babka wrote:
>
>> Anyway I'm not sure if this patch is safe. Hopefully Peter can judge
>> this better...
>>
>> > Cc: Vlastimil Babka
>> > Signed-off-by: Stafford Horne
>> > ---
>> > init/main.c | 3 +--
>> > 1 file c
On Wed, Jan 18, 2017 at 12:58:38PM +0900, Sergey Senozhatsky wrote:
> We had a deprecated_attr_warn() warning for 2 years and now the
> time has come and we finally can do the cleanup.
>
> The plan was as follows:
>
> : per-stat sysfs attributes are considered to be deprecated.
> : The basic stra
On Mon, Jan 23, 2017 at 01:47:20PM +0900, Minchan Kim wrote:
> Hello,
>
> When I look at first patch, I wanted to use increment loop but didn't
> tell to you because that small piece of code is no harmful for readbility
> to me so I want to keep author's code rather than pointing the trivial
> whi
Reviewed-by: Chris Zhong
On 01/22/2017 12:31 AM, John Keeping wrote:
Signed-off-by: John Keeping
---
Unchanged in v2
---
drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi.c
b/driv
Reviewed-by: Chris Zhong
On 01/22/2017 12:31 AM, John Keeping wrote:
In order to fully reset the state of the MIPI controller we must assert
this reset.
This is slightly more complicated than it could be in order to maintain
compatibility with device trees that do not specify the reset propert
On Sun, Jan 22, 2017 at 11:19 PM, Marcos Paulo de Souza
wrote:
> Change uint32_t to u32, solved the issue reported by checkpatch.pl:
>
> CHECK: Prefer kernel type 'u32' over 'uint32_t'
> + uint32_t *format, uint32_t *rate, u8 *channels,
>
> CHECK: Prefer kernel type 'u32' ove
i am not sure as well about reverse hurting cache.
On 2017/1/23 14:13, Joonsoo Kim wrote:
On Mon, Jan 23, 2017 at 01:47:20PM +0900, Minchan Kim wrote:
Hello,
When I look at first patch, I wanted to use increment loop but didn't
tell to you because that small piece of code is no harmful for rea
Runtime suspend shouldn't be executed if the tx queue is not empty,
because the device is not idle.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 0e99af0..e1466b
On (01/23/17 15:04), Minchan Kim wrote:
> On Wed, Jan 18, 2017 at 12:58:38PM +0900, Sergey Senozhatsky wrote:
> > We had a deprecated_attr_warn() warning for 2 years and now the
> > time has come and we finally can do the cleanup.
> >
> > The plan was as follows:
> >
> > : per-stat sysfs attribut
On Mon, Jan 23, 2017 at 01:03:47PM +0900, Sergey Senozhatsky wrote:
> On (01/23/17 11:58), Joonsoo Kim wrote:
> > Hello,
> >
> > On Sun, Jan 22, 2017 at 10:58:38AM +0800, zhouxianrong wrote:
> > > 1. memset is just set a int value but i want to set a long value.
> >
> > Sorry for late review.
> >
Robert Jarzmik writes:
> When the kernel is compiled with an "O=" argument, the object files are
> not necessarily in the source tree, and more probably in another tree.
>
> In this situation, the current used check doesn't work, and
> COMPILED_SOURCE tags is broken with O= builds.
>
> This patch
On Sun, Jan 22, 2017 at 10:58:38AM +0800, zhouxianrong wrote:
> 1. memset is just set a int value but i want to set a long value.
memset doesn't set an int value.
DESCRIPTION
The memset() function fills the first n bytes of the memory area
pointed to by s with the constant by
From: Christoph Hellwig [mailto:h...@lst.de]
> On Sun, Jan 22, 2017 at 06:39:28PM +, Matthew Wilcox wrote:
> > Two guests on the same physical machine (or a guest and a host) have access
> > to the same set of physical addresses. This might be an NV-DIMM, or it
> > might
> > just be DRAM (for
On Sat, 2017-01-21 at 11:20 -0800, Florian Fainelli wrote:
> We have a device reference, utilize it instead of pr_warn().
There is at least one more hwmon to convert in applesmc.c
Perhaps a coccinelle script?
Two questions for Julia Lawall:
o is there a better way to do this than repeat the blo
Yes, memset's prototype is int but
the implement of arch is unsigned char; for example, in arm64
.weak memset
ENTRY(__memset)
ENTRY(memset)
mov dst, dstin /* Preserve return value. */
and A_lw, val, #255
orr A_lw, A_lw, A_lw, lsl #8
orr
301 - 400 of 437 matches
Mail list logo
