On Mon, Sep 07, 2020 at 12:14:59AM +0200, Arnd Bergmann wrote:
> I've had a first pass at this now, see
>
> https://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git/log/?h=arm-kill-set_fs
>
> There are a couple of things in there that ended up uglier than I was
> hoping for, and it's
The following commit has been merged into the core/build branch of tip:
Commit-ID: 6e0bf0e0e55000742a53c5f3b58f8669e0091a11
Gitweb:
https://git.kernel.org/tip/6e0bf0e0e55000742a53c5f3b58f8669e0091a11
Author:Kees Cook
AuthorDate:Tue, 01 Sep 2020 19:53:47 -07:00
Committer:
The following commit has been merged into the core/build branch of tip:
Commit-ID: 83109d5d5fba7abf362f5a443c9f4c4ea10bbc8d
Gitweb:
https://git.kernel.org/tip/83109d5d5fba7abf362f5a443c9f4c4ea10bbc8d
Author:Kees Cook
AuthorDate:Tue, 01 Sep 2020 19:53:46 -07:00
Committer:
The following commit has been merged into the core/build branch of tip:
Commit-ID: 5a17850e251a55bba6d65aefbfeacfa9888cd2cd
Gitweb:
https://git.kernel.org/tip/5a17850e251a55bba6d65aefbfeacfa9888cd2cd
Author:Kees Cook
AuthorDate:Tue, 01 Sep 2020 19:53:44 -07:00
Committer:
The following commit has been merged into the core/build branch of tip:
Commit-ID: b3e5d80d0c48c0cc7bce56473672f4e6e1210910
Gitweb:
https://git.kernel.org/tip/b3e5d80d0c48c0cc7bce56473672f4e6e1210910
Author:Kees Cook
AuthorDate:Tue, 01 Sep 2020 19:53:43 -07:00
Committer:
The following commit has been merged into the core/build branch of tip:
Commit-ID: 4409d2f8dfe7d5088567d4ba00133f876ee586c7
Gitweb:
https://git.kernel.org/tip/4409d2f8dfe7d5088567d4ba00133f876ee586c7
Author:Kees Cook
AuthorDate:Tue, 01 Sep 2020 19:53:45 -07:00
Committer:
Paul Cercueil writes:
> Use the newly introduced pm_ptr() macro, and mark the suspend/resume
> functions __maybe_unused. These functions can then be moved outside the
> CONFIG_PM_SUSPEND block, and the compiler can then process them and
> detect build failures independently of the config. If
On Fri, Sep 04, 2020 at 04:36:39PM -0600, Rob Herring wrote:
> On Fri, Sep 4, 2020 at 9:25 AM Krzysztof Kozlowski wrote:
> >
> > Driver requires different amount of clocks for different SoCs. Describe
> > these requirements properly to fix dtbs_check warnings like:
> >
> >
On Mon, Sep 07, 2020 at 11:17:58AM +0530, Yash Shah wrote:
> Add a driver to manage the Cadence DDR controller present on SiFive SoCs
> At present the driver manages the EDAC feature of the DDR controller.
> Additional features may be added to the driver in future to control
> other aspects of the
On 04-09-20, 10:43, Ionela Voinescu wrote:
> Do you know why it was designed this way in the first place?
No.
> I assumed it was designed like this (per-cpu cppc_cpudata structures) to
> allow for the future addition of support for the HW_ALL CPPC coordination
> type. In that case you can still
Hi Marc.
I am interested in this feature.
I have confirmed this patch works fine on Fujitsu FX1000. Thanks for creating
it.
I look forward to the day when this patch is merged.
We plan to post a patch that implements IPI for CPU stop Interrupt (for crash
dump) with pseudo NMI.
Tested-by:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f4d51dffc6c01a9e94650d95ce0104964f8ae822
commit: a66cbdd6573db8515735d37793c22605432c346d mt76: mt7615: introduce
mt7663s support
date: 7 weeks ago
config: ia64-randconfig-s032-20200907 (attached
On Fri, Sep 04, 2020 at 05:45:12PM -0700, Moritz Fischer wrote:
> Hi Xu,
>
> On Wed, Aug 19, 2020 at 03:45:21PM +0800, Xu Yilun wrote:
> > This patch adds support for the Nios handshake private feature on Intel
> > PAC (Programmable Acceleration Card) N3000.
> >
> > The Nios is the embedded
On Sat, Sep 05, 2020 at 11:05:48AM +0530, Anup Patel wrote:
> Your patch will also break if the SOC specific timer has a 32bit
> free-running counter
> unlike the 64bit free-running counter found on CLINT.
>
> I guess it's better to let the SOC timer driver provide the
> method/function to read
On Mon, Sep 07, 2020 at 12:34:37AM +0200, Rasmus Villemoes wrote:
> On 03/09/2020 17.59, Christoph Hellwig wrote:
> > Christophe reported a major speedup due to avoiding the iov_iter
> > overhead, so just add this trivial function. Note that /dev/zero
> > already implements both an iter and
Hi,
Wesley Cheng writes:
> diff --git a/drivers/usb/dwc3/ep0.c b/drivers/usb/dwc3/ep0.c
> index 59f2e8c31bd1..456aa87e8778 100644
> --- a/drivers/usb/dwc3/ep0.c
> +++ b/drivers/usb/dwc3/ep0.c
> @@ -197,7 +197,7 @@ int dwc3_gadget_ep0_queue(struct usb_ep *ep, struct
> usb_request *request,
>
Resend with new subject.
---8<---
The sa2ul driver uses crypto_authenc_extractkeys and therefore
must select CRYPTO_AUTHENC.
Fixes: 7694b6ca649f ("crypto: sa2ul - Add crypto driver")
Reported-by: kernel test robot
Signed-off-by: Herbert Xu
diff --git a/drivers/crypto/Kconfig
On Sun, Sep 06, 2020 at 04:52:24PM +0800, kernel test robot wrote:
>
> >> drivers/crypto/allwinner/sun4i-ss/sun4i-ss-hash.c:483:35: sparse: sparse:
> >> incorrect type in assignment (different base types) @@ expected
> >> unsigned int [assigned] [usertype] v @@ got restricted __le32
>
> From: Thomas Gleixner
> Sent: Friday, July 17, 2020 6:03 AM
> [...]
Hi, I'm very sorry for this extremely late reply -- I was sidetracked by
something
else and I just had a chance to revisit the issue. Thank you tglx for the
comments
and suggestions, which I think are reasonable. I realized
When a netdev down event occurs after a successful call to
j1939_sk_bind(), j1939_netdev_notify() can handle it correctly.
But if the netdev already in down state before calling j1939_sk_bind(),
j1939_sk_release() will stay in wait_event_interruptible() blocked
forever. Because in this case,
Please review this patch-series.
Thank you
Vaibhav Gupta
When initializing call virtio_max_dma_size() to figure the scatter list
limit. Needed to make virtio-gpu work properly with SEV.
v2: place max_segment in drm driver not gem object.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_kms.c | 1 +
1 file changed, 1 insertion(+)
Add max_segment argument to drm_prime_pages_to_sg(). When set pass it
through to the __sg_alloc_table_from_pages() call, otherwise use
SCATTERLIST_MAX_SEGMENT.
Also add max_segment field to drm driver and pass it to
drm_prime_pages_to_sg() calls in drivers and helpers.
v2: place max_segment in
On 9/7/2020 11:52 AM, Herbert Xu wrote:
Resend with new subject.
Thanks Herbert.
Reviewed-by: Keerthy
---8<---
The sa2ul driver uses crypto_authenc_extractkeys and therefore
must select CRYPTO_AUTHENC.
Fixes: 7694b6ca649f ("crypto: sa2ul - Add crypto driver")
Reported-by: kernel
On 4/09/20 8:43 am, Ian Rogers wrote:
> On Tue, Aug 4, 2020 at 8:50 AM Ian Rogers wrote:
>> On Tue, Aug 4, 2020 at 7:49 AM Adrian Hunter wrote:
>>> On 4/08/20 4:33 pm, Ian Rogers wrote:
On Tue, Aug 4, 2020 at 3:08 AM Adrian Hunter
wrote:
> On 28/07/20 11:57 am, Ian Rogers wrote:
Changeset 2b7aadd3b9e1 ("wlcore: Adding suppoprt for IGTK key in wlcore driver")
added support for AEC CMAC cipher suite.
However, this only works with the very newest firmware version
(8.9.0.0.83). Such firmware weren't even pushed to linux-firmware
git tree yet:
> > + /**
> > +* @max_segment:
> > +*
> > +* Max size for scatter list segments. When unset the default
> > +* (SCATTERLIST_MAX_SEGMENT) is used.
> > +*/
> > + size_t max_segment;
>
> Is there no better place for this then "at the bottom"? drm_device is a
> huge
On 9/6/20 6:25 PM, Jiri Olsa wrote:
> On Sun, Sep 06, 2020 at 04:50:02PM +0530, Kajol Jain wrote:
>
> SNIP
>
>> typedef int (*func)(void *data, struct json_event *je);
>>
>> int eprintf(int level, int var, const char *fmt, ...)
>> @@ -355,6 +368,8 @@ static int
Patchset enhance current runtime parameter support. It introduces new
fields like "PerChip" and "PerCore" similar to the field "PerPkg" which is
used to specify perpkg events.
The "PerCore" and "PerChip" specifies whether its core or chip events.
Based on which we can decide which runtime
Initially, every time we want to add new terms like chip, core thread etc,
we need to create corrsponding fields in pmu_events and event struct.
This patch adds an enum called 'aggr_mode_class' which store all these
aggregation like perchip/percore. It also adds new field 'aggr_mode'
to capture
This patch removes jevents.h and makes json_events function static.
Signed-off-by: Kajol Jain
Reviewed-by: John Garry
---
tools/perf/pmu-events/jevents.c | 3 +--
tools/perf/pmu-events/jevents.h | 23 ---
2 files changed, 1 insertion(+), 25 deletions(-)
delete mode 100644
This patch adds new structure called 'json_event' inside jevents.c
file to improve the callback prototype inside jevent files.
Initially, whenever user want to add new field, they need to update
in all function callback which make it more and more complex with
increased number of parmeters.
With
This patch adds passing of pmu_event as a parameter in function
'arch_get_runtimeparam' which can be used to get details like
if the event is percore/perchip.
Signed-off-by: Kajol Jain
Acked-by: Ian Rogers
---
tools/perf/arch/powerpc/util/header.c | 7 +--
tools/perf/util/metricgroup.c
This patch adds hv_24x7 core level events in nest_metric.json file
and also add PerChip/PerCore field in metric events.
Result:
power9 platform:
command:# ./perf stat --metric-only -M PowerBUS_Frequency -C 0 -I 1000
1.706011.92.0
On Fri 04-09-20 12:21:34, Andrew Morton wrote:
> On Fri, 4 Sep 2020 07:47:45 +0200 David Hildenbrand wrote:
[...]
> @@ -1589,9 +1567,7 @@ int __ref offline_pages(unsigned long st
> reason = "failure to dissolve huge pages";
> goto
On Mon, Sep 07, 2020 at 12:01:53PM +0530, Vaibhav Gupta wrote:
> Please review this patch-series.
I see no patch here :(
On Mon, Sep 07, 2020 at 12:03:47PM +0530, Vaibhav Gupta wrote:
>
Why did you send empty emails out?
greg k-h
> +static bool
> +xfs_is_write_fault(
> + struct vm_fault *vmf)
> +{
> + return vmf->flags & FAULT_FLAG_WRITE && vmf->vma->vm_flags & VM_SHARED;
> +}
This function does not look xfs specific at all. Why isn't it it in
fs.h? While we're at it the name sounds rather generic, and
Hi Iskren,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on b36c969764ab12faebb74711c942fa3e6eaf1e96]
url:
https://github.com/0day-ci/linux/commits/Iskren-Chernev/power-supply-max17040-support-compatible-devices/20200907-112145
base
On Thu, 2020-09-03 at 18:21 +0200, Greg Kroah-Hartman wrote:
> On Tue, Aug 04, 2020 at 09:59:09PM +0800, Frankie Chang wrote:
> >
> > Frankie.Chang (3):
> > binder: move structs from core file to header file
> > binder: add trace at free transaction.
> > binder: add transaction latency
On 07/09/2020 08.20, Christoph Hellwig wrote:
> On Mon, Sep 07, 2020 at 12:34:37AM +0200, Rasmus Villemoes wrote:
>> On 03/09/2020 17.59, Christoph Hellwig wrote:
>
>>> +static ssize_t read_zero(struct file *file, char __user *buf,
>>> +size_t count, loff_t *ppos)
>>> +{
>>> +
On Mon, Sep 07, 2020 at 08:48:10AM +0200, Greg KH wrote:
> On Mon, Sep 07, 2020 at 12:03:47PM +0530, Vaibhav Gupta wrote:
> >
>
> Why did you send empty emails out?
>
> greg k-h
I was trying to re-ping the patches. Guess it went empty. I will send patches
again.
Vaibhav
Fixed checkpatch warnings two warnings still exits about DT
compatible strings appers undocumented. Fixed the other codestyle
errors, and some warnings about use of volatile and un-necessary
out of memory errors.
Signed-off-by: Naveen Panwar
---
drivers/staging/ralink-gdma/ralink-gdma.c | 29
On Mon, Sep 07, 2020 at 02:49:29PM +0800, Frankie Chang wrote:
> On Thu, 2020-09-03 at 18:21 +0200, Greg Kroah-Hartman wrote:
> > On Tue, Aug 04, 2020 at 09:59:09PM +0800, Frankie Chang wrote:
> > >
> > > Frankie.Chang (3):
> > > binder: move structs from core file to header file
> > >
On Mon, Sep 07, 2020 at 12:27:45PM +0530, Naveen Panwar wrote:
> Fixed checkpatch warnings two warnings still exits about DT
> compatible strings appers undocumented. Fixed the other codestyle
> errors, and some warnings about use of volatile and un-necessary
> out of memory errors.
>
>
On Thu, Sep 03, 2020 at 09:18:37PM +0100, Tom Murphy wrote:
> Disable combining sg segments in the dma-iommu api.
> Combining the sg segments exposes a bug in the intel i915 driver which
> causes visual artifacts and the screen to freeze. This is most likely
> because of how the i915 handles the
On Wed, Aug 19, 2020 at 4:47 PM Damien Le Moal wrote:
>
> On 2020/08/19 19:32, Kanchan Joshi wrote:
> > On Wed, Aug 19, 2020 at 3:08 PM Damien Le Moal
> > wrote:
> >>
> >> On 2020/08/19 18:27, Kanchan Joshi wrote:
> >>> On Tue, Aug 18, 2020 at 12:46 PM Christoph Hellwig wrote:
>
> On
On Fri, 4 Sep 2020 at 18:50, Heinrich Schuchardt wrote:
>
> In the memory map the regions with the lowest addresses may be of type
> EFI_RESERVED_TYPE. The reserved areas may be discontinuous relative to the
> rest of the memory. So for calculating the maximum loading address for the
> device
On Fri, Aug 14, 2020 at 1:44 PM h...@infradead.org wrote:
>
> On Wed, Aug 05, 2020 at 07:35:28AM +, Damien Le Moal wrote:
> > > the write pointer. The only interesting addition is that we also want
> > > to report where we wrote. So I'd rather have RWF_REPORT_OFFSET or so.
> >
> > That
Hi James,
On 05.09.2020 17:50, James Bottomley wrote:
> [resend with correct linux-arch address]
> On Sat, 2020-09-05 at 15:35 +0800, Hillf Danton wrote:
>> On Fri, 04 Sep 2020 08:34:39 -0700 James Bottomley wrote:
>>> On Fri, 2020-09-04 at 23:25 +0800, Hillf Danton wrote:
The DMA buffer
Drivers using legacy PCI power management .suspend()/.resume() callbacks
have to manage PCI states and device's PM states themselves. They also
need to take care of standard configuration registers.
Switch to generic power management framework using a "struct dev_pm_ops"
variable to take the
Fixes commit 42ddb453a0cd ("radeon: Conditionally compile PM code")
Before the above mentioned patch, codes between the line number 547 and
2803 were already inside "#ifdef CONFIG_PM" container. Thus, addition of
"#if defined(CONFIG_PM)" was not required in the patch. It also affected
the "#ifdef
Linux Kernel Mentee: Remove Legacy Power Management.
The original goal of the patch series is to upgrade the power management
framework of radeonfb fbdev driver. This has been done by upgrading .suspend()
and .resume() callbacks.
The upgrade makes sure that the involvement of PCI Core does not
From: Frank Wunderlich
port6 of mt7530 switch (= cpu port 0) on bananapi-r2 misses pause option
which causes rx drops on running iperf.
Cc: sta...@vger.kernel.org
Fixes: f4ff257cd160 ("arm: dts: mt7623: add support for Bananapi R2 (BPI-R2)
board")
Signed-off-by: Frank Wunderlich
---
Hi Randy,
On Sun, Sep 06, 2020 at 12:33:08PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix build errors in Microblaze when CONFIG_MEMORY_ISOLATION is not
> set/enabled by adding stubs for 3 missing functions.
I've tried to follow Kconfig dependencies to see how could we have both
On Thu, Sep 03, 2020 at 06:56:32PM +0200, Andreas Gruenbacher wrote:
> When a direct I/O write falls back to buffered I/O entirely, dio->size
> will be 0 in iomap_dio_complete. Function invalidate_inode_pages2_range
> will try to invalidate the rest of the address space. If there are any
> dirty
[Widening the CC to include Andrew and linux-fsdevel@]
[Milan: thanks for the patch, but it's unclear to me from your commit
message how/if you verified the details.]
Andrew, maybe you (or someone else) can comment, since long ago your
commit f79e2abb9bd452d97295f34376dedbec9686b986
On Fri, Sep 04, 2020 at 02:46:53PM +0530, Ritesh Harjani wrote:
> After moving ext4's bmap to iomap interface, swapon functionality
> on files created using fallocate (which creates unwritten extents) are
> failing. This is since iomap_bmap interface returns 0 for unwritten
> extents and thus
On 05/09/2020 at 10:21, Parshuram Thombare wrote:
PAE bit of NCFGR register, when set, pauses transmission
if a non-zero 802.3 classic pause frame is received.
Fixes: 7897b071ac3b ("net: macb: convert to phylink")
Signed-off-by: Parshuram Thombare
For the record:
Acked-by: Nicolas Ferre
mlx5_suspend()/resume() keep the network interface, so during hibernation
netvsc_unregister_vf() and netvsc_register_vf() are not called, and hence
netvsc_resume() should call netvsc_vf_changed() to switch the data path
back to the VF after hibernation. Note: after we close and re-open the
vmbus
On Mon, Sep 7, 2020 at 8:39 AM Gerd Hoffmann wrote:
>
> > > + /**
> > > +* @max_segment:
> > > +*
> > > +* Max size for scatter list segments. When unset the default
> > > +* (SCATTERLIST_MAX_SEGMENT) is used.
> > > +*/
> > > + size_t max_segment;
> >
> > Is there no
On Fri, Sep 04, 2020 at 04:48:07PM +0200, Bean Huo wrote:
> From: Bean Huo
>
> Current generic_file_buffered_read() will break up the larger batches of pages
> and read data in single page length in case of ra->ra_pages == 0. This patch
> is
> to allow it to pass the batches of pages down to
On Fri, Sep 04, 2020 at 12:37:19PM -0700, Joe Perches wrote:
> On Fri, 2020-09-04 at 11:10 +, Corentin Labbe wrote:
> > This patch fix a double empty line issue reported by checkpatch.
> > While at it, since now the maximum line length is now 100, reorder some
> > wrapped line.
> []
> > diff
On Mon, Sep 07, 2020 at 09:16:17AM +0200, Corentin Labbe wrote:
>
> Oh I saw the increase in checkpatch.pl but didnt saw that it was still 80 in
> coding-style.rst.
> Anyway as maintainer of this driver, I prefer unwrapped lines.
>
> I let Herbert to choose to apply the serie without this last
On Sat, Sep 05, 2020 at 03:52:06PM +0300, Dan Carpenter wrote:
> There is a kobject_add() hidden in the call to kobject_add().
>
> ret = kobject_add(q->mq_kobj, kobject_get(>kobj), "%s", "mq");
> ^^^
>
> It needs to be release on
On Fri 04-09-20 14:10:45, Roman Gushchin wrote:
> On Fri, Sep 04, 2020 at 09:42:07AM +0200, Michal Hocko wrote:
[...]
> > An explicit opt-in sounds much more appropriate to me as well. If we go
> > with a specific API then I would not make it 1GB pages specific. Why
> > cannot we have an explicit
On Thu, 2020-08-06 at 07:26:34 UTC, Evgeny Novikov wrote:
> vf610_nfc_probe() does not invoke clk_disable_unprepare() on one error
> handling path. The patch fixes that.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Fixes: 6f0ce4dfc5a3 ("mtd: rawnand: vf610: Avoid a
On Fri, 2020-07-24 at 08:38:25 UTC, Pavel Machek wrote:
> Simplify oxnas_nand_probe.
>
> Signed-off-by: Pavel Machek (CIP)
> Acked-by: Neil Armstrong
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git
nand/next, thanks.
Miquel
On Wed, 2020-07-22 at 08:02:57 UTC, YouChing Lin wrote:
> The Macronix MX31LF1GE4BC is a 3V, 1Gbit (128MB) serial
> NAND flash device.
>
> Validated by read, erase, read back, write and read back
> on Xilinx Zynq PicoZed FPGA board which included
> Macronix SPI Host (driver/spi/spi-mxic.c).
>
>
On Tue, 2020-07-21 at 09:52:07 UTC, Christophe Kerello wrote:
> This patch solves following static checker warning:
> drivers/mtd/nand/raw/stm32_fmc2_nand.c:350 stm32_fmc2_nfc_select_chip()
> error: buffer overflow 'nfc->data_phys_addr' 2 <= 2
>
> The CS value can only be 0 or 1.
>
>
On Tue, 2020-07-21 at 15:16:57 UTC, Wei Yongjun wrote:
> The sparse tool complains as follows:
>
> drivers/mtd/nand/raw/pasemi_nand.c:71:5: warning:
> symbol 'pasemi_device_ready' was not declared. Should it be static?
>
> This function is not used outside of pasemi_nand.c, so this commit
>
On Wed, 2020-07-22 at 08:02:58 UTC, YouChing Lin wrote:
> The Macronix MX31UF1GE4BC is a 1.8V, 1Gbit (128MB) serial
> NAND flash device.
>
> Validated by read, erase, read back, write and read back
> on Xilinx Zynq PicoZed FPGA board which included
> Macronix SPI Host (driver/spi/spi-mxic.c).
>
Hi all,
I was able to trigger the same issue as reported by Paul, and came
across this patch (+ Daniele's other patch and thread on the libqmi
mailing list). Applying Paul's fix solved the problem for me, changing
the MTU of the QMI interface now works fine. Thanks a lot to everyone
involved!
I
On 9/4/2020 2:31 PM, Peter Ujfalusi wrote:
On 18/08/2020 10.00, Reddy, MallikarjunaX wrote:
Hi Rob,
Thanks for your valuable comments. Please see my comments inline..
On 8/15/2020 4:32 AM, Rob Herring wrote:
On Fri, Aug 14, 2020 at 01:26:09PM +0800, Amireddy Mallikarjuna reddy
wrote:
Add
On Fri 04-09-20 10:25:02, Pavel Tatashin wrote:
> > Another alternative would be to enable/disable static branch only from
> > users who really care but this is quite tricky because how do you tell
> > you need or not? It seems that alloc_contig_range would be just fine
> > with a weaker semantic
On Fri 04-09-20 11:14:47, Pavel Tatashin wrote:
> There is a race during page offline that can lead to infinite loop:
> a page never ends up on a buddy list and __offline_pages() keeps
> retrying infinitely or until a termination signal is received.
>
> Thread#1 - a new process:
>
>
The Amlogic AXg SoCs embeds a MIPI D-PHY to communicate with DSI
panels, this adds the bindings.
This D-PHY depends on a separate analog PHY.
Neil Armstrong (2):
dt-bindings: phy: add Amlogic AXG MIPI D-PHY bindings
phy: amlogic: Add AXG MIPI D-PHY driver
The Amlogic AXg SoCs embeds a MIPI D-PHY to communicate with DSI
panels, this adds the bindings.
This D-PHY depends on a separate analog PHY.
Signed-off-by: Neil Armstrong
---
.../bindings/phy/amlogic,axg-mipi-dphy.yaml | 68 +++
1 file changed, 68 insertions(+)
create mode
The Amlogic AXG SoCs embeds a MIPI D-PHY used to communicate with DSI
panels.
Signed-off-by: Neil Armstrong
---
drivers/phy/amlogic/Kconfig | 12 +
drivers/phy/amlogic/Makefile | 1 +
drivers/phy/amlogic/phy-meson-axg-mipi-dphy.c | 413 ++
3
On Thu, Sep 03, 2020 at 06:54:34PM +0300, Leon Romanovsky wrote:
> From: Maor Gottlieb
>
> Currently, sg_alloc_table_from_pages doesn't support dynamic chaining of
> SG entries. Therefore it requires from user to allocate all the pages in
> advance and hold them in a large buffer. Such a buffer
> +static inline void _sg_chain(struct scatterlist *chain_sg,
> + struct scatterlist *sgl)
> +{
> + /*
> + * offset and length are unused for chain entry. Clear them.
> + */
> + chain_sg->offset = 0;
> + chain_sg->length = 0;
> +
> + /*
> + *
On Thu, Sep 03, 2020 at 03:18:52PM +0300, Leon Romanovsky wrote:
> +struct sg_append {
> + struct scatterlist *prv; /* Previous entry to append */
> + unsigned int left_pages; /* Left pages to add to table */
> +};
I don't really see the point in this structure. Either pass it as
two
We need a simple method to test Perf with Arm CoreSight drivers, this
could be used for smoke testing when new patch is coming for perf or
CoreSight drivers, and we also can use the test to confirm if the
CoreSight has been enabled successfully on new platforms.
This patch introduces the shell
On Thu, Sep 03, 2020 at 03:18:53PM +0300, Leon Romanovsky wrote:
> From: Maor Gottlieb
>
> Remove the implementation of ib_umem_add_sg_table and instead
> call to sg_alloc_table_append which already has the logic to
> merge contiguous pages.
>
> Besides that it removes duplicated functionality,
On Mon, Sep 07, 2020 at 08:50:53AM +0200, Rasmus Villemoes wrote:
>
> Actually, while you're micro-optimizing it, AFAIK VFS already handles
> count==0,
It doesn't.
Something is wrong. In find_busiest_group(), we are checking if src has
higher load, however, in task_numa_find_cpu(), we are checking if dst
will have higher load after balancing. It seems it is not sensible to
check src.
It maybe cause wrong imbalance value, for example, if
dst_running =
Hi Andy,
On Fri, Sep 04, 2020 at 10:12:07PM +0300, Andy Shevchenko wrote:
> On Fri, Sep 4, 2020 at 7:52 PM Vadym Kochan wrote:
> >
> > Marvell Prestera 98DX326x integrates up to 24 ports of 1GbE with 8
> > ports of 10GbE uplinks or 2 ports of 40Gbps stacking for a largely
> > wireless SMB
Hi,
This is not a really good solution, this patch will cause a wrong status to the
user:
The supplicant will give status to the user that we are connected although we
are not able to encrypt a management packet in addition, the supplicant will
try over and over to send the AES_CMAC key.
The
Hi Peter,
Thanks for the review, please see my comment inline..
On 9/4/2020 2:31 PM, Peter Ujfalusi wrote:
On 31/08/2020 11.07, Reddy, MallikarjunaX wrote:
On 8/28/2020 7:17 PM, Peter Ujfalusi wrote:
Hi,
On 27/08/2020 17.41, Reddy, MallikarjunaX wrote:
+
+
On Fri 04-09-20 11:14:48, Pavel Tatashin wrote:
> It is expensive to drain per-cpu page lists as a thread is started on each
> CPU, and we are waiting for them to complete.
>
> Currently, we drain on every block of pages that is isolated. Instead lets
> drain once after pages are isolated.
>
>
Enable sata interface on HiHope RZ/G2H board.
Signed-off-by: Lad Prabhakar
Reviewed-by: Biju Das
---
arch/arm64/boot/dts/renesas/r8a774e1-hihope-rzg2h-ex.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a774e1-hihope-rzg2h-ex.dts
Hi Mathieu,
On Fri, Sep 04, 2020 at 03:33:32PM -0600, Mathieu Poirier wrote:
[...]
> > diff --git a/tools/perf/tests/shell/test_arm_coresight.sh
> > b/tools/perf/tests/shell/test_arm_coresight.sh
> > new file mode 100755
> > index ..8696bb5df45a
> > --- /dev/null
> > +++
The Amlogic AXG MIPI + PCIe Analog PHY provides function for both PCIe and
MIPI DSI at the same time, and is not exclusive.
Thus remove the invalid phy cell parameter.
Signed-off-by: Neil Armstrong
---
.../bindings/phy/amlogic,meson-axg-mipi-pcie-analog.yaml | 4 ++--
1 file changed, 2
The AXG Analog MIPI-DSI PHY also provides functions to the PCIe PHY,
thus we need to have inclusive support for both interfaces at runtime.
This fixes the regmap get from parent node, removes cell param
to select a mode and implement runtime configuration & power on/off
for both functions since
On Mon, 2020-04-27 at 19:54:13 UTC, "Gustavo A. R. Silva" wrote:
> pr_notice is preferred over printk.
>
> Also, coalesce formats as coalescing is part of coding-style:
> "never break user-visible strings such as printk messages"
>
> Suggested-by: Joe Perches
> Signed-off-by: Gustavo A. R.
On Mon, 2020-04-27 at 19:50:37 UTC, "Gustavo A. R. Silva" wrote:
> Update logic for broken test. Use a more common logging style.
>
> It appears the logic in this function is broken for the
> consecutive tests of
>
> if (prog_status & 0x3)
> ...
> else if
On Mon, 2020-08-24 at 02:57:44 UTC, Chris Packham wrote:
> In physmap_flash_of_init() the maps[].name can be populated based on the
> optional 'linux,mtd-name' property in the dts. Make sure this is
> retained when filling in the rest of the map[] data.
>
> Signed-off-by: Chris Packham
Applied
On Tue, 2020-05-05 at 14:01:16 UTC, Arnd Bergmann wrote:
> Building lpddr2_nvm with clang can result in a giant stack usage
> in one function:
>
> drivers/mtd/lpddr/lpddr2_nvm.c:399:12: error: stack frame size of 1144 bytes
> in function 'lpddr2_nvm_probe' [-Werror,-Wframe-larger-than=]
>
> The
1 - 100 of 1482 matches
Mail list logo
