On Sun, Jan 22, 2017 at 09:31:44AM +0800, Alex Shi wrote:
>
> >Yeah, that could be problematic. The code snippet gives the general idea but
> >it
> >could be changed by for example by a flag telling the cpus when they enter
> >idle
> >to update their state_count. Or something like that.
>
> Yes
Hi Magnus,
On Mon, Jan 23, 2017 at 12:40 PM, Magnus Damm wrote:
> From: Magnus Damm
>
> Bump up the maximum numbers of micro-TLBS to 48.
>
> Each IPMMU device instance get micro-TLB assignment via
> the "iommus" property in DT. Older SoCs tend to use a
> maximum number of 32 micro-TLBs per IPMMU
On Monday 23 January 2017 13:40:58 Pavel Machek wrote:
> It seems that battery driver stopped working on N900 between -rc4 and
> -rc5.
Which one of those 4 drivers stopped working?
--
Pali Rohár
pali.ro...@gmail.com
Hi!
It seems that battery driver stopped working on N900 between -rc4 and
-rc5.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horse
Hi Minchan,
Thanks for reviewing.
On 2017/1/23 13:14, Minchan Kim wrote:
> Hello,
>
> On Thu, Jan 19, 2017 at 10:59:03PM +0800, ys...@foxmail.com wrote:
>> From: Yisheng Xie
>>
>> @@ -1527,7 +1527,8 @@ static int get_any_page(struct page *page, unsigned
>> long pfn, int flags)
>> {
>> int
The current pinconf packed format allows only 16-bit argument limiting
the maximum value 65535. For most types this is enough. However,
debounce time can be in range of hundreths of milliseconds in case of
mechanical switches so we cannot represent the worst case using the
current format.
In order
When a GPIO driver is backed by a pinctrl driver the GPIO driver
sometimes needs to call the pinctrl driver to configure certain things,
like whether the pin is used as input or output. In addition to this
there are other configurations applicable to GPIOs such as setting
debounce time of the GPIO.
Currently we already have two pin configuration related callbacks
available for GPIO chips .set_single_ended() and .set_debounce(). In
future we expect to have even more, which does not scale well if we need
to add yet another callback to the GPIO chip structure for each possible
configuration para
This series makes it possible to configure pins from GPIO chip drivers by
implementing a new callback .set_config(). This callback replaces the
existing .set_single_ended() and .set_debounce() simply because adding new
callbacks for each possible configuration type does not scale. So instead
we re-
On Mon, Jan 16, 2017 at 01:23:30AM -0600, Suravee Suthikulpanit wrote:
> static void perf_iommu_read(struct perf_event *event)
> {
> - u64 count = 0ULL;
> - u64 prev_raw_count = 0ULL;
> - u64 delta = 0ULL;
> + u64 count, prev;
> + s64 delta;
I did send that email where I told
Am 23.01.2017 um 09:18 schrieb Matthew Wilcox :
> Clearly nobody ever tried to build the documentation for the radix tree
> before:
>
> include/linux/radix-tree.h:400: warning: cannot understand function
> prototype: 'void ** radix_tree_iter_init(struct radix_tree_iter *iter,
> unsigned long sta
On Mon, Jan 16, 2017 at 01:23:34AM -0600, Suravee Suthikulpanit wrote:
> From: Suravee Suthikulpanit
>
> In, perf_iommu_start(), we need to check the return value from
> amd_iommu_set_reg(). In case of failure, we should not enable the PMU.
>
> Also, in perf_iommu_read(), we need to check the re
From: Yasir-Khan
This patch adds xilinx uart loopback support by modifying the
cdns_uart_set_mctrl function to handle the switch to loopback mode.
After this patch, the loopback mode can be enabled/disabled by
setting/clearing the TIOCM_LOOP modem bit via TIOCMBIS/TIOCMBIC
ioctls respectively.
S
We get a lot of harmless warnings about this header file at W=1 level
because of an unusual function declaration:
kernel/trace/trace.h:766:1: error: 'inline' is not at beginning of declaration
[-Werror=old-style-declaration]
This moves the inline statement where it normally belongs, avoiding the
The of_node member in struct drm_bridge is hidden when CONFIG_OF
is disabled, causing a build error:
drivers/gpu/drm/bridge/dw-hdmi.c: In function '__dw_hdmi_probe':
drivers/gpu/drm/bridge/dw-hdmi.c:2063:14: error: 'struct drm_bridge' has no
member named 'of_node'
We could fix this either using
On 01/20/2017 03:12 AM, Stephen Boyd wrote:
On 01/19, Vivek Gautam wrote:
On 01/19/2017 06:10 AM, Stephen Boyd wrote:
Didn't we already move away from subnodes for lanes in an earlier
revision of these patches? I seem to recall we did that because
lanes are not devices and the whole "phy as a
On Mon, Jan 23, 2017 at 12:08:12PM +0100, SF Markus Elfring wrote:
> > but it certainly carries the risk of breaking something
>
> This is usual in software development, isn't it?
>
If you break something but you're trying to fix something then normally
you still end up fixing more than you brea
A bugfix introduced a new warning as it marked a function as __init
that is called by both __init and non-__init functions:
WARNING: vmlinux.o(.text.unlikely+0x1b26): Section mismatch in reference from
the function section_deactivate() to the function
.init.text:section_active_mask()
WARNING: vm
> -Original Message-
> From: Vineet Gupta [mailto:vgu...@synopsys.com]
> Sent: Tuesday, January 03, 2017 9:11 PM
> To: Yuriy Kolerov ; linux-snps-
> a...@lists.infradead.org
> Cc: alexey.brod...@synopsys.com; linux-kernel@vger.kernel.org;
> marc.zyng...@arm.com
> Subject: Re: [PATCH v3 3/
One line was apparently pasted incorrectly during a new feature patch:
drivers/net/phy/marvell.c:2090:15: error: initialized field overwritten
[-Werror=override-init]
.features = PHY_GBIT_FEATURES,
I'm removing the extraneous line here to avoid the W=1 warning and restore
the previous flags v
The __alloc_pages_slowpath() has gotten rather complex and gcc
is no longer able to follow the gotos and prove that the
alloc_flags variable is initialized at the time it is used:
mm/page_alloc.c: In function '__alloc_pages_slowpath':
mm/page_alloc.c:3565:15: error: 'alloc_flags' may be used unini
A cleanup caused a harmless warning:
drivers/pinctrl/mvebu/pinctrl-kirkwood.c: In function 'kirkwood_pinctrl_probe':
drivers/pinctrl/mvebu/pinctrl-kirkwood.c:460:19: error: unused variable 'res'
[-Werror=unused-variable]
The obvious fix is to remove the declaration of the now unused
variable.
F
On Mon, 23 Jan 2017, sean.w...@mediatek.com wrote:
> 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 ch
On Mon, 23 Jan 2017, sean.w...@mediatek.com wrote:
> 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 in
On Mon, 23 Jan 2017, Alexandre Belloni wrote:
> On 19/01/2017 at 13:30:31 +0100, Enric Balletbo i Serra wrote :
> > From: Stephen Barber
> >
> > On platforms with a Chrome OS EC, the EC can function as a simple RTC.
> > Add a basic driver with this functionality.
> >
> > Signed-off-by: Stephen
On Thu, 19 Jan 2017, Enric Balletbo i Serra wrote:
> From: Stephen Barber
>
> If the EC supports RTC host commands, expose an RTC device.
>
> Signed-off-by: Stephen Barber
> Signed-off-by: Enric Balletbo i Serra
> ---
> drivers/platform/chrome/cros_ec_dev.c | 22 ++
> 1 f
On Fri, 20 Jan 2017, Enric Balletbo i Serra wrote:
> From: Douglas Anderson
>
> Add the defines for the new buttons and switches connected to the CrosEC.
>
> Signed-off-by: Douglas Anderson
> Signed-off-by: Enric Balletbo i Serra
> ---
> include/linux/mfd/cros_ec_commands.h | 73
> +
Arm, IIO and PWM Maintainers,
Enjoy!
The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
ib-mfd-arm-iio-pwm-v4.10
for you
On 01/23, Oleg Nesterov wrote:
>
> Add the new helper to walk the process tree, the next patch adds a user.
> Note that it visits the group leaders only, proc_visitor can do
> for_each_thread itself or we can trivially extend walk_process_tree() to
> do this.
Please consider this patch as a prepar
>> We have got different preferences for the placement of error code settings.
> Yes we do, so what's the point? Both are OK.
Can a function implementation be executed a bit faster in the case
that error codes will usually only matter if they would be set after
a concrete software failure
> Plea
On Sun, Jan 22, 2017 at 06:28:06PM +0100, Nicolas Iooss wrote:
> Function sbridge_register_mci() sets pvt->info.show_interleave_mode to
> knl_show_interleave_mode() on Knight's Landing and
> show_interleave_mode() anywhere else. These functions are only called in
> a debug statement and knl_show_in
The only check there was done was a debugging check. Remove it and
replace the return value with void to reduce error checking.
Signed-off-by: Matias Bjørling
---
drivers/lightnvm/core.c | 41 +
1 file changed, 9 insertions(+), 32 deletions(-)
diff --git
The number of configuration groups has been limited to one in current
code, even if there is support for up to four. With the introduction
of the open-channel SSD 1.3 specification, only a single
group is exposed onwards. Reflect this in the nvm_id structure.
Signed-off-by: Matias Bjørling
---
d
A couple of patches. The first seven patches is cleanup patches, that
cleans up the codebase for when pblk is added to the kernel, and
prepare the code such that a device can be used as a normal block device
(as long as the access rules are respected).
The last patch adds ioctls for vectored I/Os,
Gratulálunk a nyerteseknek (ASA - CJ: SP / 11420/2 / EU 41..
Az Ön e-mail I D nyert 450,000.00Euro (450.000. Euro)
Spanyol Nemzetközi jótékonysági program "El Gordo. (. Ref: SP.EU/11420/2/41.)
A szerencsés számok 0/31/13/92/20.
Pontosítás és eljárás Kapcsolat;
S. C. biztonsági cég IRODA
A Kap
The nvm_submit_ppa* functions are no longer needed after gennvm and core
have been merged.
Signed-off-by: Matias Bjørling
---
drivers/lightnvm/core.c | 109 ---
include/linux/lightnvm.h | 4 --
2 files changed, 113 deletions(-)
diff --git a/drivers
Going from target specific ppa addresses to device was accomplished by
first converting target to generic ppa addresses and generic to device
addresses. The conversion was either open-coded or used the built-in
nvm_trans_* and nvm_map_* functions for conversion. Simplify the
interface and cleanup t
Enable user-space to issue vector I/O commands through ioctls. To issue
a vector I/O, the ppa list with addresses is also required and must be
mapped for the controller to access.
For each ioctl, the result and status bits are returned as well, such
that user-space can retrieve the open-channel SS
For the first iteration of Open-Channel SSDs, it was anticipated that
there could be various media managers on top of an open-channel SSD,
such to allow vendors to plug in their own host-side FTLs, without the
media manager in between.
Now that an Open-Channel SSD is exposed as a traditional block
On Sun, 22 Jan 2017, Joe Perches wrote:
> On Sun, 2017-01-22 at 22:43 -0800, Joe Perches wrote:
> > Two questions for Julia Lawall:
> >
> > o is there a better way to do this than repeat the blocks
> > one for each replacement
> > o can struct device * dev be made an arbitrary identifier
> >
>
Since the merge of gennvm and core, there is no longer a need for the
device specific bad block functions.
Signed-off-by: Matias Bjørling
---
drivers/lightnvm/core.c | 40
include/linux/lightnvm.h | 2 --
2 files changed, 4 insertions(+), 38 deletions(-
After gennvm and core have been merged, there are no more callers to
nvm_erase_ppa. Therefore collapse the device specific and target
specific erase functions.
Signed-off-by: Matias Bjørling
---
drivers/lightnvm/core.c | 57 ++--
include/linux/lightnv
Hi Will,
On 23/01/2017 12:46, Will Deacon wrote:
> [adding David Woodhouse, since he maintains this driver]
Thank you for adding David to the list.
Whoever is likely to pull this, please let me know if I need to respin
to add missed Will's Acked-by.
Thanks
Eric
>
> Will
>
> On Thu, Jan 19, 2
Hi,
Alan Stern writes:
> On Mon, 16 Jan 2017, Felipe Balbi wrote:
>
>> > The gadget driver never calls usb_ep_queue in order to receive the next
>> > SETUP packet; the UDC driver takes care of SETUP handling
>> > automatically.
>>
>> yeah, that's another thing I'd like to change. Currently, we
Add the new helper to walk the process tree, the next patch adds a user.
Note that it visits the group leaders only, proc_visitor can do
for_each_thread itself or we can trivially extend walk_process_tree() to
do this.
Signed-off-by: Oleg Nesterov
---
include/linux/sched.h | 3 +++
kernel/fork.
On 01/22, Pavel Tikhomirov wrote:
>
> >
> >Hmm. could you explain how this change helps CRIU? I mean, why
> >restorer can't do prctl(CHILD_SUBREAPER) before the first fork?
>
> Imagine we have these tree in pidns:
>
> 1: has_child_subreaper == 0 && is_child_subreaper == 0
> |-2: has_child_subreaper
On 23.1.2017 12:39, David Binderman wrote:
>
> Hello there,
>
> [linux-4.10-rc5/drivers/char/xilinx_hwicap/buffer_icap.c:301]: (style)
> Variable 'num_writes' is modified but its new value is never used.
> [linux-4.10-rc5/drivers/char/xilinx_hwicap/buffer_icap.c:356]: (style)
> Variable 'read_c
On Mon, 16 Jan 2017, Javier Martinez Canillas wrote:
> The I2C core always reports a MODALIAS of the form i2c: even if the
> device was registered via OF, this means that exporting the OF device ID
> table device aliases in the module is not needed. But in order to change
> how the core reports mo
Remove unused variables which generates these warnings:
[linux-4.10-rc5/drivers/char/xilinx_hwicap/buffer_icap.c:301]: (style)
Variable 'num_writes' is modified but its new value is never used.
[linux-4.10-rc5/drivers/char/xilinx_hwicap/buffer_icap.c:356]: (style)
Variable 'read_count' is modified
On Fri, 13 Jan 2017, Linus Walleij wrote:
> We didn't have proper device tree bindings for this clock,
> I standardized it to use the exact chipname so let's rename
> it "ab8500-clk" and rectify the device tree compatible string
> to "stericsson,ab8500-clk".
>
> Cc: Ulf Hansson
> Signed-off-by:
On 2017/1/23 9:30, John Hubbard wrote:
>
>
> 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, rem
On Fri, 13 Jan 2017, Thierry Escande wrote:
> From: Shawn Nematbakhsh
>
> pm_suspend_via_firmware() will return false for platforms with ACPI
> disabled and ACPI is a prerequisite for S0ix support.
>
> With this patch, sleep state event sent to EC is forced to S3 if ACPI is
> disabled.
>
> Sig
2017-01-23 12:45 GMT+01:00 Felipe Balbi :
>
> Hi,
>
> Richard Genoud writes:
>> On 19/01/2017 09:03, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Richard Genoud writes:
Hi,
Since commit c499ff71ff2a2 ("usb: dwc3: core: re-factor init and exit
paths")
(merged in 4.8), the usb ports
On Mon, Jan 23, 2017 at 11:00:15AM +0100, SF Markus Elfring wrote:
> >> @@ -1327,27 +1327,30 @@ static ssize_t tg_set_max(struct kernfs_open_file
> >> *of,
> >>break;
> >>ctx.body += len;
> >>
> >> - ret = -EINVAL;
> >>p = tok;
> >>
From: Magnus Damm
Update the IPMMU DT binding documentation to include the r8a7796 compat
string for R-Car M3-W.
Signed-off-by: Magnus Damm
Acked-by: Laurent Pinchart
Acked-by: Rob Herring
Acked-by: Simon Horman
Acked-by: Geert Uytterhoeven
---
Previously posted separately as
[PATCH v3]
From: Magnus Damm
Bump up the maximum numbers of micro-TLBS to 48.
Each IPMMU device instance get micro-TLB assignment via
the "iommus" property in DT. Older SoCs tend to use a
maximum number of 32 micro-TLBs per IPMMU instance however
newer SoCs such as r8a7796 make use of up to 48 micro-TLBs.
From: Magnus Damm
Support the r8a7796 IPMMU by sharing feature flags between
r8a7795 and r8a7796. Also update IOMMU_OF_DECLARE to hook
up the updated compat string.
Signed-off-by: Magnus Damm
---
Changes since V1:
- None
drivers/iommu/ipmmu-vmsa.c |9 +++--
1 file changed, 7 insert
On Sat, Jan 21, 2017 at 1:53 AM, Andy Lutomirski wrote:
> On Fri, Jan 20, 2017 at 8:33 AM, Djalal Harouni wrote:
>> On Thu, Jan 19, 2017 at 8:52 PM, Andy Lutomirski wrote:
>>> On Thu, Jan 19, 2017 at 5:53 AM, Djalal Harouni wrote:
>> [...]
Sure, the hidepid mount option is old enough, and
[adding David Woodhouse, since he maintains this driver]
Will
On Thu, Jan 19, 2017 at 08:57:53PM +, Eric Auger wrote:
> This patch registers the [FEE0_h - FEF0_000h] 1MB MSI
> range as a reserved region and RMRR regions as direct regions.
>
> This will allow to report those reserved regi
iommu/ipmmu-vmsa: r8a7796 support V2
[PATCH v2 1/3] iommu/ipmmu-vmsa: Add r8a7796 DT binding
[PATCH v2 2/3] iommu/ipmmu-vmsa: Increase maximum micro-TLBS to 48
[PATCH v2 3/3] iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code
This series adds r8a7796 support to the IPMMU driver. The DT binding
ge
Hi,
Richard Genoud writes:
> On 19/01/2017 09:03, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Richard Genoud writes:
>>> Hi,
>>> Since commit c499ff71ff2a2 ("usb: dwc3: core: re-factor init and exit
>>> paths")
>>> (merged in 4.8), the usb ports on odroid-XU4 don't work anymore.
>>>
>>> [ Actually,
On Thu, Jan 19, 2017 at 08:57:55PM +, Eric Auger wrote:
> The get() populates the list with the MSI IOVA reserved window.
>
> At the moment an arbitray MSI IOVA window is set at 0x800
> of size 1MB. This will allow to report those info in iommu-group
> sysfs.
>
> Signed-off-by: Eric Auger
Hi Roger,
On 2017년 01월 23일 20:19, Roger Quadros wrote:
> - Some SoC's (e.g. Qualcomm MSM) do not have the OTG controller block
> but do have both host and peripheral controllers and so can operate
> in dual role mode. Current series does not address this case.
> We can get dual-role to work with s
On Mon, 16 Jan 2017, Javier Martinez Canillas wrote:
> Hello Chanwoo,
>
> Thanks for the review.
>
> On 01/16/2017 03:46 AM, Chanwoo Choi wrote:
> > Hi,
> >
> > I think that this patch better to squash with patch3.
> > After applying the patch3, this driver doesn't use
> > the max77686_i2c_id t
On Fri, 13 Jan 2017, Javier Martinez Canillas wrote:
> The driver is only used in DT platforms so there's no need to
> have an i2c_device_id table.
>
> Signed-off-by: Javier Martinez Canillas
> Acked-by: Laxman Dewangan
> Reviewed-by: Krzysztof Kozlowski
> Tested-by: Krzysztof Kozlowski
>
>
On Mon, Jan 23, 2017 at 7:24 PM, Wei-Ning Huang wrote:
> On Tue, Nov 8, 2016 at 2:08 PM, Yong Mao wrote:
>> From: yong mao
>>
>> 1. Add irqlock to protect accessing the shared register
>> 2. Modify the implementation of msdc_card_busy due to SDIO
>> 3. Implement enable_sdio_irq
>> 4. Add msdc_re
On Fri, 13 Jan 2017, Javier Martinez Canillas wrote:
> If a driver is only used in DT platforms, there's no need to get the
> i2c_device_id as an argument of the probe function. Since this data
> can be get from the matching of_device_id.
>
> There's a temporary .probe_new field in struct i2c_dri
On Fri, 13 Jan 2017, Javier Martinez Canillas wrote:
> The driver is only used in platforms that have DT support so always the
> I2C device .data will be get from the matched OF node and never will be
> from the I2C device ID table.
>
> Signed-off-by: Javier Martinez Canillas
> Acked-by: Laxman
On Fri, 13 Jan 2017, Javier Martinez Canillas wrote:
> Use the generic helper to get the matched of_device_id .data, instead of
> open coding it.
>
> The driver was checking if matching the OF node with the driver's OF table
> was failing, but this doesn't make too much sense since this can't hap
On Mon, Jan 23, 2017 at 10:47:44AM +0100, Thomas Gleixner wrote:
> So again:
>
> Can please everyone involved write up their specific requirements
> for CQM and stop spamming us with half baken design proposals?
>
> And I mean abstract requirements and not again something which is
> refe
On Thu, 12 Jan 2017, Javier Martinez Canillas wrote:
> The driver is only used in platforms that have DT support so always the
> I2C device .data will be get from the matched OF node and never will be
> from the I2C device ID table.
>
> Signed-off-by: Javier Martinez Canillas
> ---
>
> drivers
Hi,
On Fri, 20 Jan 2017 15:08:57 +0900, Jaehoon Chung wrote:
> On 01/17/2017 10:38 PM, Romain Perier wrote:
> > In my case I can reproduce the issue on the rock2 and the firefly-rk3288. A
> > workaround is to
> >
> > comment the line ".pm = <&pm_ops_foo>" .
>
> Sorry for late. I'm checking ru
On Tue, Nov 8, 2016 at 2:08 PM, Yong Mao wrote:
> From: yong mao
>
> 1. Add irqlock to protect accessing the shared register
> 2. Modify the implementation of msdc_card_busy due to SDIO
> 3. Implement enable_sdio_irq
> 4. Add msdc_recheck_sdio_irq mechanism to make sure all
>interrupts can be
On Wednesday 14 December 2016 01:06 PM, Ingo Molnar wrote:
> * Alexis Berlemont wrote:
>
>> Hi Masami,
>>
>> Many thanks for your mail.
>>
>> Here is another patch set which tries to fix the points you mentioned:
>>
>> * Skip the arguments containing a constant ($123);
>> * Review the code in c
USB port is micro-AB type and can function as peripheral
as well as host. Enable dual-role mode for USB2.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/am57xx-idk-common.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/am57xx-idk-common.dtsi
b/arch
Add OTG and GHWPARAMS6 register definitions
Signed-off-by: Roger Quadros
---
drivers/usb/dwc3/core.h | 82 +
1 file changed, 82 insertions(+)
diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
index d514dca..fc82d2e 100644
--- a/driver
Hi Christoffer,
Christoffer Dall writes:
> On Wed, Jan 18, 2017 at 06:05:46PM +, Mark Rutland wrote:
>> On Wed, Jan 18, 2017 at 04:17:18PM +, Punit Agrawal wrote:
>> > Mark Rutland writes:
>> >
>> > > On Wed, Jan 18, 2017 at 02:51:31PM +, Punit Agrawal wrote:
>> > >> I should've cl
If usb/otg-fsm.h and usb/composite.h are included together
then it results in the build warning [1].
Prevent that by defining VDBG locally.
Also get rid of MPC_LOC which doesn't seem to be used
by anyone.
[1] - warning fixed by this patch:
In file included from drivers/usb/dwc3/core.h:33,
fr
Hi,
We rely on the OTG controller block to provide us with
VBUS and ID line status via an interrupt.
This is then used to switch the controller between host, peripheral
and idle roles based on the following table.
ID VBUSdual-role state
-- ---
0 x A_
To avoid checkpatch warnings with new patches let's
start using the BIT() macro wherever possible.
Signed-off-by: Roger Quadros
---
drivers/usb/dwc3/core.h | 192 +--
drivers/usb/dwc3/dwc3-omap.c | 48 +--
drivers/usb/dwc3/gadget.h| 20 +
USB1 port is micro-AB type and can function as peripheral
as well as host. Enable dual-role mode for USB1.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/am437x-gp-evm.dts | 2 +-
arch/arm/boot/dts/am437x-sk-evm.dts | 2 +-
arch/arm/boot/dts/am43x-epos-evm.dts | 2 +-
3 files changed, 3 in
If dr_mode is "otg" then support dual role mode of operation.
Get ID and VBUS information from the OTG controller
and put the controller in the appropriate state.
This is our dual-role state table.
ID VBUSdual-role state
-- ---
0 x A_HOST - Host cont
We need to break from all cases if we want to treat
each one of them separately.
Fixes: d2728fb3e01f ("usb: dwc3: omap: Pass VBUS and ID events transparently")
Signed-off-by: Roger Quadros
---
drivers/usb/dwc3/dwc3-omap.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/dwc3/dwc3-
USB1 port is micro-AB type and can function as peripheral
as well as host. Enable dual-role mode for USB1.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/dra7-evm.dts | 2 +-
arch/arm/boot/dts/dra72-evm-common.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
On Fri, Jan 20, 2017 at 04:02:56PM +0100, Vlastimil Babka wrote:
> On 01/17/2017 10:29 AM, Mel Gorman wrote:
>
> [...]
>
> > @@ -1244,10 +1243,8 @@ static void __free_pages_ok(struct page *page,
> > unsigned int order)
> > return;
> >
> > migratetype = get_pfnblock_migratetype(
Hi Steve,
On Sun, 2017-01-22 at 18:31 -0800, Steve Longerbeam wrote:
>
> 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 directl
On Sat, 21 Jan 2017, Zhihui Zhang wrote:
> Sure, I believe that comments should always match the code. In this
That's fine.
> case, using either LVL_SIZE - 1 or LVL_SIZE is fine based on my
> understanding about 20 days ago. But I could be wrong and miss some
> subtle details. Anyway, my point i
This patch will update dsi clock control method.
1. dsi non-continue clock mode will enhance antistatic effect for panel
2. EOT packet control will judge whether dsi send end of packet or not
by customize
Signed-off-by: shaoming chen
Signed-off-by: YT Shen
Acked-by: CK Hu
---
drivers/gpu/drm/m
On 01/23/2017 12:00 PM, Philipp Zabel wrote:
> On Fri, 2017-01-20 at 21:39 +0100, Hans Verkuil wrote:
> [...]
>>> There is a VDIC entity in the i.MX IPU that performs de-interlacing with
>>> hardware filters for motion compensation. Some of the motion compensation
>>> modes ("low" and "medium" moti
This patch add support for the Mediatek MT2701 DISP subsystem.
There is only one OVL engine in MT2701.
Signed-off-by: YT Shen
Acked-by: CK Hu
---
drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 8
drivers/gpu/drm/mediatek/mtk_disp_rdma.c| 6 ++
drivers/gpu/drm/mediatek/mtk_drm_
This patch update enable/disable flow of DSI module.
Original flow works on there is a bridge chip: DSI -> bridge -> panel.
In this case: DSI -> panel, the DSI sub driver flow should be updated.
We need to initialize DSI first so that we can send commands to panel.
Signed-off-by: shaoming chen
Si
> Patches that changes open coded things to common helpers or things like
> kmalloc_array where appropriate or things that make the code more robust
> are fine and welcome, but I am not going to take this as it just shuffles
> things around.
Thanks for such information.
> It does not fix anythin
From: shaoming chen
add dsi interrupt control
Signed-off-by: shaoming chen
Acked-by: CK Hu
---
drivers/gpu/drm/mediatek/mtk_dsi.c | 92 ++
1 file changed, 92 insertions(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_dsi.c
b/drivers/gpu/drm/mediatek/mtk_dsi.
From: shaoming chen
add dsi read/write commands for transfer function
Signed-off-by: shaoming chen
Acked-by: CK Hu
---
drivers/gpu/drm/mediatek/mtk_dsi.c | 168 -
1 file changed, 166 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/mediatek/mtk_d
update connections for OVL, RDMA, BLS, DSI
Signed-off-by: YT Shen
Acked-by: CK Hu
---
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp.c
b/drivers/gpu/drm/mediatek/mtk_drm_ddp.c
index b77d
cleaning up unused define and refine function name and variable
Signed-off-by: shaoming chen
Signed-off-by: YT Shen
Acked-by: CK Hu
---
drivers/gpu/drm/mediatek/mtk_dsi.c | 73 --
drivers/gpu/drm/mediatek/mtk_mipi_tx.c | 8 ++--
2 files changed, 39 insertio
Add BLS component for PWM + GAMMA function
Signed-off-by: YT Shen
Acked-by: CK Hu
---
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 5 -
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 2 ++
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp_com
We need to acquire mutex before using the resources,
and need to release it after finished.
So we don't need to write registers in the blanking period.
Signed-off-by: YT Shen
Acked-by: CK Hu
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 75 -
drivers/gpu/drm/medi
There are some hardware settings changed, between MT8173 & MT2701:
DISP_OVL address offset changed, color format definition changed.
DISP_RDMA fifo size changed.
DISP_COLOR offset changed.
MIPI_TX pll setting changed.
And add prefix for mtk_ddp_main & mtk_ddp_ext & mutex_mod.
Signed-off-by: YT She
Add decriptions about supported chips, including MT2701 & MT8173
Signed-off-by: YT Shen
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 ++
Documentation/devicetree/bindings/display/mediatek/mediatek,dsi.txt | 2 ++
2 files changed, 4 insertio
601 - 700 of 823 matches
Mail list logo
