On Wed, Dec 16, 2020 at 03:03:55AM +0100, Andrew Lunn wrote:
> > > From what you are saying, it sounds like from software you cannot
> > > independently control the GPIO controller reset?
> >
> > No. The hardware implements the default MAC reset behavior. So the
> > GPIO controller gets reset sync
On 12/16/20 10:03 AM, Al Viro wrote:
Once more, with feeling: why bother? What's wrong
with using the damn strndup_user() and then doing
whatever checks you want with the data already
copied, living in normal kernel memory, with all
string functions applicable, etc.?
I was trying to avoid the
> -Original Message-
> From: Bin Meng
> Sent: 10 December 2020 19:05
> To: Yash Shah
> Cc: linux-...@vger.kernel.org; linux-ser...@vger.kernel.org; linux-
> p...@vger.kernel.org; linux-...@vger.kernel.org; linux-kernel ker...@vger.kernel.org>; linux-riscv ;
> devicetree ; open list:GPIO
On 07-12-20, 11:46, Viresh Kumar wrote:
> On 19-11-20, 11:35, Viresh Kumar wrote:
> > On 18-11-20, 08:53, Rob Clark wrote:
> > > On Tue, Nov 17, 2020 at 9:28 PM Viresh Kumar
> > > wrote:
> > > >
> > > > On 17-11-20, 09:02, Rob Clark wrote:
> > > > > With that on top of the previous patch,
> > > >
From: Xuewen Yan
when a task dequeued, it would update it's util and cfs_rq's util,
the following calling relationship exists here:
update_load_avg() -> cfs_rq_util_change() -> cpufreq_update_util()->
sugov_update_[shared\|single] -> sugov_get_util() -> cpu_util_cfs();
util = max {rq->cfs.avg.u
On Tue, Dec 15, 2020 at 08:22:23PM -0800, Linus Torvalds wrote:
> I only see this on my laptop, but that's probably because my desktop
> is built using clang. So it's a gcc code generation interaction, I
> suspect..
>
> Anyway, the new warning is
>
> drivers/gpu/drm/drm_edid.o: warning: objto
On 16-12-20, 00:03, Ionela Voinescu wrote:
> Hi,
>
> On Tuesday 15 Dec 2020 at 11:04:16 (+0530), Viresh Kumar wrote:
> > The AMU counters won't get used today if the cpufreq driver is built as
> > a module as the amu core requires everything to be ready by late init.
> >
> > Fix that properly by
Hi,
On Wed, 2020-09-23 at 17:24 +0100, Mark Brown wrote:
> On Mon, Sep 21, 2020 at 07:48:10PM +0800, Hsin-Hsiung Wang wrote:
>
> > +Required properties:
> > +- compatible: "mediatek,mt6359-regulator"
>
> The compatible isn't used by the driver (which is good!) so should be
> dropped from the bin
From: Archie Pusaka
Implements the monitor removal functionality for advertising monitor
offloading to MSFT controllers. Supply handle = 0 to remove all
monitors.
Signed-off-by: Archie Pusaka
Reviewed-by: Miao-chen Chou
Reviewed-by: Yun-Hao Chung
Reported-by: kernel test robot
Reported-by: D
From: Archie Pusaka
Implements the feature to disable/enable the filter used for
advertising monitor on MSFT controller, effectively have the same
effect as "remove all monitors" and "add all previously removed
monitors".
This feature would be needed when suspending, where we would not want
to g
From: Archie Pusaka
Enables advertising monitor offloading to the controller, if MSFT
extension is supported. The kernel won't adjust the monitor parameters
to match what the controller supports - that is the user space's
responsibility.
This patch only manages the addition of monitors. Monitor
From: Archie Pusaka
When the controller is powered off, the registered advertising monitor
is removed from the controller. This patch handles the re-registration
of those monitors when the power is on.
Signed-off-by: Archie Pusaka
Reviewed-by: Miao-chen Chou
Reviewed-by: Yun-Hao Chung
---
(
Hi Greg,
thanks for taking a look at this.
On Tue, Dec 15, 2020 at 02:39:14PM +0100, Greg KH wrote:
> On Tue, Dec 15, 2020 at 09:22:40PM +0800, Chen Yu wrote:
> > The time to finish a xhci_handshake() is platform specific
> > and sometimes during suspend resume test the followng
> > errors were enc
From: Archie Pusaka
MSFT needs rssi parameter for monitoring advertisement packet,
therefore we should supply them from mgmt. This adds a new opcode
to add advertisement monitor with rssi parameters.
Signed-off-by: Archie Pusaka
Reviewed-by: Manish Mandlik
Reviewed-by: Miao-chen Chou
Reviewed
From: Archie Pusaka
Hi linux-bluetooth,
This series of patches manages the hardware offloading part of MSFT
extension API. The full documentation can be accessed by this link:
https://docs.microsoft.com/en-us/windows-hardware/drivers/bluetooth/microsoft-defined-bluetooth-hci-commands-and-events
On Tue, Dec 15, 2020 at 06:23:18PM +0530, Siddhesh Poyarekar wrote:
> +static char *copy_mount_devname(const void __user *data)
> +{
> + char *p;
> + long length;
> +
> + if (data == NULL)
> + return NULL;
> +
> + length = strnlen_user(data, PATH_MAX);
> +
> + if (!
Hi Dan,
On Wed, 16 Dec 2020 at 03:06, Dan Carpenter wrote:
>
> Hi Archie,
>
> url:
> https://github.com/0day-ci/linux/commits/Archie-Pusaka/MSFT-offloading-support-for-advertisement-monitor/20201215-163858
> base:
> https://git.kernel.org/pub/scm/linux/kernel/gi
I only see this on my laptop, but that's probably because my desktop
is built using clang. So it's a gcc code generation interaction, I
suspect..
Anyway, the new warning is
drivers/gpu/drm/drm_edid.o: warning: objtool: do_cvt_mode() falls
through to next function drm_mode_detailed.isra.0()
a
On Thu, Nov 12, 2020 at 05:33:24PM +0800, Kang Wenlin wrote:
> From: Wenlin Kang
>
> The strncpy() function may create a unterminated string,
> use strscpy_pad() instead.
>
> This fixes the following warning:
>
> fs/ext4/super.c: In function '__save_error_info':
> fs/ext4/super.c:349:2: warning
DeeQ X5-Z8300 is a laptop empowered by Intel Atom Cherry Trail. Add
quirks to select the correct input map, jack-detect options to enable
jack sensing and internal/headset microphones.
Signed-off-by: Chris Chiu
---
sound/soc/intel/boards/bytcr_rt5651.c | 8
1 file changed, 8 insertions(
On Wed, 2020-12-16 at 00:05 +0100, Bean Huo wrote:
> From: Bean Huo
>
> Delete ufshcd_wb_buf_flush_enable() and ufshcd_wb_buf_flush_disable(),
> move the implementation into ufshcd_wb_toggle_flush().
>
> Signed-off-by: Bean Huo
> ---
Reviewed-by: Stanley Chu
On Wed, 2020-12-16 at 00:05 +0100, Bean Huo wrote:
> From: Bean Huo
>
> d_wb_alloc_units and d_ext_ufs_feature_sup only be used while WB probe.
> They are just used to confirm the condition that "if bWriteBoosterBufferType
> is set to 01h but dNumSharedWriteBoosterBufferAllocUnits is set to zero,
On Wed, 2020-12-16 at 00:05 +0100, Bean Huo wrote:
> From: Bean Huo
>
> UFS device-related flags should be grouped in ufs_dev_info. Take
> wb_enabled and wb_buf_flush_enabled out from the struct ufs_hba,
> group them to struct ufs_dev_info, and align the names of the structure
> members verticall
On 12/15/20 6:56 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Sun, 13 Dec 2020 22:09:55 -0800 Guenter Roeck wrote:
>>
>> On 12/13/20 9:23 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> After merging the watchdog tree, today's linux-next build (x86_64
>>> allmodconfig) failed like this:
>>>
>>> I
Add DT bindings YAML schema for DMA controller driver
of Lightning Mountain (LGM) SoC.
Signed-off-by: Amireddy Mallikarjuna reddy
Reviewed-by: Rob Herring
---
v1:
- Initial version.
v2:
- Fix bot errors.
v3:
- No change.
v4:
- Address Thomas langer comments
- use node name pattern as dma-co
Add DMA controller driver for Lightning Mountain (LGM) family of SoCs.
The main function of the DMA controller is the transfer of data from/to any
peripheral to/from the memory. A memory to memory copy capability can also
be configured.
This ldma driver is used for configure the device and channn
Add DMA controller driver for Lightning Mountain (LGM) family of SoCs.
The main function of the DMA controller is the transfer of data from/to any
peripheral to/from the memory. A memory to memory copy capability can also
be configured. This ldma driver is used for configure the device and channne
Hi,
The below init_module() prints "foo: false". This is strange since
static_branch_enable() is called before the static_branch_unlikely().
This strange behavior happens to v5.10 and an old v5.4 kernel.
If I remove the "__init" marker from the init_module() function, then
I get the expected outpu
On Wed, Dec 16, 2020 at 11:45 AM Mike Kravetz wrote:
>
> On 12/15/20 5:03 PM, Mike Kravetz wrote:
> > On 12/13/20 7:45 AM, Muchun Song wrote:
> >> diff --git a/fs/Kconfig b/fs/Kconfig
> >> index 976e8b9033c4..4c3a9c614983 100644
> >> --- a/fs/Kconfig
> >> +++ b/fs/Kconfig
> >> @@ -245,6 +245,21 @@
On 12/15/20 5:03 PM, Mike Kravetz wrote:
> On 12/13/20 7:45 AM, Muchun Song wrote:
>> diff --git a/fs/Kconfig b/fs/Kconfig
>> index 976e8b9033c4..4c3a9c614983 100644
>> --- a/fs/Kconfig
>> +++ b/fs/Kconfig
>> @@ -245,6 +245,21 @@ config HUGETLBFS
>> config HUGETLB_PAGE
>> def_bool HUGETLBFS
>
The pull request you sent on Tue, 15 Dec 2020 18:08:55 +0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git
> tags/erofs-for-5.11-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e88bd82698af86887e33b07d48a1aec263cbeddb
Thank you!
--
Deet-doot-d
The pull request you sent on Tue, 15 Dec 2020 19:17:06 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
> exec-update-lock-for-v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d01e7f10dae29eba0f9ada82b65d24e035d5b2f9
Thank you!
The pull request you sent on Tue, 15 Dec 2020 16:31:25 +0100:
> g...@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux
> tags/close-range-openat2-v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/345d4ab5e0a226e0e27219bef9ad150504666b0d
Thank you!
--
De
The pull request you sent on Tue, 15 Dec 2020 16:43:41 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
> signal-for-v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6febd8bef36e64fc1f4aaff1f6302be5c653ad64
Thank you!
--
Deet-d
The pull request you sent on Tue, 15 Dec 2020 16:59:55 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
> exec-for-v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/faf145d6f3f3d6f2c066f65602ba9d0a03106915
Thank you!
--
Deet-doo
The pull request you sent on Mon, 14 Dec 2020 22:51:07 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git regset.followup
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/37373d9c37a3401c08f22b61de1726b4f584b2e7
Thank you!
--
Deet-doot-dot, I am a bot
The pull request you sent on Mon, 14 Dec 2020 22:34:17 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.epoll
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1a825a6a0e7eb55c83c06f3c74631c2eeeb7d27f
Thank you!
--
Deet-doot-dot, I am a bot.
htt
The pull request you sent on Mon, 14 Dec 2020 16:15:53 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.11-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f1ee3b8829006b3fda999f00f0059aa327e3f3d0
Thank you!
--
Deet-doot-dot, I am a bot
The pull request you sent on Mon, 14 Dec 2020 12:07:50 -0600:
> git://github.com/kleikamp/linux-shaggy.git tags/jfs-5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9867cb1fd510187d8f828540bdb48f78fceb70b3
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.doc
The pull request you sent on Mon, 14 Dec 2020 11:54:29 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8a7a4301ddafa8445684c6c9cad2382bd42e7c4a
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Mon, 14 Dec 2020 08:22:46 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git locks-v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a725cb4d708e5ac8bc76a70b3002ff64c07312d8
Thank you!
--
Deet-doot-dot, I am a bo
On 12/14/2020 4:02 PM, Vijayanand Jitta wrote:
>
>
> On 12/14/2020 3:04 PM, Alexander Potapenko wrote:
>> On Mon, Dec 14, 2020 at 5:02 AM Vijayanand Jitta
>> wrote:
>>>
>>>
>>>
>>> On 12/11/2020 6:55 PM, Alexander Potapenko wrote:
On Fri, Dec 11, 2020 at 1:45 PM Vijayanand Jitta
On Tue, Dec 15, 2020 at 3:00 PM Eric W. Biederman wrote:
>
> There is a minor conflict with parallel changes to the bpf task_iter
> code. The changes don't fundamentally conflict but both are removing
> code from same areas of the same function.
Ok, that was somewhat confusing.
I think I got it
Might I tempt an x86/mm maintainer to ack this, or a x86-tip
maintainer to apply it outright?
On Wed, Dec 2, 2020 at 10:28 PM Dan Williams wrote:
>
> Commit 28ee90fe6048 ("x86/mm: implement free pmd/pte page interfaces")
> introduced a new location where a pmd was released, but neglected to run
>
On Wed, Dec 16, 2020 at 9:04 AM Mike Kravetz wrote:
>
> On 12/13/20 7:45 AM, Muchun Song wrote:
> > The purpose of introducing HUGETLB_PAGE_FREE_VMEMMAP is to configure
> > whether to enable the feature of freeing unused vmemmap associated with
> > HugeTLB pages. And this is just for dependency ch
On Wed, Dec 16, 2020 at 4:16 AM Christophe JAILLET
wrote:
>
> Le 15/12/2020 à 20:35, Dan Carpenter a écrit :
> > On Tue, Dec 15, 2020 at 08:08:15PM +0100, Maxime Ripard wrote:
> >> On Tue, Dec 15, 2020 at 07:18:48PM +0100, Christophe JAILLET wrote:
> >>> Le 15/12/2020 à 12:37, Maxime Ripard a écri
Hi,
On Tue, 2020-12-15 at 11:56 +, Mark Brown wrote:
> On Tue, Dec 15, 2020 at 05:23:08PM +0800, Hsin-hsiung Wang wrote:
> > On Tue, 2020-11-24 at 17:07 +, Mark Brown wrote:
>
> > > This looks like it could just be regmap_get_voltage_sel_regmap()?
> > > Otherwise the driver looks good.
>
Quoting Zong Li (2020-11-25 19:00:43)
> Add YAML DT binding documentation for the SiFive FU740 PRCI. The
> link of unmatched board as follow, the U740-C000 manual would be present
> in the same page later.
>
> https://www.sifive.com/boards/hifive-unmatched
>
> Passes dt_binding_check.
>
> Si
On Tue, Dec 15, 2020 at 2:44 PM Eric W. Biederman wrote:
>
> Most of this I believe has already come in through Catalin Marinas pull
> request "arm64 updates for 5.11".
Yeah, pretty much all got merged that way earlier, so I edited your
email heavily for the one remaining part that this pull brou
On Wed, Dec 16, 2020 at 4:21 AM Nicolas Dufresne wrote:
>
> Le mardi 15 décembre 2020 à 15:54 +0200, Stanimir Varbanov a écrit :
> > Hi Tomasz,
> >
> > On 12/15/20 1:47 PM, Tomasz Figa wrote:
> > > On Tue, Dec 15, 2020 at 8:16 PM Stanimir Varbanov
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > >
On Tue, Dec 15, 2020 at 11:37 PM Helen Koike wrote:
>
> Hi Tomasz,
>
> On 12/14/20 7:46 AM, Tomasz Figa wrote:
> > On Fri, Dec 4, 2020 at 4:52 AM Helen Koike
> > wrote:
> >>
> >> Hi,
> >>
> >> Please see my 2 points below (about v4l2_ext_buffer and another about
> >> timestamp).
> >>
> >> On 12
On Tue, Dec 15, 2020 at 10:22:00PM +0100, Michael Walle wrote:
> Now that there aren't any more macros with parameters, move the macros
> above any functions.
>
> Signed-off-by: Michael Walle
Reviewed-by: Andrew Lunn
Andrew
On Mon, Dec 07, 2020 at 06:01:43PM +, Maciej W. Rozycki wrote:
> On Thu, 3 Dec 2020, Al Viro wrote:
>
> > > Linux-mips was cc'd, but I'm adding Thomas B to the cc here explicitly
> > > just so that he has a heads-up on this thing and can go and look at
> > > the mailing list in case it goes to
Hi all,
On Sun, 13 Dec 2020 22:09:55 -0800 Guenter Roeck wrote:
>
> On 12/13/20 9:23 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the watchdog tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > In file included from include/linux/device.h:15,
> >
Expose AVX (VEX-encoded) versions of the Vector Neural Network
Instructions to guest.
The bit definition:
CPUID.(EAX=7,ECX=1):EAX[bit 4] AVX_VNNI
The following instructions are available when this feature is
present in the guest.
1. VPDPBUS: Multiply and Add Unsigned and Signed Bytes
2. VPDPB
A processor supports AVX_VNNI instructions if CPUID.(EAX=7,ECX=1):EAX[bit 4]
is present.
This series includes kernel and kvm patches, kernel patch define this
new cpu feature bit and kvm expose this bit to guest. When this bit is
enabled on cpu or vcpu, the cpu feature flag is shown as "avx_vnni"
From: Kyung Min Park
Add AVX version of the Vector Neural Network (VNNI) Instructions.
A processor supports AVX VNNI instructions if CPUID.0x07.0x1:EAX[4] is
present. The following instructions are available when this feature is
present.
1. VPDPBUS: Multiply and Add Unsigned and Signed Bytes
On Tue, Dec 15, 2020 at 07:41:23PM +0300, Sergey Temerkhanov wrote:
> Unlock RCU before running another loop iteration
If you are able to keep it looping for a long time, I would really
like to see the reproducer.
This patch changes the read I/O to the HPB read I/O.
If the logical address of the read I/O belongs to active sub-region, the
HPB driver modifies the read I/O command to HPB read. It modifies the UPIU
command of UFS instead of modifying the existing SCSI command.
In the HPB version 1.0, the max
On Wed, Dec 16, 2020 at 10:10:22AM +1100, Dave Chinner wrote:
> On Tue, Dec 15, 2020 at 11:05:07AM -0800, Jane Chu wrote:
> > On 12/15/2020 3:58 AM, Ruan Shiyang wrote:
> > > Hi Jane
> > >
> > > On 2020/12/15 上午4:58, Jane Chu wrote:
> > > > Hi, Shiyang,
> > > >
> > > > On 11/22/2020 4:41 PM, Shiy
This is a patch for managing L2P map in HPB module.
The HPB divides logical addresses into several regions. A region consists
of several sub-regions. The sub-region is a basic unit where L2P mapping is
managed. The driver loads L2P mapping data of each sub-region. The loaded
sub-region is called a
syzbot has found a reproducer for the following issue on:
HEAD commit:9317f948 Add linux-next specific files for 20201215
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=151add9750
kernel config: https://syzkaller.appspot.com/x/.config?x
Changelog:
v13 -> v14
1. Cleanup codes by commentted in Greg's review.
2. Add documentation for sysfs entries (from Greg's review).
3. Add experiment result of HPB performance testing. (in this mail)
v12 -> v13
1. Cleanup codes by comments from Can Guo.
2. Add HPB related descriptor/flag/attribut
This is a patch for the HPB initialization and adds HPB function calls to
UFS core driver.
NAND flash-based storage devices, including UFS, have mechanisms to
translate logical addresses of IO requests to the corresponding physical
addresses of the flash storage.
In UFS, Logical-address-to-Physica
Am Freitag, den 11.12.2020, 14:30 +0800 schrieb Meng Yu:
+/* curve25519 */
+static u64 curve25519_g_x[] = { 0x0009, 0x,
+ 0x, 0x };
+static u64 curve25519_p[] = { 0xffed, 0x
On 12/15/2020 09:21 PM, Thomas Bogendoerfer wrote:
On Thu, Dec 03, 2020 at 08:32:52PM +0800, Tiezhu Yang wrote:
In the current code, we can not build under !CONFIG_NUMA and !CONFIG_SMP
on the Loongson64 platform, it seems bad for the users who just want to
use pure single core (not nosmp) to deb
Little kvm works fine with nomodeset, so will be busy for a while
bisecting two other problems that popped up here this cycle. (hohum)
[1.815561] WARNING: CPU: 7 PID: 355 at drivers/gpu/drm/ttm/ttm_pool.c:365
ttm_pool_alloc+0x41b/0x540 [ttm]
[1.815561] Modules linked in: ext4(E) crc16(E)
On Tue, Dec 15, 2020 at 10:21:59PM +0100, Michael Walle wrote:
> value is u16, masking with 0x is a nop. Drop it.
>
> Signed-off-by: Michael Walle
Reviewed-by: Andrew Lunn
Andrew
Am Freitag, den 11.12.2020, 14:30 +0800 schrieb Meng Yu:
+/* size in bytes of the n prime */
+#define HPRE_ECC_NIST_P128_N_SIZE 16
Do we truly need P-128? Besides, I do not see that curve being defined in
contemporary cipher specs.
+#define HPRE_ECC_NIST_P192_N_SIZE 24
+#defin
On Tue, Dec 15, 2020 at 10:21:58PM +0100, Michael Walle wrote:
> The macro enetc_mdio_rd_reg() is just used in that particular case and
> has a hardcoded parameter name "mdio_priv". Define a specific function
> to use for readx_poll_timeout() instead. Also drop the TIMEOUT macro
> since it is used
On Wed, Dec 16, 2020 at 3:21 AM Ted Estes wrote:
> On 12/15/2020 6:01 PM, Jann Horn wrote:
> > On Wed, Dec 16, 2020 at 12:25 AM Alejandro Colomar (man-pages)
> > wrote:
> >> On 12/16/20 12:23 AM, Alejandro Colomar (man-pages) wrote:
> >>> On 12/16/20 12:07 AM, Jann Horn wrote:
> As the comme
Meng,
It looks like not just definitions but some static data is moved to
includes. Why?
Thanks,
Yes, as both 'crypto' and HPRE use elliptic curves parameters, once
we keep them in 'include/crypto/ecc_curve_defs.h', crypto drivers
can use curves parameters without redefining them.
Thanks,
The pull request you sent on Tue, 15 Dec 2020 12:07:49 -0600:
> https://git.kernel.org/pub/scm/linux/kernel/git/andersson/remoteproc.git
> tags/rpmsg-v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e87b070839418ce8fec5aa9d5324d90f47e69f77
Thank you!
--
Deet-do
The pull request you sent on Tue, 15 Dec 2020 12:07:35 -0600:
> https://git.kernel.org/pub/scm/linux/kernel/git/andersson/remoteproc.git
> tags/hwlock-v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0e10f9c89332def4288b33866a1b793ffc94107b
Thank you!
--
Deet-d
The pull request you sent on Tue, 15 Dec 2020 12:07:30 -0600:
> https://git.kernel.org/pub/scm/linux/kernel/git/andersson/remoteproc.git
> tags/rproc-v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ef9df0011791ce302b646e2adf3c698f3b20b90a
Thank you!
--
Deet-do
On Tue, Dec 15, 2020 at 10:21:57PM +0100, Michael Walle wrote:
> Before commit 6517798dd343 ("enetc: Make MDIO accessors more generic and
> export to include/linux/fsl") these macros actually had some benefits.
> But after the commit it just makes the code hard to read. Drop the macro
> indirection
AxiDMA driver exposed the dma_set_max_seg_size() to the DMAENGINE.
It shall helps the DMA clients to create size-optimized linked-list
for the controller.
However, there are certain situations where DMA client might not be
abled to benefit from the dma_get_max_seg_size() if the segment size
can't
Add support for Intel KeemBay AxiDMA BYTE and HALFWORD registers
programming.
Intel KeemBay AxiDMA supports data transfer between device to memory
and memory to device operations.
This code is needed by I2C, I3C, I2S, SPI and UART which uses FIFO
size of 8bits and 16bits to perform memory to devi
Add support for Intel KeemBay AxiDMA device handshake programming.
Device handshake number passed in to the AxiDMA shall be written to
the Intel KeemBay AxiDMA hardware handshake registers before DMA
operations are started.
Reviewed-by: Andy Shevchenko
Signed-off-by: Sia Jee Heng
---
.../dma/dw
Add support for DMA Scatter-Gather (SG) constraint so that DMA clients can
handle the AxiDMA limitation.
Without supporting DMA constraint the default Max segment size reported by
dmaengine is 64KB, which is not supported by Intel KeemBay AxiDMA.
Reviewed-by: Andy Shevchenko
Signed-off-by: Sia J
Add support for Intel KeemBay AxiDMA to the .compatible field.
The AxiDMA Apb region will be accessible if the compatible string
matches the "intel,kmb-axi-dma".
Reviewed-by: Andy Shevchenko
Signed-off-by: Sia Jee Heng
---
drivers/dma/dw-axi-dmac/dw-axi-dmac-platform.c | 8
1 file chan
Add support for Intel KeemBay DMA registers. These registers are required
to run data transfer between device to memory and memory to device on Intel
KeemBay SoC.
Reviewed-by: Andy Shevchenko
Signed-off-by: Sia Jee Heng
---
drivers/dma/dw-axi-dmac/dw-axi-dmac.h | 14 ++
1 file chang
Add support for device_prep_dma_cyclic() callback function to benefit
DMA cyclic client, for example ALSA.
Existing AxiDMA driver only support data transfer between memory to memory.
Data transfer between device to memory and memory to device in cyclic mode
would failed if this interface is not su
Add support for Intel KeemBay AxiDMA to the dw-axi-dmac
Schemas DT binding.
Signed-off-by: Sia Jee Heng
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml | 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/dma/snps,dw
Add device_prep_slave_sg() callback function so that DMA_MEM_TO_DEV
and DMA_DEV_TO_MEM operations in single mode can be supported.
Existing AxiDMA driver only support data transfer between
memory to memory. Data transfer between device to memory and
memory to device in single mode would failed if
Add support for DMA_RESIDUE_GRANULARITY_BURST so that AxiDMA can report
DMA residue.
Existing AxiDMA driver only support data transfer between
memory to memory operation, therefore reporting DMA residue
to the DMA clients is not supported.
Reporting DMA residue to the DMA clients is important as
Add support for of_dma_controller_register() so that DMA clients
can pass in device handshake number to the AxiDMA driver.
DMA clients shall code the device handshake number in the Device tree.
When DMA activities are needed, DMA clients shall invoke OF helper
function to pass in the device handsh
Add device_config() callback function so that the device address
can be passed to the dma driver.
DMA clients use this interface to pass in the device address to the
AxiDMA. Without this interface, data transfer between device to memory
and memory to device would failed.
Reviewed-by: Andy Shevche
Add support for device_synchronize() callback function to sync with
dmaengine_terminate_sync().
Reviewed-by: Andy Shevchenko
Signed-off-by: Sia Jee Heng
---
drivers/dma/dw-axi-dmac/dw-axi-dmac-platform.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/dma/dw-axi-dmac/dw-axi-
The DMA memory block is created at driver load time and exist for
device lifetime. Move the dma_pool_create() to the ->chan_resource()
callback function allowing the DMA memory blocks to be created as needed
and destroyed when the channel is freed.
Reviewed-by: Andy Shevchenko
Signed-off-by: Sia
Simplify and refactor the descriptor management by removing the redundant
Linked List Item (LLI) queue control logic from the AxiDMA driver.
The descriptor is split into virtual descriptor and hardware LLI so that
only hardware LLI memories are allocated from the DMA memory pool.
Up to 64 descript
YAML schemas Device Tree (DT) binding is the new format for DT to replace
the old format. Introduce YAML schemas DT binding for dw-axi-dmac and
remove the old version.
Signed-off-by: Sia Jee Heng
---
.../bindings/dma/snps,dw-axi-dmac.txt | 39 --
.../bindings/dma/snps,dw-axi-dmac.ya
The below patch series are to support AxiDMA running on Intel KeemBay SoC.
The base driver is dw-axi-dmac. This driver only support DMA memory copy
transfers. Code refactoring is needed so that additional features can be
supported.
The features added in this patch series are:
- Replacing Linked Lis
In devfreq_add_device, replace devfreq->dev.parent
as dev to keep code simple.
Signed-off-by: pierre Kuo
---
drivers/devfreq/devfreq.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index 6aa10de792b3..94cc25fd68da 10
On 12/15/2020 6:01 PM, Jann Horn wrote:
On Wed, Dec 16, 2020 at 12:25 AM Alejandro Colomar (man-pages)
wrote:
On 12/16/20 12:23 AM, Alejandro Colomar (man-pages) wrote:
On 12/16/20 12:07 AM, Jann Horn wrote:
Am Tue, Dec 15, 2020 at 06:01:25PM +0100 schrieb Alejandro Colomar (man-pages):
Ther
Hi Geert-san, Matti-san,
> From: Geert Uytterhoeven, Sent: Wednesday, December 16, 2020 1:13 AM
> On Tue, Dec 15, 2020 at 5:02 PM Geert Uytterhoeven
> wrote:
> > On Fri, Dec 11, 2020 at 3:03 PM Vaittinen, Matti
> > wrote:
> > > On Fri, 2020-12-11 at 20:27 +0900, Yoshihiro Shimoda wrote:
> > >
On Tue, Dec 15, 2020 at 5:32 PM Ira Weiny wrote:
>
> On Fri, Dec 11, 2020 at 02:14:28PM -0800, Andy Lutomirski wrote:
> > On Mon, Nov 23, 2020 at 10:10 PM wrote:
> > IOW we have:
> >
> > struct extended_pt_regs {
> > bool rcu_whatever;
> > other generic fields here;
> > struct arch_extende
> > From what you are saying, it sounds like from software you cannot
> > independently control the GPIO controller reset?
>
> No. The hardware implements the default MAC reset behavior. So the
> GPIO controller gets reset synchronously with the MAC reset and that
> can't be changed.
Is there pin
On 12/12/20 4:47 PM, Philip Li wrote:
On Thu, Dec 10, 2020 at 12:41:32PM +, Geva, Erez wrote:
On 10/12/2020 04:11, kernel test robot wrote:
Hi Erez,
Thank you for the patch! Yet something to improve:
Thanks for the robot,
as we rarely use clang for kernel. It is very helpful.
[auto
On Tue, 2020-11-17 at 11:48 -0800, Srinivas Pandruvada wrote:
> Add ACPI IDs for thermal drivers for Alder Lake support.
>
This patch was not in PULL request.
It is simple patch, adding ids. Can we send as part of second PULL?
Thanks,
Srinivas
> Signed-off-by: Srinivas Pandruvada <
> srinivas.pa
101 - 200 of 1218 matches
Mail list logo