| /Linux-v6.1/drivers/pinctrl/intel/ |
| D | pinctrl-intel.c | 104 struct intel_community *community; in intel_get_community() local
108 community = &pctrl->communities[i]; in intel_get_community()
109 if (pin >= community->pin_base && in intel_get_community()
110 pin < community->pin_base + community->npins) in intel_get_community()
111 return community; in intel_get_community()
114 dev_warn(pctrl->dev, "failed to find community for pin %u\n", pin); in intel_get_community()
119 intel_community_get_padgroup(const struct intel_community *community, in intel_community_get_padgroup() argument
124 for (i = 0; i < community->ngpps; i++) { in intel_community_get_padgroup()
125 const struct intel_padgroup *padgrp = &community->gpps[i]; in intel_community_get_padgroup()
137 const struct intel_community *community; in intel_get_padcfg() local
[all …]
|
| D | pinctrl-intel.h | 57 * If pad groups of a community are not the same size, use this structure
82 * struct intel_community - Intel pin community description
83 * @barno: MMIO BAR number where registers for this community reside
94 * @pin_base: Starting pin of pins in this community
95 * @npins: Number of pins in this community
102 * @ngpps: Number of pad groups in this community
104 * @nirqs: Optional total number of IRQs this community can generate
106 * @regs: Community specific common registers (reserved for core driver)
107 * @pad_regs: Community specific pad registers (reserved for core driver)
203 * @communities: Opaque context per community (driver dependent)
|
| D | pinctrl-cherryview.c | 79 * struct intel_community_context - community context for Cherryview
268 * Southwest community can generate GPIO interrupts only for the first 8
362 * North community can generate GPIO interrupts only for the first 8
571 const struct intel_community *community = &pctrl->communities[0]; in chv_pctrl_readl() local
573 return readl(community->regs + offset); in chv_pctrl_readl()
578 const struct intel_community *community = &pctrl->communities[0]; in chv_pctrl_writel() local
579 void __iomem *reg = community->regs + offset; in chv_pctrl_writel()
589 const struct intel_community *community = &pctrl->communities[0]; in chv_padreg() local
595 return community->pad_regs + offset + reg; in chv_padreg()
1348 const struct intel_community *community = &pctrl->communities[0]; in chv_gpio_set_intr_line() local
[all …]
|
| /Linux-v6.1/Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 7 provide a set of rules for almost any open source community. Every
8 open-source community is unique and the Linux kernel is no exception.
10 community will interpret it. We also do not expect this interpretation
28 kernel community, a "maintainer" is anyone who is responsible for a
41 That being said, our community is vast and broad, and there is no new
43 behave in the parts of the community where they are active. That
49 others in the community when needed. Do not be afraid to reach out to
83 the Code of Conduct. The kernel community is aware of that and provides
89 The Linux kernel community primarily interacts on a set of public email
98 Conduct. The Linux kernel community does not have an "official" project
[all …]
|
| D | researcher-guidelines.rst | 8 The Linux kernel community welcomes transparent research on the Linux
13 The community greatly appreciates if researchers can share preliminary
17 sharing open access copies of the published research with the community
20 This document seeks to clarify what the Linux kernel community considers
31 The Linux kernel community expects that everyone interacting with the
34 code) produced by the Linux kernel community is welcome, though research
53 the entire developer community's trust in the contributor (and the
63 When engaging with the developer community, sending a patch has
141 related to this document and the developer community's expectations,
|
| D | code-of-conduct.rst | 11 our community a harassment-free experience for everyone, regardless of age, body
25 * Focusing on what is best for the community
26 * Showing empathy towards other community members
58 when an individual is representing the project or its community. Examples of
59 representing a project or community include using an official project e-mail
86 kernel community will be interpreting this document.
|
| D | 1.Intro.rst | 13 availability to users, community support in many forms, and the ability to
25 emphasis on involving the development community as soon as possible.
33 review. To be taken seriously by the development community, patches must be
81 Working with the kernel development community is not especially hard. But,
83 difficulties when trying to do kernel work. The kernel community has
93 community's ways (or, worse, who tries to flout or circumvent them) will
94 have a frustrating experience in store. The development community, while
101 community is always in need of developers who will help to make the kernel
103 join our community.
121 learning how to work with the kernel community and get their code into the
[all …]
|
| D | kernel-enforcement-statement.rst | 9 sustainability of our software and community.
12 contributions made to our community, we share an interest in ensuring that
14 community and do not have an unintended negative impact on the health and
17 community to undertake the following commitment to users of the Linux kernel
21 it is in the best interests of our development community to adopt the
45 as a last resort, to be initiated only when other community efforts have
|
| D | 3.Early-stage.rst | 31 immediate problem. To the wider kernel community, though, it was seen as a
38 The audio community, however, could not see past the particular solution
55 - and to discuss it with the development community before investing in the
75 discussions with the community before launching into implementation. Early
95 Years of experience with the kernel development community have taught a
98 released into the community. Sometimes these problems are severe,
100 the kernel community's standards. Some examples include:
173 provide can help the development community provide useful input on the
189 community informed as you go.
|
| D | howto.rst | 8 to work with the Linux kernel development community. It tries to not
24 and hints on how to work with the community. It will also try to
25 explain some of the reasons why the community works like it does.
50 existing development community. It is a diverse group of people, with
79 invaluable for learning how to interact with the kernel community. When
207 some task to start doing to join into the kernel development community,
429 Working with the community
432 The goal of the kernel community is to provide the best possible kernel
457 In a community that is looking for the best technical solution possible,
471 Differences between the kernel community and corporate structures
[all …]
|
| D | index.rst | 9 Working with the kernel development community
14 to learn about how our community works. Reading these documents will make
38 Other guides to the community that are of interest to most developers are:
|
| D | embargoed-hardware-issues.rst | 78 unable to enter into any non-disclosure agreements. The kernel community
86 The Linux kernel community has a deep understanding of the requirement to
90 The Linux kernel community has successfully handled hardware security
92 community compliant development under embargo restrictions.
94 The Linux kernel community has a dedicated hardware security team for
108 effective deterrent in our community. In case a violation happens the
194 kernel developer community as needed. Bringing in experts can happen at any
275 the Linux kernel community.
|
| D | 2.Process.rst | 39 community) is merged into the mainline kernel. The bulk of changes for a
161 done without involving the community, but it is better to do this work
198 leave a poor impression in the development community. Merging code
349 community is git. Git is one of a number of distributed version control
350 systems being developed in the free software community. It is well tuned
389 lists. It is hard to be a fully-functioning member of the community
408 development community comes together as a whole; developers who avoid this
475 noise which is distracting for the development community as a whole, so,
477 introduce themselves to the community will not get the sort of reception
496 building respect with the rest of the development community.
|
| D | development-process.rst | 22 work with the development community with a minimum of frustration. It is
23 an attempt to document how this community works in a way which is
|
| D | 6.Followthrough.rst | 17 kernel community to ensure that your code is up to the kernel's quality
98 kernel development community; he can often unjam a situation which seems to
123 contents visible to the development community as a whole. At this point,
179 development community remembers developers who lose interest in their code
211 be hurtful and discouraging, but the community will remember your reaction
|
| D | 5.Posting.rst | 7 the community for review and, eventually, inclusion into the mainline
8 kernel. Unsurprisingly, the kernel development community has evolved a set
23 feedback from the community before the work is complete. So you should
38 sending patches to the development community. These include:
82 out how to do it in the way that the community expects. There are a few
|
| /Linux-v6.1/sound/soc/sof/ |
| D | sof-pci-dev.c | 111 /* all Up boards use the community key */
120 * All newer platforms use the community key
247 * for platforms using the SOF community key, change the in sof_pci_probe()
265 "community"); in sof_pci_probe()
268 "Platform uses community key, changed fw path to %s\n", in sof_pci_probe()
|
| /Linux-v6.1/Documentation/scsi/ |
| D | FlashPoint.rst | 24 "Mylex is committed to supporting the Linux community," says Peter Shambora,
86 been problematic for members of the Linux community, in that no Linux
112 publicly about BusLogic's attitude toward the Linux community, and I felt
132 SCSI solution for the Linux community, and does not want to see anyone left
|
| D | lpfc.rst | 43 The community supporting kernel.org has driven an effort to remove
52 community in modifying the behavior of the SCSI midlayer so that SCSI
|
| /Linux-v6.1/Documentation/ |
| D | index.rst | 15 Working with the development community
19 community and getting your work upstream.
|
| /Linux-v6.1/tools/testing/selftests/rcutorture/doc/ |
| D | rcu-test-image.txt | 60 https://help.ubuntu.com/community/KVM/CreateGuests
61 https://help.ubuntu.com/community/JeOSVMBuilder
|
| /Linux-v6.1/Documentation/devicetree/bindings/arm/omap/ |
| D | omap.txt | 119 - OMAP3 BeagleBoard : Low cost community board
131 - OMAP4 PandaBoard : Low cost community board
149 - AM335X Bone : Low cost community board
|
| /Linux-v6.1/Documentation/arc/ |
| D | arc.rst | 12 - `<https://embarc.org>`_ - Community portal for open source on ARC.
20 Other projects are developed by Synopsys and made available to community
|
| /Linux-v6.1/Documentation/gpu/ |
| D | introduction.rst | 108 As a freedesktop.org project, dri-devel, and the DRM community, follows the
112 interacting with community members on mailing lists, IRC, or bug
113 trackers. The community represents the project as a whole, and abusive
|
| /Linux-v6.1/drivers/net/ |
| D | LICENSE.SRC | 13 of ideas throughout the research community. All software is furnished
|
